search

hapi-server / tasks

Task tracker
0 stars 0 forks source link

Jon and Sandy - SuperMAG #9

Open rweigel opened 4 months ago

rweigel commented 4 months ago

My recollection is that a few years ago, we were a few weeks from Sandy having his server running.

jvandegriff commented 3 months ago

Sandy - cloud storage is filling up, so SuperMAG given deadline; SuperMAG PI is now on-board with doing this!!

We will use 1 min data and SuperMAG programmer will help.

rweigel commented 3 months ago

Another motivation to getting this done: We are starting to see people build HAPI servers that pass through SuperMAG data:

https://spaceweather.knmi.nl/viewer/?layout=omni_ae_intermagnet#start=2017-09-07T06:00:00&end=2017-09-09T18:00:00

Really, the source should be a SuperMAG HAPI server.

jvandegriff commented 1 month ago

Update from Sandy - approval from PI; now just technical issues left (where to run server); will also add to HelioCloud

rweigel commented 1 month ago

Notes:

  1. The fill of 0 is wrong: see https://hapi-server.org/servers-dev/#server=SuperMAG&dataset=data_AAA&parameters=N&start=2020-01-01T00:00Z&stop=2020-01-03T00:00Z&return=image&format=hapiplot&style=svg; it should be 999999.0
  2. A sample time range of one month for 1-minute data is too long - a data request takes > 30 seconds. Most browsers timeout after ~120 seconds, and I can imagine an overloaded server often failing on a sample request. I suggest 3 days.
  3. The data in the dataset name is redundant (because I know it is data ...) and makes matching with INTERMAGNET tedious. Eventually, we'll have WDC data that does not use data. However, this is what SuperMAG uses internally, so perhaps it is better to be internally consistent.
  4. Will non-baseline removed data be available from SuperMAG? Or, will the removed baseline be provided in metadata? Sometimes one wants to know this when comparing.