Rename to LIGO/Virgo/KAGRA Public Alerts User Guide.

Issue: #271 (closed) Related merge request: !96 (merged)

changed milestone to %Review Readiness Presentation

assigned to @leo-singer

mentioned in issue #271 (closed)

changed title from Draft: Change "LIGO/Virgo" to "LIGO/Virgo/KAGRA" and report new "Timeline" of the observational plan. to Draft: Rename to LIGO/Virgo/KAGRA Public Alerts User Guide and report new "Timeline" of the observational plan.

changed the description

added 1 commit

• 15499bb8 - More work

Compare with previous version

added 1 commit

• 8c6d7db5 - More work

Compare with previous version

marked this merge request as ready

changed title from Rename to LIGO/Virgo/KAGRA Public Alerts User Guide and report new "Timeline" of the observational plan. to Rename to LIGO/Virgo/KAGRA Public Alerts User Guide.

@shaon.ghosh @brandon.piotrzkowski Please give a look.

I have the same question as in !96 (merged): why not rename to the IGWN Public Alerts User Guide? Have we received instruction from spokespersons?

resolved all threads

added 1 commit

• 5ab15fb4 - Typo

Compare with previous version

resolved all threads

The XML files, FITS headers, and sample code output need to be updated. See my earlier MR.

It is probably easier just to review my MR.

added 1 commit

• 7ec37379 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

@leo-singer I cannot access !96 (diffs).

I don't know why that would be. My fork is publicly accessible.

@leo-singer Very strange. Anyway, I checked your merge request !96 (merged) and I approved it. In that merge request, I am set as a reviewer and not as a peer. I suggest that you may merge it and that I will rebase this one with respect to the new master.