JIVE Wiki

User Tools

Site Tools

Trace:
sfxc-guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
sfxc-guide [2023/07/10 14:31] – keimpemasfxc-guide [2023/07/10 14:38] (current) – keimpema
Line 1: Line 1:
 ====== SFXC User's Manual ====== ====== SFXC User's Manual ======
-==== Mark Kettenis ==== +Mark Kettenis (JIVE)
-JIVE +
-Table of Contents+
  
-1. Running the SFXC correlator +===== Chapter 1. Running the SFXC correlator =====
-2. The correlator control file +
-3. Preparing your VEX file +
-4. Post-processing +
-List of Examples +
- +
-1.1. Rank file example +
-2.1. Control file example +
- +
-====== Chapter 1. Running the SFXC correlator ======+
 SFXC is an MPI application. This means that running it is somewhat dependent on the MPI implementation installed on your system. The instructions here are for OpenMPI, which currently seems to be the most popular Open Source MPI implementation for Linux systems. SFXC is an MPI application. This means that running it is somewhat dependent on the MPI implementation installed on your system. The instructions here are for OpenMPI, which currently seems to be the most popular Open Source MPI implementation for Linux systems.
  
Line 28: Line 17:
 The remainder of the processes will be assigned to correlations processes. A single slot is sufficient for these processes. The remainder of the processes will be assigned to correlations processes. A single slot is sufficient for these processes.
  
-**Example 1.1. Rank file example**+=== Example 1.1. Rank file example === 
 <code> <code>
 rank 0=head slot=0 rank 0=head slot=0
Line 45: Line 35:
 SFXC will automatically generate delay tables using the CALC10 code that's included in the distribution. The CALC10 needs some additional input files to do its work. These are the JPL Solar System Ephemeris (''DE405_le.jpl''), ocean loading information (''ocean.dat'') and antenna tilt (''tilt.dat''). It expects to find these in a directory pointed to by the CALC_DIR environment variable. A copy of ''DE405_le.jpl'' as well as ocean loading and antenna tilt information for many antennas that co-observe with the European VLBI Network (EVN) can be found in ''sfxc/lib/calc10/data'' in the source distribution. SFXC will automatically generate delay tables using the CALC10 code that's included in the distribution. The CALC10 needs some additional input files to do its work. These are the JPL Solar System Ephemeris (''DE405_le.jpl''), ocean loading information (''ocean.dat'') and antenna tilt (''tilt.dat''). It expects to find these in a directory pointed to by the CALC_DIR environment variable. A copy of ''DE405_le.jpl'' as well as ocean loading and antenna tilt information for many antennas that co-observe with the European VLBI Network (EVN) can be found in ''sfxc/lib/calc10/data'' in the source distribution.
  
-====== Chapter 2. The correlator control file  ======+===== Chapter 2. The correlator control file  =====
  
 The correlator control file uses the JavaScript Object Notation (JSON) format. It is constumary to give these files a ''.ctrl'' extension. The correlator control file uses the JavaScript Object Notation (JSON) format. It is constumary to give these files a ''.ctrl'' extension.
Line 81: Line 71:
 An example of a control file is given below: An example of a control file is given below:
  
-**Example 2.1. Control file example**+=== Example 2.1. Control file example ===
 <code> <code>
 { {
Line 111: Line 101:
 </code> </code>
  
-====== Chapter 3. Preparing your VEX file ======+===== Chapter 3. Preparing your VEX file =====
  
 Some information needs to be provided in the VEX file that is typically not emitted by the scheduling software. It is essential that you have $CLOCK and $EOP blocks. Some of the tools distributed with SFXC also use the $TAPELOG_OBS block. We recommend that in the $EOP block you provide entries at a 24 hour intervals and have an additional entry for the day before and the day after the observation. All these blocks need to be properly referenced; from the $GLOBAL block for $EOP and from the $STATION block fot the $CLOCK and $EOP blocks. Some information needs to be provided in the VEX file that is typically not emitted by the scheduling software. It is essential that you have $CLOCK and $EOP blocks. Some of the tools distributed with SFXC also use the $TAPELOG_OBS block. We recommend that in the $EOP block you provide entries at a 24 hour intervals and have an additional entry for the day before and the day after the observation. All these blocks need to be properly referenced; from the $GLOBAL block for $EOP and from the $STATION block fot the $CLOCK and $EOP blocks.
Line 138: Line 128:
 [2] https://safe.nrao.edu/wiki/bin/view/VLBA/Vex2doc#A_61_36THREADS_61_Block [2] https://safe.nrao.edu/wiki/bin/view/VLBA/Vex2doc#A_61_36THREADS_61_Block
  
-====== Chapter 4. Post-processing ======+===== Chapter 4. Post-processing =====
  
 As with the Mark4 hardware correlator, SFXC output is converted into an AIPS++/CASA MeasurementSet using the j2ms2 program. Create a directory with the name of experiment as given in the VEX file. Copy the VEX file into this directory and rename it to experiment.vix where experiment is again the name of the experiment as given in the VEX file. As with the Mark4 hardware correlator, SFXC output is converted into an AIPS++/CASA MeasurementSet using the j2ms2 program. Create a directory with the name of experiment as given in the VEX file. Copy the VEX file into this directory and rename it to experiment.vix where experiment is again the name of the experiment as given in the VEX file.
sfxc-guide.1688999487.txt.gz · Last modified: 2023/07/10 14:31 by keimpema