This is an old revision of the document!
This page describes how to set DiFX up to allow “native” Mark5 correlations. This page does not cover the use of fuseMK5. In the “nativemk5” approach described here, an mpifxcorr datastream process runs on each Mark5 unit, meaning that mpifxcorr must be compliled in a manner that can be run on the Mark5 units.
Compatibility of the Conduant streamstor drivers severely limits the choice of Linux kernels. The supported kernel versions depend on the exact version of the driver (the SDK version number) that is used. SDK version 8.2 or later are suggested as earlier versions have known stability issues related to the way the streamstor cards are accessed by DiFX. As of this writing (Nov 18, 2010) only 32-bit kernels are supported. See mixing architectures to see how to configure a cluster to support a mixture of 32 bit and 64 bit members of a cluster running mpifxcorr. Note that mixing different streamstor SDK versions across the cluster is possible, but for each a separately compiled version of the mpifxcorr binary will be required due to differences in library requirements. Differences between major SDK releases (e.g., SDK8 and SDK9) usually also have API-level changes. Currently mpifxcorr can be compiled against either SDK8 or SDK9 series.
Mark5 units as distributed by Conduant or Haystack Observatory typically have a fully installed software development kit. It may be desirable to reinstall the OS and/or upgrade the SDK. Please follow the guidelines for SDK installation provided by Conduant.