Skip to Content
Last modified by robert on 2024/11/12 16:42
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 Check [[HERE>>https://docs.google.com/spreadsheets/u/3/d/e/2PACX-1vRyK1XUmYMXIHt-5BWhoZchVtMD3Lxtgqi69WoxEuWgUem7Ob_VzdG8L1OHlBjD7g/pubhtml]]
10
11 == Submitting an Application to the ANSIR Committee ==
12
13 TBA
14
15 = Metadata =
16
17 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.
18
19 = Applying for an FDSN Network Code =
20
21 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!//
22
23 = Accessing your data at AusPass =
24
25 See [[HERE>>http://auspass.edu.au/xwiki/bin/view/Data/Tutorials/]] for tips and advice on using python and obspy to access our server.