396 / 376 / 347 / 358 / 409 / 357 / 400 contains all the changes for optical that currently stands #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e optical table data correctly. but we're now much closer.
…ode away now that im no longer facing radio telescope states
This was referenced Apr 15, 2025
Closed
Closed
…plit them up. and then extra work to try to get the summary page to be filled in
357 abs optical submission
changes from 396 to 400
alan-stokes
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
376:
includes new interfaces for new data extractions needed to both separate the 2 types of observation and to extract the telescope data for the table.
358:
adds the cascade functionality to support deletion correctly.
347:
this contains classes for the data extracted from the xml.
396:
nothing needed for this ticket.
400:
i think this is just the split from condition, so i think that makes it really a master merge update. but who knows.
357:
contains the api object for the rest request for cloning a proposal in the optical database and then some extra support for debugging
409:
nothing needed for this ticket.