Is RUN_POLAR redondant with RUN_POSTALL in .ini files ? (0.7.286)

[larnoldgithub]

Run the polar recipes

RUN_POLAR = True

Run the postprocessing recipes

RUN_POSTALL = True

[njcuk9999]

These are completely different.

You can find the sequences here: http://apero.exoplanets.ca/auto/recipe_sequences/spirou/sequences.html

Note that the names (POLAR and POSTALL) depend on the sequence being used in the run.ini files

But I think you are looking at a run.ini will the full_seq thus you look at this page: http://apero.exoplanets.ca/auto/recipe_sequences/spirou/sequence_full_seq.html

ORDER | RECIPE | SHORTNAME | RECIPE KIND | REF RECIPE | FIBER | FILTERS | ARGS | KWARGS

35 | apero_pol_spirou.py | POLAR | polar-tcorr | No | AB | KW_DPRTYPE: POLAR_FP, POLAR_DARK |   | –exposures=[TELLU_OBJ]

36 | apero_postprocess_spirou.py | POSTALL | post-all | No | – | KW_DPRTYPE: OBJ_FP, OBJ_DARK, POLAR_FP, POLAR_DARK | {files}=[DRS_PP] |  

So

• RUN_POLAR runs the apero_pol_spirou.py recipe
• RUN_POSTALL runs the apero_postprocessing_spirou.py recipe

I reminder that apero_postprocessing just produces the CADC outputs from the rest of the reduction (so just the packaging of the e.fits, t.fits, s.fits, v.fits) it does not run any code to run the CCF, extraction, telluric correction etc

[larnoldgithub]

Thanks Neil, Indeed I'm using the full_seq