-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not producing *icubes.fits files, issue with standard star calibration or missing file? #137
Comments
Hi Shawn, Your reduction log indicates that the pipeline is failing to recognize your standard star as a standard star or that you are missing the matching standard file. I am pretty sure that you need to edit the OBJECT header keyword to be "bd26d2606" and "bd28d4211" instead of "BD+262606" and "BD+284211" in frames #28 and 40-42 respectively. The pipeline should then be able to recognize them as standards. Cheers, |
Hi Rosalie, Thank you for the quick response! I've made those changes and rerun the pipeline. It finished very quickly and appears not to actually have done anything. There are still no *icubes.fits files in the redux folder.. Most of the events say "Already processed (already in proctab)". Only one event failed: 2022-07-18 13:22:35:DRPF:INFO: Event completed: name file_ingested, action action_planner, arg name kb210507_00017.fits, recurr False I've attached the full terminal output in txt file again. Thank you! |
Hi Shawn, I suspect you will need to entirely rerun the pipeline, because it still thinks 28 and 40-42 are OBJECT frames, which was determined the first time you ran the pipeline. You need the pipeline to reassess all the data, not use previous pipeline files. Cheers, |
Hi Rosalie,
Thank you very very much for your help. I will try it again.
All the best,
Shawn
…On Tue, Jul 19, 2022 at 1:13 AM Rosalie McGurk ***@***.***> wrote:
Hi Shawn,
I suspect you will need to entirely rerun the pipeline, because it still
thinks 28 and 40-42 are OBJECT frames, which was determined the first time
you ran the pipeline. You need the pipeline to reassess all the data, not
use previous pipeline files.
Cheers,
Rosalie
—
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMJGO4NWQVTR2JUXYVMEN2DVUXQIBANCNFSM53WV7OQQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hello,
I opened an issue in February (#126 ) that was mostly solved, but I had an additional question that was never addressed. One night in particular has not successfully reduced. It fails to produce *icubes.fits files, but it does produce the other *icube, *icubed, and *icubew files. I have successfully reduced several other nights with the same process. I suspect there may be some file missing? The *icubes.fits are calibrated to the standard star, correct?
A colleague of mine sent me mosaics made from the same observations. I noticed that the pixel values are several orders of magnitude higher than my other observations, which suggests to me that they probably used one of the datacube types that was not calibrated to the standard star. So I think they had similar problems.
I hope we can figure this out! :) Thanks!
Shawn
Below, I've attached two txt files. The first is the terminal output from my attempt to reduce the data in March. The second is just the lines that mentioned a failure to create a file.
03042022_may7_reduction.txt
03042022_may7_reduction_failed.txt
The text was updated successfully, but these errors were encountered: