Duplicated file name from different data request

[ennosigaeus]

I found this curious case in our analysis of the duplicated file names.

solo_L1_stix-sci-xray-spec_20220124T120004-20220124T180507_V01_2201240033-59166.fits    L1  spec    20220124T120004 20220124T180507 V01 2201240033  59166   spec_20220124T120004_20220124T180507
solo_L1_stix-sci-xray-spec_20220124T120004-20220124T180507_V01_2201249786-60605.fits    L1  spec    20220124T120004 20220124T180507 V01 2201249786  60605   spec_20220124T120004_20220124T180507

There are two requests "behind" those two files.

Request number 2201249786 is over 21900 seconds and captures data from 12 pm to 6 pm, which is in line with the file name (12 - 18). The request number 2201240033 is only over 5791 seconds and starts at roughly 3 am in the morning. This should lead to a file name indicating an interval ranging from 3 am to 4:30 am. However, the file name is the same as for the other request.

[nicHoch]

some more insights:

with the RID 2201240033 are actually 2 RIDs "connected"

2201240033 and 2201240014

here are the IORs (@drhlxiao thanks for providing the link and a new search API https://datacenter.stix.i4ds.net/api/ior/uid/2201240033)

2201240033:

IOR https://datacenter.stix.i4ds.net/view/ior/overview/675

it says: Start Time - seconds (PIX00072) = 696340696 2022-01-24T11:59:59 Tmax (PIX00078) = 219000 (21900 s) = 6h

DataCenter: https://datacenter.stix.i4ds.net/view/list/bsd this DOES NOT align with the request TC

https://datacenter.stix.i4ds.net/view/list/fits this aligns with the request TC

https://datacenter.stix.i4ds.net/view/data-request/list this DOES NOT align with the request TC it shows the request times for RID 2201240014 instate

STIXCore product: solo_L1_stix-sci-xray-spec_20220124T120004-20220124T180507_V01_2201240033-59166.fits here this aligns with the request TC

2201240014:

IOR https://datacenter.stix.i4ds.net/view/ior/overview/643

it says: Start Time - seconds (PIX00072) = 696307935 2022-01-24T02:53:58 Tmax (PIX00078) = 57910 (5791 s) = 1.6h

DataCenter: https://datacenter.stix.i4ds.net/view/list/bsd this aligns with the request TC

https://datacenter.stix.i4ds.net/view/list/fits this aligns with the request TC question why there are many L1A files with the same vesion @drhlxiao

https://datacenter.stix.i4ds.net/view/data-request/list this aligns with the request TC

STIXCore product: solo_L1_stix-sci-xray-spec_20220124T025410-20220124T043046_V01_2201240014-56454.fits this aligns with the request TC

2201249786:

this is the other RID where a duplication for RID 2201240033 where detected

IOR https://datacenter.stix.i4ds.net/view/ior/overview/694

it says: Start Time - seconds (PIX00072) = 696340696 2022-01-24T11:59:59 Tmax (PIX00078) = 219000 (21900 s) = 6h

DataCenter: https://datacenter.stix.i4ds.net/view/list/bsd this aligns with the request TC

https://datacenter.stix.i4ds.net/view/list/fits this aligns with the request TC

https://datacenter.stix.i4ds.net/view/data-request/list this aligns with the request TC

STIXCore product: solo_L1_stix-sci-xray-spec_20220124T120004-20220124T180507_V01_2201249786-60605.fits this aligns with the request TC

Conclusion

for the very same time period the Spectrogram was requested twice with different RIDs 2201240033and 2201249786

at some places the datacenter is mixing up the 2 connected RIDs 2201240033and 2201240014 from STICCore point of view it looks sound to me

[samaloney]

@nicHoch @ennosigaeus can we close this?