Setup pipeline for night-time observations

[eford]

Nightime NEID data is very similar except:

• there's no pyrheliometer data, so no need to download L0 files; and
• 2. there multiple target stars being observed, so will want to add another layer to the directory structure for the target.
     Let's talk through before actually implementing this

[eford]

To find datafiles to be included in the automatic downloads/processing for nighttime observations, please query:

• All publically avaliable L2 files for the following targets (standard stars):
  • HD 4628
  • HD 9407
  • HD 10700 (τ Ceti)
  • HD 89269
  • HD 127334
  • GJ 699 (Barnard’s Star)
  • HD 185144 (σ Draconis)
  • HD 221354
• All avaliable L2 files for all targets from the following programs (some will be public, but others will require my login/password to access)
  • 2021A-2015
  • 2021B-2015
  • 2021A-0390
  • 2021B-0450

[eford]

For the directory structure of nighttime observations, my initial suggestion is
Inputs:
ROOT/INST/OBJECT/PIPELINEVER/L2/YYYY/MM/DD/neid*.fits
Outputs:
ROOT/INST/OBJECT/PIPELINEVER/outputs/USERID/PIPELINEID/YYYY/MM/DD/*.{jld2,fits,csv,toml}
where
ROOT = /gpfs/group/ebf11/default/pipeline/data/
INST = neid
OBJECT = string taken from OBJECT field of primary FITS header (if spaces convert them to _)
PIPELINEVER: Note that you can now check swversion when you run a query and see which version of the DRP pipeline at TAC was used to create the currently avaliable file. We want the major and minor version to match, but can process files with different patch release versions as part of the same group. So for now PIPELINEVER could be "v1.1".
L2: For nighttime observations, we only need to download the L2 files (not the L0 or L1's).