Skip to Content
Last modified by KB on 2025/08/12 11:59
From version 11.1
edited by KB
on 2025/06/30 10:02
Change comment: There is no comment for this version
To version 17.1
edited by santi
on 2025/07/22 18:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kimberley
1 +XWiki.santi
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 a relevant infrastructure collection 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). However, if this selection doesn't suit your research needs or is in short supply, please let us know ~-~- we may have other options. 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 encouraged to make early contact, so we aware of your plans.
14 14  
... ... @@ -18,16 +18,19 @@
18 18  
19 19  The recommended process is:
20 20  
21 -~1. Check availability
21 +~1. Check availability;
22 22  
23 -2. Review the terms and conditions: [[ANSIR: Terms and Conditions>>https://www.auscope.org.au/ansir-terms]]
23 +2. Review the terms and conditions: [[ANSIR: Terms and Conditions;>>https://www.auscope.org.au/ansir-terms]]
24 24  
25 -3. Review the application form: [[ANSIR: Application Form>>https://www.auscope.org.au/ansir-application-form]]
25 +3. Review the application form: [[ANSIR: Application Form>>https://www.auscope.org.au/ansir-application-form]];
26 26  
27 -4. Contact our Scientific Coordinator to schedule a consultation
27 +4. Contact our Scientific Coordinator to schedule a consultation;
28 28  
29 -5. Submit your application
29 +5. Submit your application.
30 30  
31 +
32 +If accepted, you will be directed back to our Scientific Coordinator to finalise requirements and logistics.
33 +
31 31  = Metadata =
32 32  
33 33  Recording proper metadata is critical to seismic experiments. You should be taking in-field logs (recommended long term station and nodal deploy field logs (links)) and backing these up digitally in multiple locations. When submitting your data to ANU, we also require a copy of this metadata to be submitted in the [[standard ANU metadata format>>attach:example_metadata.txt]] as a simple text file. This is how we can quickly generate FDSNxml metadata files for use in AusPass, our seismic data server.
... ... @@ -34,12 +34,12 @@
34 34  
35 35  = Applying for an FDSN Network Code =
36 36  
37 -The FDSN requires that each seismic network have a 2-character Network Code assigned to it to differentiate it when shared online. These must be registered from FDSN [[HERE>>https://www.fdsn.org/networks/request/]] or you can ask us to help with this. Ideally you will need a network code before you plan on saving any data as this network code is part of the metadata stored in the file's data.
40 +The FDSN assigns a 2-character Network Code to each seismic network to differentiate them when shared online. Register your Network Code with FDSN [[HERE>>https://www.fdsn.org/networks/request/]]before saving any data ~-~- it will be part of the metadata stored in your network file data.
38 38  
39 -Because the network code is only 2 characters, often they are reused and can only be differentiated by the range of years they are in operation. Thus, 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 the range assigned to your requested network code then you might be forced to use two separate network codes to accommodate this "spill over". For example, if you are operating a multi-year network with a planned end during 2027, we recommend adding a year of "buffer" to your registration request in the event that your experiment is delayed or extends further than you originally planned, e.g. request a code that spans 2024-2028.
42 +Because the 2-character codes are often reused, networks are also differentiated by the range of years they are in operation. It is therefore **CRITICAL** to register a year range that will accommodate your entire experiment. If you are operating a multi-year network we recommend adding a year to buffer your registration in case of delays or extensions (e.g., for a project planned from Feb 2024 to April 2027, please register 2024-2028). This range can be trimmed when your project has ended.
40 40  
41 -Remember, **//you can always trim the timespan of your network, but don't assume you can add to it!//**
44 +If your project ends up with data outside of the assigned range, and the code has already been reused for another network, you will need an additional code for the "spill over". Remember: **//You can always trim the timespan of your network, but you may not be able to add to it!//**
42 42  
43 43  = Accessing your data at AusPass =
44 44  
45 -See [[HERE>>http://auspass.edu.au/xwiki/bin/view/Data/Tutorials/]] for tips and advice on using python and ObsPy to access our server.
48 +See [[FDSN Guide>>doc:Data.FDSN Guide.WebHome]] [[HERE>>http://auspass.edu.au/xwiki/bin/view/Data/Tutorials/]] for tips and advice on using python and ObsPy to access our server.