Node Use Policy

Home » General Information » Policy » Node Use Policy

EPIC Node Usage and Support Policy

Version 1.0

2/27/2019

Introduction

This policy clarifies the responsibilities and support provided by the EPIC Instrument Center for node experiments utilizing the EarthScope/EPIC node pool. The primary drivers behind this policy are as follows:

  • To clarify EPIC and the PI’s roles and responsibilities for nodal experiments

  • To assure that the shipping and import/export of these instruments adheres to the appropriate dangerous goods regulations based on mode of transport.

  • To assure that we can continue to control EarthScope EPIC assets and scheduling of equipment under our control.

As with all experiments, there may be specific details that fall into the grey areas not specifically addressed by this policy and we are willing to work with PI’s to assure their experiments are successful as long as these three primary directives are met.

Motivation

The use of nodal instruments is of growing interest to the seismological community and EarthScope is responding to community’s desires by increasing the capabilities of the EPIC pool with a planned growth of nodal instrumentation and ancillary support equipment. At the same time, the community is investing their own funds in procuring their own small nodal pools and scheduling their own experiments along with supporting their colleagues by providing instrumentation and support for others. These joint community experiments are both performed independent of EarthScope resources, and in collaboration with EarthScope scheduled experiments. There are a number of issues that complicate the role that EarthScope (PIC) plays in the support of these joint experiments due to a number of issues. Namely:

  • Nodes are considered “dangerous goods” (DG) for shipping purposes due to the presence of the integrated Lithium battery power system. Therefore, neither EarthScope, nor independent node owners can legally ship each other’s nodes. EarthScope has obtained IATA certification that allows us ship the DG items. It is a requirement that each node owner also have this certification both on the shipping and receiving end.
  • EarthScope nodes are on an extremely tight schedule and are in high demand. The only way to ensure that the nodes are not delayed for future experiments is to control all aspects of experiment planning, data handling and recharge/functional validation for the EarthScope owned nodes.
  • Data handling will be required for nodes checked out from the EarthScope pool due to the infrastructure required to accomplish this task, which is not the standard for other pool equipment. Therefore, we will be adding work to our staff for this particular task. We cannot take on the additional task of handling data from other node systems whose numbers and quality we cannot control.
  • Although EarthScope nodes can be offloaded and recharged with community owned infrastructure, the turn-around time for this task would be beyond the control of EarthScope and therefore, could put future experiments at the risk of delay or receipt of non- functional equipment.

Due to these issues, we provide the following policy on how we will handle nodal experiment support (shipping, data handling, node validation and programming of field computers (HHT’s)) for those potential experiments using the following combinations of EarthScope and community resources:

  1. 100% EarthScope supported,
  2. partially support with EarthScope and community resources, or
  3. fully operated with community resources.

100% EPIC equipment

Shipping

  1. EPIC will arrange all outgoing EPIC equipment shipments with assistance from PI.
  2. Experiments in the Lower 48 require freight for all outbound and inbound shipments. This circumvents most Dangerous Goods (DG) issues.
  3. For all foreign and domestic experiments not in the lower 48, return shipment of EPIC nodes to PIC will require PIs to either:
    1. Get certification as a lithium battery shipper and provide documentation of certification to PIC before the experiment leaves our dock.
    2. Contract a Hazmat Shipping Service.
    3. Have one of EPIC’s certified staff present to help with return shipment at the PI’s expense (travel costs only – no salary)
  4. Antarctic experiments using Portable pool nodes are allowed no more than 5 weeks logistics pre- and post PI’s on/off ice dates.
  5. As is standard policy – Shipping costs are the responsibility of the PI.

