Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Current »

Click on the expander buttons below for more information.

Data access

 What are the data proprietary periods?

  • Observations requested through Director’s Discretionary Time (DDT) typically have a proprietary period of three months. PIs may also choose to waive the proprietary period.

  • Open Time proposals typically have a proprietary period of 12 months after the last observation has been obtained.

  • Proprietary periods vary for Large Survey Projects (LSPs) depending on observing seasons.

 I am a co-investigator on a proposal. How do I get access to the data?

It is the responsibility of the the Principal Investigator (PI) to assign access to their team, using the Keycloak administration console.

Please see the group management guide for instructions on how to do this.

 The science products in the SARAO repository are not loading.

If you see a message saying ‘Loading bucket contents…’ which goes nowhere, please check whether you have ad-blockers or pop-up blockers running.

Spectral line

 Is Doppler tracking available?

MeerKAT does not apply Doppler corrections. We advise using the CASA task CVEL to apply corrections after bandpass calibration is applied.

Observing

 How do I set up my observation for polarisation calibration?

See discussion on polarisation calibration.

 Can I request night time observations only to minimise RFI?

The MeerKAT RFI environment is dominated by satellite-based RFI and as such is largely independent of time of day. Solar interference may play a factor in observations of low-surface brightness HI and this may be justification for night-only observations.

The Observation Planning Tool (OPT)

 What are the 'pool resources' listed in the OPT when I am setting up instrument parameters for my observation?

These specify the systems that will receive data from the digitisers. Standard observations must have the correlator/beamformer (CBF) and the science data processor (SDP). Optional resources are the user-supplied equipment (USE), which capture data commensally.

Data reduction

 My strong spectral line has been flagged by SDP. What do I do?

Do not apply all flags when converting to MS format. ingest_rfi flags any outliers and usually catches lines such as Galactic HI and masers. In this case you should only use --static, --cam, --data_lost

Flag descriptions are here.

 Why is so much of my data flagged?

  • Calibration for the preceding cal scans failed, thus causing subsequent target scans to be flagged. This was quite frequent in the early development phases of the pipeline.

Do not apply SDP flags when setting up the conversion to measurement set, or disable the flags in CASA.

 What sort of compute resources will I need to reduce and analyse my data?

See the page on compute requirements.

  • No labels