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
For now when I download the files using fido.fetch, and after renaming files to highlight the instrument, time and the wavelength resulting in filenames (for an an hour) as EIT_2010-05-10T11:12:12.174Z_195.fits EIT_2010-05-10T11:24:10.567Z_195.fits EIT_2010-05-10T11:36:10.559Z_195.fits EIT_2010-05-10T11:48:10.851Z_195.fits EIT_2010-05-10T12:00:10.542Z_195.fits EUVI-A_2010-05-10T11:06:15.007_304.fits EUVI-A_2010-05-10T11:15:30.007_195.fits EUVI-A_2010-05-10T11:25:30.006_195.fits EUVI-A_2010-05-10T11:30:30.006_195.fits EUVI-A_2010-05-10T11:40:30.006_195.fits EUVI-A_2010-05-10T11:46:15.006_304.fits EUVI-A_2010-05-10T11:55:30.006_195.fits EUVI-A_2010-05-10T12:05:30.006_195.fits EUVI-B_2010-05-10T11:05:55.441_195.fits EUVI-B_2010-05-10T11:06:40.443_304.fits EUVI-B_2010-05-10T11:15:55.442_195.fits EUVI-B_2010-05-10T11:25:55.443_195.fits EUVI-B_2010-05-10T11:30:55.444_195.fits EUVI-B_2010-05-10T11:40:55.446_195.fits EUVI-B_2010-05-10T11:46:40.446_304.fits EUVI-B_2010-05-10T11:55:55.448_195.fits EUVI-B_2010-05-10T12:05:55.449_195.fits
However, there is a significant timing issue. I mean we would wabt to restrict ourseves with data that is taken more or less at the same time. Is there a way to resolve this, maybe we should add a functionality to find times.
The text was updated successfully, but these errors were encountered:
I was wondering if the header information (which I am using to rename files for convenience) does have time information. A hacky way would be to find overlaps of time within a tolerance limit. It is the inconsistency between EIT and STEREO cadence, that might work in our favour. Maybe @edmondb@tremblaybenoit have some ideas?
For now when I download the files using fido.fetch, and after renaming files to highlight the instrument, time and the wavelength resulting in filenames (for an an hour) as
EIT_2010-05-10T11:12:12.174Z_195.fits EIT_2010-05-10T11:24:10.567Z_195.fits EIT_2010-05-10T11:36:10.559Z_195.fits EIT_2010-05-10T11:48:10.851Z_195.fits EIT_2010-05-10T12:00:10.542Z_195.fits EUVI-A_2010-05-10T11:06:15.007_304.fits EUVI-A_2010-05-10T11:15:30.007_195.fits EUVI-A_2010-05-10T11:25:30.006_195.fits EUVI-A_2010-05-10T11:30:30.006_195.fits EUVI-A_2010-05-10T11:40:30.006_195.fits EUVI-A_2010-05-10T11:46:15.006_304.fits EUVI-A_2010-05-10T11:55:30.006_195.fits EUVI-A_2010-05-10T12:05:30.006_195.fits EUVI-B_2010-05-10T11:05:55.441_195.fits EUVI-B_2010-05-10T11:06:40.443_304.fits EUVI-B_2010-05-10T11:15:55.442_195.fits EUVI-B_2010-05-10T11:25:55.443_195.fits EUVI-B_2010-05-10T11:30:55.444_195.fits EUVI-B_2010-05-10T11:40:55.446_195.fits EUVI-B_2010-05-10T11:46:40.446_304.fits EUVI-B_2010-05-10T11:55:55.448_195.fits EUVI-B_2010-05-10T12:05:55.449_195.fits
However, there is a significant timing issue. I mean we would wabt to restrict ourseves with data that is taken more or less at the same time. Is there a way to resolve this, maybe we should add a functionality to find times.
The text was updated successfully, but these errors were encountered: