-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FRB Schema for the CHIME Telescope #217
base: main
Are you sure you want to change the base?
Conversation
Seeing many failed checks, is there action I should take on this? Cheers! |
Yes, there were some missing contributing instructions to configure pre-commit hooks. See #218. |
@tabbott36 A gentle reminder. Please validate it and run prettier, before we start reviewing it. |
Hi @tabbott36, I see from your commits that you ran the Also, I would suggest updating the names of your example files, for example: from |
Hi @dakota002, thanks for the help! Yes, I will revert the versioning and rename the example files. |
@@ -0,0 +1,24 @@ | |||
{ | |||
"$schema": "https://gcn.nasa.gov/schema/main/gcn/notices/chime/frb.schema.json", | |||
"alert_type": "detection", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a valid option, the allowed values are:
"allowedValues": [
"initial",
"update",
"retraction"
]
These are defined here https://github.com/nasa-gcn/gcn-schema/blob/main/gcn/notices/core/Alert.schema.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review, I was hoping to be consistent with existing CHIME/FRB Alert types (see issue 198), but if this is too much trouble, "initial" can replace what we currently call "detection" and "subsquent".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tabbott36 we are working on adding subsequent
(see #221).
However, initial
will likely remain the same, else we need to take votes from the missions that are already using it.
For validation, as detection
and subsequent
please add a new property, current alert_type
is not consistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, sounds good to me. Thanks, Vidushi!
No problem! I have suggested a few other changes that should also fix your validation checks |
@tabbott36 This looks good to me now, can you please squash your commits down to 1? If you have questions on this I can assist you |
… the frb schema feat(chime/frb.schema.json): final touches on the FRB schema "properties" fix(npm): Fixed npm checks 4.2.0 Back to development Update gcn/notices/chime/frb.schema.json Co-authored-by: Dakota Dutko <[email protected]> Update gcn/notices/chime/detection.example.json Co-authored-by: Dakota Dutko <[email protected]> Update gcn/notices/chime/retraction.example.json Co-authored-by: Dakota Dutko <[email protected]> Update gcn/notices/chime/subsequent.example.json Co-authored-by: Dakota Dutko <[email protected]> Update gcn/notices/chime/update.example.json Co-authored-by: Dakota Dutko <[email protected]> fix(Versioning): reverted version number to 4.1.0 fix(version): Reverted the version to 4.1.0 using npm fix(gal_el_model-properties): corrected galactic electron density model properties fix(Data-types): Fixed incorrect data types in FRB schema
Sure thing! I believe it's been squashed to one commit now. Thanks! |
@Vidushi-GitHub @jracusin is this good now? |
We still are working on it. |
"type": "number", | ||
"description": "A machine learning score from 0-1 separating RFI (0) from an astrophysical signal (1)" | ||
}, | ||
"probability": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"probability": { | |
"association_probability": { |
}, | ||
"sampling_time": { | ||
"type": "number", | ||
"description": "The time resolution of the real-time FRB search." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in what units?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review, I will correct this to say milliseconds.
"properties": { | ||
"alert_kind": { | ||
"type": "string", | ||
"description": "The kind of alert (detection or subsequent). Similar meaning to alert_type" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is updated in the core schema, please utilize it.
}, | ||
"snr": { | ||
"type": "number", | ||
"description": "Signal-to-noise ratio of the burst" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this different from rate_snr
in core/Statistics.schema.json?
"description": "Signal-to-noise ratio of the burst" | |
"description": "Signal-to-noise ratio of the burst [dimensionless]" |
"type": "number", | ||
"description": "Estimated contribution to the dispersion measure from the Galaxy using the YMW2016 model." | ||
}, | ||
"trigger_time_error": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This property has been added in the core/DateTime.schema.json, please utilize it.
"type": "number", | ||
"description": "The time resolution of the real-time FRB search." | ||
}, | ||
"bandwidth": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it's same as spectrum
property in core/Reporter.schema.json?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, yes, it looks like the same thing. "bandwidth" here is the frequencies over which the instrument observes, so I think it alligns well with the "spectrum" property. I'll update it! Thanks
Hi @tabbott36, we have added a few properties in core schema motivated from your CHIME/FRB schema, thanks! |
Description
Added the FRB schema for the Canadian Hydrogen Intensity Mapping Experiment (CHIME). Also added an example json for each alert type (detection, subsequent, retraction, and update).
Questions for GCN Team
Testing
I modelled the schema after other observatories' schemas but am open to suggestions regarding testing.