Skip to Content
Last modified by KB on 2025/08/12 11:59
From version 1.2
edited by robert
on 2024/01/23 11:45
Change comment: There is no comment for this version
To version 20.1
edited by KB
on 2025/08/12 11:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.robert
1 +XWiki.Kimberley
Content
... ... @@ -4,33 +4,48 @@
4 4  
5 5  = Planning Your Experiment =
6 6  
7 -zzz
7 +== Checking Instrument Availability ==
8 8  
9 -== Sub-paragraph ==
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 -zzz
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 -== Sub-paragraph ==
13 +Lead times will depend on the scale and configuration of your project, delivery logistics, and staff availability.
14 14  
15 -zzz
15 +Applicants are strongly encouraged to make early contact or expressions of interest.
16 16  
17 -
17 +== Submitting an Application to the ANSIR Committee ==
18 18  
19 -
19 +Applications (a.k.a., Proposals) are received by AuScope on behalf of the ANSIR Committee. Successful proposals are then forwarded to the relevant support facility. 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 AuScope's National Geophysics Program Manager.
20 20  
21 -= Applying for an FDSN Network Code =
21 +The recommended process is:
22 22  
23 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
23 +~1. Check availability;
24 24  
25 -== Sub-paragraph ==
25 +2. Review the terms and conditions: [[ANSIR: Terms and Conditions;>>https://www.auscope.org.au/ansir-terms]]
26 26  
27 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
27 +3. Review the application form: [[ANSIR: Application Form>>https://www.auscope.org.au/ansir-application-form]];
28 28  
29 +4. Contact our Scientific Coordinator to schedule an initial consultation;
29 29  
30 -= Organising Data & Metadata =
31 +5. Submit your application.
31 31  
32 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
33 33  
34 -== Sub-paragraph ==
34 +If accepted, you will be directed back to our Scientific Coordinator to finalise requirements and logistics. This will be formalised in a Supply Agreement between your institute and ANU.
35 35  
36 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
36 +
37 += Metadata =
38 +
39 +Recording proper metadata is critical to seismic experiments. ANSIR-supported experiments are required to keep field logs (recommended long term station and nodal deploy field logs (links)) and recommended to back these up digitally in multiple locations. When submitting your data, 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.
40 +
41 += Applying for an FDSN Network Code =
42 +
43 +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.
44 +
45 +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.
46 +
47 +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!//**
48 +
49 += Accessing your data at AusPass =
50 +
51 +See [[FDSN Guide>>doc:Data.FDSN Guide.WebHome]] for tips and advice on using python and ObsPy to access our server.
example_metadata.txt
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +2.7 KB
Content
... ... @@ -1,0 +1,46 @@
1 +# AKL-HR Node Array (AHNA) code X5
2 +CITE: Name, Name, and Name. (2023). A Node Array [Data set]. International Federation of Digital Seismograph Networks. https://doi.org/10.7914/8jxr-7029
3 +
4 +#SITE START END LAT LONG ELEV SPS RECORDER S/N SENSOR S/N PROPERTY,LOCALITY,COUNTRY COMMENTS
5 +
6 +# INSTALL
7 +AKL01 20-05-2023T00:00 30-06-2023T00:00 -37.0471 175.5245 75 250 SSNODE_C 590001950 SSNODE_5S 590001950 "Te Puru,Hauraki,NZ"
8 +AKL02 20-05-2023T00:00 30-06-2023T00:00 -36.7476 175.5026 70 250 SSNODE_C 590001943 SSNODE_5S 590001943 "Coromandel Town,Hauraki,NZ"
9 +AKL03 20-05-2023T00:00 30-06-2023T00:00 -36.9694 175.5020 98 250 SSNODE_C 590002068 SSNODE_5S 590002068 "Te Mata,Hauraki,NZ"
10 +AKL05 19-05-2023T19:00 22-02-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001957 SSNODE_5S 590001957 "South Head South,Auckland,NZ" "site was disturbed"
11 +AKL06 19-05-2023T19:00 30-06-2023T00:00 -37.2459 175.3426 34 250 SSNODE_C 590001930 SSNODE_5S 590001930 "Back Miranda,Auckland,NZ"
12 +AKB05 02-05-2023T00:37 30-06-2023T00:00 -36.6651 175.4800 63 250 TSAWR TS085A TRILL120 4875 "Colville,Hauraki,NZ"
13 +
14 +# SERVICE 1
15 +AKL05 22-02-2023T00:00 30-06-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001999 SSNODE_.2S 590001999 "South Head South,Auckland,NZ" "swapped node to shortperiod"
16 +
17 +
18 +
19 +
20 +################### ANY LINE BEGINNING WITH # will be commented! Comments are good!
21 +
22 +
23 +# NOTES
24 +# the start/end time is not critical, but good to have. what IS critical are the times of instrument changes as this potentially affects response information
25 +# to mark equipment changes, add a new line with an updated start date (e.g. AKL05 above)
26 +# can use tabs or spaces, but spaces tend to look nicer. formatting ultimately doesn't matter too much so long as there is any sort of "white space" between the fields
27 +# if you don't know a serial number, put 999. if you don't know the elevation, put 0
28 +# for Nodes, put the same serial number for both Recoder and Sensor (since they are the same!)
29 +
30 +
31 +# EXAMPLE INSTRUMENT LABELS
32 +#LPR200 = ANU LPR-200 logger (beige box)
33 +#TSAWR = ANU TerraSAWR logger (yellow box)
34 +
35 +#TRILL120 = Trillium Compact 120s
36 +#TRILL20 = Trillium Compact 20s
37 +#TRILL120PH = Trillium Compact 120s PostHole
38 +#CMG6TD = Guralp 6TD
39 +#CMG3ESP = Guralp 3ESP
40 +#3DLITE = Lenarrtz 3D-LITE
41 +
42 +#SSNODE_C = output was in COUNTS (there is also SSNODE_MV, if you (accidentally!) output to millivolts etc)
43 +#SSNODE_5S = broadband (can also use SSNODE_BB)
44 +#SSNODE_.2S = shortperiod (can also use SSNODE_SP)
45 +
46 +#it doesn't matter too much what you use for equipment labels, so long as they are consistent and otherwise defined somewhere in the comments!