HHT, Node and Data Handling

  1. EPIC will set up the experiment program/project with assistance and verification from PI. This requires access to the node support ancillary equipment
  2. EPIC will provide a sufficient number of programmed HHTs for deployment.
  3. After return of the nodes to EPIC, EPIC will offload the nodes and the PI will be given a copy of the raw fcnt data files on PI-supplied drives (EPIC will provide required drive specifications). This will occur within 3 weeks of receipt of nodes or drives whichever is thelatter.
  4. PI will supply the following information for conversion to PH5: Experiment Mobilization Form, a complete “Final Layout” Spreadsheet with corresponding KMZ file, and a Shot Position Spreadsheet if it’s an active source experiment
  5. EPIC will create a PH5 data volume for archive with DMC in a timely manner (~3 weeks after receipt of information requested in item iv)
  6. PI is responsible for verifying completeness of data archived at DMC. EPIC will remove/delete waveform data from the PIC server once fcnt files are delivered to PI and PI has verified DMC archive or after 6 months from offload if not previously verified by PI.
  7. Any ancillary costs associated with large data volumes will be the responsibility of the PI – as per DS Data policy.

Mixed EPIC and PI equipment

Shipping

  1. EPIC and non-EPIC nodes must remain separate shipments.
  2. PI is responsible for all shipping arrangements of non-EPIC owned nodes to and from field.
  3. EPIC will arrange all outgoing EPIC equipment shipments with assistance from PI.
  4. Experiments in the Lower 48 require freight for all outbound and inbound shipments. This circumvents most DG issues.
  5. For all foreign and domestic experiments not in the lower 48, return shipment of EPIC nodes to PIC will require PIs to either:
    1. Get certification as a lithium battery shipper and provide documentation of certification to PIC before the experiment leaves our dock.
    2. Contract a Hazmat Shipping Service.
    3. Have one of EPIC’s certified staff present to help with return shipment.
  6. Antarctic experiments using Portable pool nodes are allowed no more than 5 weeks logistics pre- and post PI’s on/off ice dates.
  7. As is standard policy – Shipping costs are the responsibility of the PI.

HHT, Node and Data Handling

  1. EPIC will coordinate with the PI to set up project on respective servers (i.e. EPIC will be responsible for EPIC nodes & HHT, PI will be responsible for non-EPIC nodes and HHT).
  2. EPIC will provide sufficient, programmed HHT for EPIC owned nodes. PI is expected to provide sufficient, programmed HHT for non- EPIC nodes.
  3. After return of the EPIC nodes to EPIC, EPIC will offload the nodes and the PI will be given a copy of the fcnt data files on PI-supplied drives (EPIC will provide required drive specifications). This will occur within 3 weeks of receipt of nodes or drives whichever is thelatter.
  4. PI will provide EPIC an Experiment Mobilization Form, a complete “Final Layout” Spreadsheet with corresponding KMZ file, and Shot Position Spreadsheet if it’s an active source experiment.
  5. EPIC will create PH5 data volume for the EPIC nodes for archive with DMC in a timely manner (~3 weeks of receipt of the information requested in iv.).
  6. PI is responsible for offload and creation of the PH5 data volume for non- EPIC nodes.
  7. EPIC will provide software and data archiving support to PI for PH5 creation and integration with EPIC created PH5 data volume.
  8. PI is responsible for verifying completeness of data archived at DMC
  9. EPIC will remove/delete waveform data from the PIC server once fcnt files are delivered to PI and PI has verified DMC archive or after 6 months from offload if not previously verified by PI.
  10. The PI may choose or be required (depending on their funding) to archive the data from the non-EarthScope nodes at the EarthScope Data Management Center (DMC). If this is the case, the PI will follow the EarthScope Data Services policies for acceptance and formats into the archive.
  11. Any ancillary costs associated with large data volumes will be the responsibility of the PI – as per DS Data policy.

No EPIC equipment

  1. EPIC will provide, via GitHub, software and instructions for converting fcnt files into a PH5 data volume.
  2. All other aspects of the node experiment support are the responsibility of the PI.
  3. The PI may choose or be required (depending on their funding) to archive the data from their experiment at the DMC. If this is the case, the PI will follow the EarthScope Data Services policies for acceptance and formats into the archive.
  4. Any ancillary costs associated with large data volumes will be the responsibility of the PI – as per DS Data policy.
  • Printer-friendly version
  • PDF version
Related categories:
EarthScope Primary Instrument Center
New Mexico Tech
100 East Road, Socorro, NM 87801