search

AuScope / seed-vault

MIT License
1 stars 0 forks source link

Implement STATION step for Event Based Workflows #23

Closed bmotevalli closed 10 hours ago

bmotevalli commented 1 month ago

Below is from .cfg file. UI elements for each parameter. For reference, refer to example .cfg files provided by Rob.

client -> Dropdown list. Also, it might be better to push the client selection to the settings page as well instead of putting it in the event or station pages. (check with @filefolder)

inventory -> check with @filefolder how to get this. for now ignore it.

force_station -> separate entries for network and station (for simplicity, for now use textbox. later, we may want to use dropdowns, if it makes sense to do so)

exclude_stations -> separate entries for network and station (for simplicity, for now use textbox. later, we may want to use dropdowns, if it makes sense to do so)

starttime, endtime -> currently we only support date. Check with @filefolder to see if datetime is required.

startbefore,startafter,endbefore,endafter -> Check with @filefolder what are these parameters. Are they datetime or just time intervals. If they are timeintervals, what are their units. Ignore these parameters for now until it is clarified.

network, station, location, channel -> Use textbox for now.

geomtry -> use Map

includerestricted -> checkbox -> Check with @filefolder to get an understanding

level -> dropdown -> looks to be limitted choices. Check with @filefolder to understand what are the possible options.

filefolder commented 2 weeks ago

sorry i must have missed this post before. i think most are clear now but a few maybe are not

client -> Dropdown list. Also, it might be better to push the client selection to the settings page as well instead of putting it in the event or station pages. (check with @filefolder)

would like to suggest that all defaults be "EARTHSCOPE"

includerestricted -> checkbox -> Check with @filefolder to get an understanding

this is a good checkbox to have.. and by default it should be unchecked. this keeps people from trying (and failing) to download data they don't have access to. if people are intentionally searching for embargoed data then they can click this.

level -> dropdown -> looks to be limitted choices. Check with @filefolder to understand what are the possible options.

options are station (just the station position), channel (everything in station and now also information about the available channels), and response (everything in channel but now including poles and zeros to remove instrument sensitivity). As a general rule, I would just default to channelat all times as the download size between station and channel is fairly small. We won't need response information in this project.

NTaherifar commented 5 days ago

"I’ve added the include_restricted checkbox with a default unchecked setting, as suggested. Additionally, I included the level dropdown with the options of Channel and Station, defaulting to Channel as recommended.

@filefolder, For the client dropdown, I encountered an issue with setting EARTHSCOPE as the default due to an error (The FDSN service shortcut 'EARTHSCOPE' is unknown). To avoid this, I’ve set IRIS as the default client for now.

filefolder commented 5 days ago

thanks-- for now, IRIS and EARTHSCOPE are the same, but IRIS was renamed to EARTHSCOPE last year and future versions of obspy may not keep routing it. the solution is to update obspy to version 1.4.1 (which should be a requirement for the package also)