Skip to Content
Last modified by Kimberley on 2025/06/30 10:38
Show last authors
1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
4
5 = Planning Your Experiment =
6
7 == Checking Instrument Availability ==
8
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
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
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
15 == Submitting an Application to the ANSIR Committee ==
16
17 Applications (a.k.a., Proposals) are received and forwarded by AuScope's National Geophysics Program Manager. Eligibility and access procedures are summarised on AuScope's website (see links below). If you have any questions not addressed by these resources, you are welcome to contact us or the NGPM.
18
19 The recommended process is:
20
21 ~1. Check availability;
22
23 2. Review the terms and conditions: [[ANSIR: Terms and Conditions;>>https://www.auscope.org.au/ansir-terms]]
24
25 3. Review the application form: [[ANSIR: Application Form>>https://www.auscope.org.au/ansir-application-form]];
26
27 4. Contact our Scientific Coordinator to schedule a consultation;
28
29 5. Submit your application.
30
31
32 If accepted, you will be directed back to our Scientific Coordinator to finalise requirements and logistics.
33
34 = Metadata =
35
36 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.
37
38 = Applying for an FDSN Network Code =
39
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.
41
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.
43
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!//**
45
46 = Accessing your data at AusPass =
47
48 See [[HERE>>http://auspass.edu.au/xwiki/bin/view/Data/Tutorials/]] for tips and advice on using python and ObsPy to access our server.