Thank you for the update and the support. Looking forward to it.
Try now, it should be up and running again.
Thank you so much, indeed it is working.
Hello, unfortunately it seems to have stopped again.
Hi, the server seems to be down again. Thank you for the continued support.
Thanks for letting us know. The NDS2 server seems to be working now. Please let us know if you continue to experience problems. You can also try OSDF to see if that’s more reliable.
Thank you, I’ll check it out. Also, I’m fetching aux files and not sure if it was updated but last time I tried OSDF does not support fetching those.
@Shan909 That’s strange. The aux data should be on OSDF. If you are not able to find it there, please let me know, and I will take a look. It would help me if you can give me a specific example of what channel and times you are trying to find.
I think the issue is aux data is only on nds, not sure.
Added the code in attachment but it’s simply osdf in a user friendly wrapper.
Here the channel is L1:ASC-X_TR_A_NSUM_OUT_DQ
time segments:
start,end
1256663958,1256673192
1256673691,1256756709
1256766682,1256772748
1256775368,1256798949
@Shan909 The aux data are available on OSDF. Here is an example command that finds a data file:
$ gw_data_find -r datafind.gwosc.org -o L -t L1_AUX_AR1 --latest -u osdf
osdf:///gwdata/O4a/AUX/AUX_AR1/L1/L-L1_AUX_AR1-13894/L-L1_AUX_AR1-1389428288-63.gwf
In python, this seems to work:
>>> import os
>>> import requests_pelican as rp
>>> from gwdatafind import find_urls
>>> url = find_urls( "L", "L1_AUX_AR1", 1256663958, 1256673192, urltype='osdf', host="https://datafind.gwosc.org")
>>> print(url)
So, I tried it using 04 data you mentioned and it works well although I am not sure which auxillary file AUX_AR1 is never saw the name before.
However, for the older runs (03) it still does not work
The frame type is documented on the docs page:
This data release has frame type AUX_AR1 and is available via OSDF allowing to select and download the data. To launch large dataset jobs on a computing cluster one can use HTCondor .
Access for O3 aux data are documented here:
Some sample python code is included on the page:
import os
import requests_pelican as rp
from gwdatafind import find_urls
url = find_urls( "H", "H1_AUX_AR1 ", 1240559616, 1240559626, urltype='osdf', host="https://datafind.gwosc.org")
with open(os.path.basename(url[0]), mode="wb") as file:
file.write(rp.get(url[0]).content)
Hmm…so through OSDF I first need to find channels from frame types and then fetch it.
I’ll try that one soon but if you are involved in the development process, wouldn’t it be more simpler to have a channel name tab also as a optional parameter to run like the nds approach. Just a suggestion and thanks for the redirect. I did not know about the OSDF working for aux channels come to think of it maybe I didn’t see it on the webpage earlier either. Is this a new feature?
I’m sorry, OSDF is not developed in-house. You can read more about the team that supports it and offer suggestions to them at the link below. We did recently update our GWOSC documentation regarding how to access GW data via OSDF, so it makes sense that this seems new. I would welcome any suggestions you can offer for how to make the documentation more clear and easy to use.
Ah go it. I am going to add osdf support now to my GWeasy app too. Thanks for all the information, hopefully OSDF won’t trip off as much as nds.

