Fits file naming schemes

[kyyip]

Given that we are working with fits files from various sources(ptf, lco, simulated), and these image sets have various naming schemes that differ from one another, I think it would make sense to try and establish a consistent fits file naming scheme. There are two reasons for this. One, we can avoiding sorting issues when loading fits files using 'read', in particular alphanumeric naming schemes, i.e. 0.fits, 1.fits, etc. Although with Ben's recent pull request, this is much less of an issue. Second, we can include information about the fits file into the name of the file itself(date, source, level of processing, etc.). It would be nice to simply look at the name of a fits file and know it's contents straight away instead of having to decipher 'elp0m411-kb88-20200117-0129-e00.fits.fz' or sets of images that just say '{integer number}.fits'. Comment if you have any ideas, or if this idea is a bad one.

[varun-magesh]

This is a great idea, what standard of naming would you propose?

[PK0207]

I think maybe we can pull the date of images and source of images (PTF, LCO, etc.) and add that to the index naming scheme we have