You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only purpose of the SCST file in gPipeline right now is to extract the FDTTDC (FUV detector temperature) for correction of relative offsets. It would make more sense to put all of these temperatures into a per-eclipse lookup table at a MAST database rather than require the SCST file.
The text was updated successfully, but these errors were encountered:
That's sounds straightforware, you don't by chance have some python code handy that would take a file as input and then spit out the eclipse number and any needed data to sysout and I can just redirect to a file, I can run it on all the SCST files and load the data into the DB. Alternatively I can use some tools that I'm familiar with to do it but that might take longer.
The only purpose of the SCST file in gPipeline right now is to extract the FDTTDC (FUV detector temperature) for correction of relative offsets. It would make more sense to put all of these temperatures into a per-eclipse lookup table at a MAST database rather than require the SCST file.
The text was updated successfully, but these errors were encountered: