the isr roadmap in the coopeus project - · pdf filethe isr roadmap in the coopeus project ......

The ISR roadmapThe ISR roadmapin the COOPEUS projectin the COOPEUS project

Anders Tjulin, EISCAT Scientific [email protected]

EISCAT User Meeting 2015 ISR Roadmap 2

What is COOPEUS?

● A programme connecting research infrastructures– Supported by the EU (FP7) in cooperation with NSF– September 2012 – August 2015

● Five areas of research– Space weather– Carbon observations– Biodiversity– Ocean observations– Solid earth dynamics

● Partner institutes in USA and Europe


COOPEUS structure

● Analytical phase– Commonalities and gaps connected to data and information

collection and sharing within the communities in Europe and across the Atlantic are identified

● Intermediate synthesis phase– Collect the results– Identify case studies

● Domain specific user scenarios● Event specific user scenarios

● Study phase– Case studies carried out

● Final synthesis phase– Define roadmap for future cooperation


COOPEUS Task 2.5

● Task 2.5: Construction of joint atmospheric radar roadmap– In this task, we will develop a common approach to facility scheduling

and operating procedures, which will optimize the co-ordination of EU and US facilities at an observational level, in order to ensure best value return from the entire observing network.

– We will also develop a common understanding of the priorities for future facility developments and upgrades.

– The output will be a joint roadmap for ISR observations including recommendations for how a common scheduling and operational philosophy can be implemented and a list of prioritized future tasks to improve the co-ordination of existing facilities and the interoperability of their data.

– In this way, we will map out a co-ordinated approach for the international community, extending beyond the lifetime of the project.


The roadmap

● The finished roadmap is available for download– www.coopeus.eu/progress/

● Based on discussions with COOPEUS project partners and e-infrastructure operators

● Recommendations for incoherent scatter radar operations

http://www.coopeus.eu/progress/


Why do we need ISR observations?

● ISR technique is one of the most powerful methods for detailed measurements of the ionosphere– Electron density– Electron and ion temperatures– Bulk flow

● Observing connection between Sun and Earth– Solar-terrestrial physics– Space weather


Trends in ISR research

● Generally increasing interest in environmental sciences– International collaborations– Global coverage

● Space weather prediction– Improved dependence on modelling of effects

from space weather events● Continuous observations

– Moving from campaigns towards observatories● Larger data volumes and quicker data access

requirements


The global context

● The ionosphere ignores political borders

● Observations should ideally also ignore political borders


ISR systems in the world

● There are more than fifteen facilities in the world capable of ISR observations

● COOPEUS involves EISCAT and US systems


ISR facilities in the COOPEUS project

EISCAT UHF

EISCAT VHF

EISCAT UHFEISCAT Svalbard Radar

EISCAT_3D

Millstone Hill

Jicamarca

Arecibo

JicamarcaSondrestrom

PFISR

RISR


ISR facilities in the COOPEUS project

Operator Owner Funder First operation

EISCAT UHF EISCAT EISCAT SA, STEL, NIPR, CRIRP, NFR, NERC, VR 1981

EISCAT VHF EISCAT EISCAT SA, STEL, NIPR, CRIRP, NFR, NERC, VR 1985

EISCAT Svalbard Radar EISCAT EISCAT SA, STEL, NIPR, CRIRP, NFR, NERC, VR 1996

EISCAT_3D EISCAT EISCAT TBC TBC

Millstone Hill MIT MIT NSF 1960

Jicamarca Radio Observatory Cornell University Instituto Geofisico del Perú NSF 1961

Arecibo Observatory SRI International NSF NSF 1963

Sondrestrom SRI International NSF NSF 1983

PFISR SRI International NSF NSF 2007

RISR SRI International NSF (University of Calgary) NSF (University of Calgary) 2009 (2011)


The need for a roadmap

● Large variations in equipment and organisation– Harmonisation needed for efficient collaboration

● Increasingly more data intensive– Common strategy for data formats and access– Must be in line with capabilities and standards set by e-infrastructure providers

● EISCAT_3D to be constructed “soon”– Defining system for the future– Ready for future standards


Areas for collaborative efforts

● Identified areas where collaborative efforts suitable and of great value– Definition of data levels– Data format– Access– Standard operations– Non-standard operations– Training and education– Outreach


Data levels● Data levels used in ISRs were identified earlier in the COOPEUS project

– Presented at EISCAT_3D Users Meeting 2014● Level 1: Lowest accessible level of digital sampled and filtered data

– System-specific– Not normally stored

● Level 2: Correlated data products– Data exchange– Used for long-term storage

● Level 3: Physical parameters– Most requested from users

● (Level 4: Graphical visualisations and published articles)● Sufficient metadata needed for all levels

Receiver

RF signal voltageV(t)

Correlated productsV(t)V*(t+T)

Plasma parametersn, Te, Ti, ...

Correlator Fitter


Data format

● Level 1– Traditionally no standards have been needed– Storing these data requires standards– HDF5 used at AMISR and Millstone Hill a starting point

● Level 2– Largest harmonisation effort needed here– HDF5 is a starting point

● Level 3– Standard data container used by the Madrigal database– Should be upgraded/changed to handle EISCAT_3D data

Common Features of Correlated ISR Data Formats

System metadata

Antenna – specified for TX and RX systems separately:

Site reference coordinates

Number of beams

For each beam:

Beam shape

Beam pointing

Beam pointing coordinate system

For each feed polarisation:

Feed bandpass shape

Feed amplitude and phase calibration

Transmitter:

TX frequency time history

Modulation envelope time history:

Amplitude

Phase

Peak power

Average power

Receiver:

Number of channels

For each channel:

Association of that channel with antenna beam / feed / polarisation, or with sampled TX channel

Receiver centre RF frequency

Receiver final frequency (=0 for baseband data)

Receiver effective impulse response / bandpass shape (amplitude and phase)

Receiver timing:

RF blank interval, if present

Attenuation time history

Noise calibration diode injection system parameters (if present):

Timing of noise calibration pulse injection

Absolute noise calibration pulse power

Receiver amplitude and phase calibration

Receiver noise temperature

Correlated product data

Number of lag profiles

For each lag profile:

Associated receiver channels (different if cross-correlation, same if auto-correlation)

Associated transmitted modulation

Radar ambiguity function: delay × lag × range

Time average interval

Start offset from leading edge of TX pulse

Range sampling vector

Lag sampling vector

Lag product matrix (range × lag)

Lag product variance matrix (range × lag)

DC offset as a function of range


Access

● Access to data– Madrigal exists now for level 3 data

● Other data portals could also be offered

– Data available through requests– Technical solutions under discussion in several projects

● Access to facilities– Technical aspects– Access rights


Standard operations

● All facilities have a set of standard modes● Increased value if these could be combined for global view of

ionosphere● Continuous, or near continuous, operation of great value to study

trends through long data series– Such operations only possible from a limited number of ISR facilities– Financing the high costs for continuous operations is a big issue


Non-standard operations

● The incoherent scatter radar world days are coordinated observations by the ISRs of the world– About 20 per year– Scheduled well in advance– Coordinated through the Incoherent Scatter Working Group of URSI– Data available as soon as possible

● Protocols for unplanned coordinated observations are needed– For example following large space weather events


Training and education

● ISR operator community is very small● Training of engineers should be coordinated

– Not automatic – projects for this have to be defined● Education of users should be coordinated

– International ISR courses are organised regularly


Outreach

● The ISR operator community should have a common voice– Limited to commonalities

● Protection of radio frequencies● Stressing the importance of continuous observations

● Projects to streamline this coordination should be identified


Communication channels

● The COOPEUS project has shown us:– where coordination can be made– how difficult coordination is in practice

● Identify channels to discuss the needed harmonisation actions– URSI ISWG meetings (every three years) a possible starting point

● An arena for coordination needs to be organised, and funded, in a sustainable fashion


Recommendations on organisational level (part 1)

● Identify a sustainable arena that is suitable for discussions on international coordination.

● Follow the COOPEUS joint data policy.● Work towards the introduction of persistent data identifiers.● Agree on a level 2 data standard and make sure that it is suitable for long term storage.● Make sure that the level 3 data produced are fit to be used in common data portals by

connecting sufficient amount of meta-data.● Prepare protocols for migration of data, both to new formats and new depositories.● Open for possibilities to implement a common scheduling and operational philosophy.


Recommendations on organisational level (part 2)

● Continue the incoherent scatter world days planning as it is done now.● Make sure that protocols exist for event-driven observations, where one

facility/organisation can suggest operation of other facilities/organisations.● Make efforts to expand the ISR community through high visibility and good

connection to academic institutions.● Identify projects for training and exchange of radar operation engineers.● Continue the incoherent scatter radar summer schools.● Identify projects for coordinating outreach efforts.


Recommendations on facility level

● Aim for using harmonised level 1 data format for the internal data processing.

● Ensure that data migration activities follow strategy protocols.● Use the ENVRI reference model as a guideline for the data framework.● Ensure that standard operating modes are defined for producing long-

term continuous data sets that can be used to observe ionospheric changes over time.

● Open for activities involving exchange of engineers for training purposes.


Finally...

● Coordination activities should not end at the end of the project

the isr roadmap in the coopeus project - · pdf filethe isr roadmap in the coopeus project ......

Documents