Planning Your Experiment
Checking Instrument Availability
Availability for most of our passive seismic instruments is regularly updated HERE .
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.
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.
Submitting an Application to the ANSIR Committee
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.
The recommended process is:
1. Check availability
2. Review the terms and conditions: ANSIR: Terms and Conditions
3. Review the application form: ANSIR: Application Form
4. Contact our Scientific Coordinator to schedule a consultation
5. Submit your application
Metadata
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 as a simple text file. This is how we can quickly generate FDSNxml metadata files for use in AusPass, our seismic data server.
Applying for an FDSN Network Code
Each seismic network needs its own 2-character Network Code to help differentiate it. These must be registered from FDSN HERE 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!
Accessing your data at AusPass
See HERE for tips and advice on using python and ObsPy to access our server.