Skip to Content
Last modified by KB on 2025/08/12 11:59
From version 4.1
edited by KB
on 2025/06/16 15:19
Change comment: There is no comment for this version
To version 7.1
edited by robert
on 2025/06/17 16:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kimberley
1 +XWiki.robert
Content
... ... @@ -8,7 +8,7 @@
8 8  
9 9  Availability for most of our passive seismic instruments is regularly updated  [[HERE>>https://docs.google.com/spreadsheets/u/3/d/e/2PACX-1vRyK1XUmYMXIHt-5BWhoZchVtMD3Lxtgqi69WoxEuWgUem7Ob_VzdG8L1OHlBjD7g/pubhtml]] .
10 10  
11 -The linked table shows instruments that are actively maintained (i.e., that we aim to keep in field-ready condition). These are the instruments we most often supply. However, if this selection doesn't suit your research needs or is in short supply, please let us know ~-~- we may have alternate solutions. Your feedback also helps us maintain relevant infrastructure collections for the research community.
11 +The linked table shows instruments that are actively maintained (i.e., that we aim to keep in field-ready condition). These are the instruments we most often supply. However, if this selection doesn't suit your research needs or is in short supply, please let us know ~-~- we may have alternate solutions. Your feedback also helps us maintain a relevant infrastructure collection for the research community.
12 12  
13 13  Lead times will depend on the scale of your project, delivery logistics, and staff availability. Applicants are therefore encouraged to make early contact, so we aware of your plans.
14 14  
... ... @@ -34,8 +34,8 @@
34 34  
35 35  = Applying for an FDSN Network Code =
36 36  
37 -Each seismic network needs its own 2-character Network Code to help differentiate it. These must be registered from FDSN [[HERE>>https://www.fdsn.org/networks/request/]] or you can ask us to help with this. It is **CRITICAL** to ensure that you select the correct year range for your experiment, because if your project ends up with data outside of your originally requested network code then you may be forced to use two separate network codes. If you are operating a multi-year network with a planned end of, say, 2027, we recommend adding a year of "buffer" to your registration request e.g. request a code from 2024-2028. Remember, //you can always trim the timespan of your network, but it is often impossible to add to it!//
37 +Each seismic network needs its own 2-character Network Code to help differentiate it. These must be registered from FDSN [[HERE>>https://www.fdsn.org/networks/request/]] or you can ask us to help with this. It is **CRITICAL** to ensure that you select the correct year range for your experiment, because if your project ends up with data outside of your originally requested network code then you may be forced to use two separate network codes. If you are operating a multi-year network with a planned end of, say, 2027, we recommend adding a year of "buffer" to your registration request e.g. request a code from 2024-2028. Remember, **//you can always trim the timespan of your network, but don't assume you can add to it!//**
38 38  
39 39  = Accessing your data at AusPass =
40 40  
41 -See [[HERE>>http://auspass.edu.au/xwiki/bin/view/Data/Tutorials/]] for tips and advice on using python and obspy to access our server.
41 +See [[HERE>>http://auspass.edu.au/xwiki/bin/view/Data/Tutorials/]] for tips and advice on using python and ObsPy to access our server.