Separating allSky and SSM and PE source classification

Description

Separating allSky and SSM and PE source classification

• Based on search type or PE updatem, define source classes in each of the cases.
• This is a first commit that roughly defines the properties for SSM alerts.

Checklist

Thanks for your contribution! Please complete and check off the following quality control tasks.

Changes:

• I created this merge request from my own fork and from a branch other than main or master.
• I checked that the CI pipeline completes without errors.
• I added a change log entry (or this is a minor change that does not require a change log entry).

Whitespace:

• No line that I added ends with trailing whitespace.
• Every file that I modified ends with one blank line.

Grammar and spelling:

• I proofread my contribution and made sure that it is free from spelling and grammatical errors.
• I used American English rather than British English spelling.
• I used the Oxford (serial) comma in lists of three or more items.
• I minimized use of the passive voice.

Figures and code:

• I contributed plot directive code to generate figures (or I did not contribute any figures).
• I contributed Python code that conforms to the PEP 8 style guide (or I did not contribute Python code).

added O4 SSM labels

assigned to @bhooshan.gadre

@deep.chatterjee @sushant.sharma-chaudhary This is just a first try. I tried separating by the search type or PE.

Also, I need to define SSM as a term somewhere, I guess.

added 1 commit

• 284d6f56 - Adding source property definistions from online PE

Compare with previous version

added 1 commit

• 1229fba1 - Some consistency style fixes

Compare with previous version

added 1 commit

• 04343bcd - definition for SSM

Compare with previous version

added 1 commit

• b92802b5 - Fixing Title underline too short warning

Compare with previous version

mentioned in merge request !242 (closed)

added 1 commit

• bf417874 - Adding relevant content from...

Compare with previous version

Now the MR contents also include relevant parts from !242 (closed) . @divya.singh @ryan.magee Please have a look.

added 1 commit

• 9ad70610 - AllSky supercedes SSM for superevent condition added

Compare with previous version

Checks: What is the starting frequency used by Online PE for SSM superevents? Is it same as searches or does PE uses the full frequency band?

This MR is a draft. Please remember to remove the draft status when you are ready for review.

@bhooshan.gadre looks mostly good. There are a few typos and/or minor changes I don't think you want to pull in:

1: depeding -> depending

2: added an extra - (I don't know if that matters)

3: I don't think the i should be in the middle of that line.

4: that the either -> that either

5: this is definition -> this definition

6: in reference -> in the reference

7: from higher frequency -> from higher frequencies OR from a higher frequency

8: GstLAL, MBTA -> GstLAL and MBTA

Thank you for carrying this forward, Bhooshan. Can I close !242 (closed) now?

added 1 commit

• d76c05aa - Upading source properties

Compare with previous version

added 1 commit

• 1c940576 - Addressing Ryan's comments

Compare with previous version

resolved all threads

The Alert Content section excludes HasSSM quantities in many places like Alert examples, VO events and properties section.

In Data Analysis/ Inference sections, lets make a tabular layout connecting search and source properties and its differences.

added 1 commit

• ab243a4d - Adding SSM and updating HasNS dependence on search

Compare with previous version