Documentation review: Creating and managing events
Creating an event from a YAML file.
Statement: A full list of all of the events available in this manner is available in the curated settings documentation A link is missing/ Add a link at the statement, e.g.: A full list of all of the events available in this manner is available in the curated settings documentation, see this link.
There already is a notice on this (see screenshot on the left) [Screenshot of the TODO in the documentation]
Adding an event from GraceDB
Command description:
ligo_proxy_init isaac.asimov
[Screenshot showing that ligo_proxy_init
is not found.
Adding an event from GraceDB
Command description:
asimov event create --superevent S200316bj
[Screenshot showing that authentication details can't be found]
Might be due to the type of account I have?
Getting a set of events from GraceDB
Command description:
asimov event create --search "label:PE_READY"
[Screenshot showing 403 error]
Creating an event using the command line
Command description:
asimov event create GW150914
Missing a -n, so
asimov event create -n GW150914
Adding additional configuration information
It works!!!
So, the Todo below can be removed.
Couldn’t check
olivaw event configurator GW170817 --json gw170817.json
as I couldn’t find where to run PE configurator
Adding calibration evelopes
Example command `asimov event calibration GW150914 --calibration H1:/home/albert.einstein/h1-cal.dat --calibration L1:/home/ albert.einstein/l1-cal.dat
-
Correct the title: envelopes -
Eliminate the space after -- so:
asimov event calibration GW150914 --calibration
H1:/home/albert.einstein/h1-cal.dat --calibration
L1:/home/albert.einstein/l1-cal.dat
Adding calibration for GW170817
Does not add the calibration files for available detectors in the ledger nor it does the manual addition from file with --calibration [path]
for this, I’ve got paths from another given example, after having just created the event and without using asimov apply -f ...
Automated documentation section
asimov event create
Missing -n, so in the documentation we should write:
asimov event create -n NAME
In the subsequent list of options, --search is missing
asimov event load
and asimov event populate
Commands load and populate not found!
asimov event delete
asimov event delete appears as a possibility when typing asimov event –help
but then when using it, it does not work and asimov event delete –help
yields the screenshot above, looking non-sensical because of DELETE
Webpage The Asimov ledger:
https://asimov.docs.ligo.org/asimov/master/ledger.html#ledger Where What to do Notes All the way in the page Add examples under (as done for the other sections) : • Project data • Event data • Analysis data • Pipeline data (here, adding also bayswave in example list) I wonder whether we should also provide a description for every item in every key. For example: • Under the key data: which is the full list of possible data types, and then one depth down, e.g. the lists for calibration: , channels: etc. • When numerical values are involved, as e.g. in segment length: 4 provide the description for segment length and the range of values it might be given It’s a lot of work, but I think that in this manner it would really be very user-friendly. I can do it, using existing documentation somewhere. For example: from GraceDB?