Skip to content
Snippets Groups Projects
  1. Jan 22, 2025
  2. Dec 16, 2024
  3. Nov 20, 2024
  4. Nov 14, 2024
  5. Oct 01, 2024
  6. Sep 12, 2024
  7. Jul 12, 2024
  8. Jun 25, 2024
  9. Jun 21, 2024
  10. Jun 18, 2024
  11. Jun 17, 2024
    • John Frankland's avatar
      Several enhancements to mesytec_receiver_mfm_transmitter: · c0455d1b
      John Frankland authored
       * no arguments are obligatory, it is possible to launch without any arguments,
         if required files are in the working directory.
       * usage:
      
      Optional arguments:
        -c [ --config_dir ] arg (=.)          directory in which to look for config
                                              files
        --config_file arg (=transceiver.cfg)  file with default argument values (in
                                              config_dir)
        -h [ --mvme_host ] arg (=localhost)   url of host where mvme-zmq is runnning
        -m [ --crate_map ] arg (=crate_map.dat)
                                              name of file containing crate map
        -y [ --mvlc_config ] arg (=mvlc_crateconfig.yaml)
                                              yaml file with exported MVLC config
        -s [ --data_source ] arg (=0)         data source id [0-255] for MFM frame
                                              headers
        -p [ --mvme_port ] arg (=5575)        port number of mvme-zmq host
        -z [ --zmq_port ] arg (=9097)         port on which to publish MFM data
        -b [ --buffer_size ] arg (=64)        buffer size to use (in kilobytes)
        -t [ --timeout ] arg (=1000)          timeout for buffer flush (in
                                              milliseconds)
       * mvme_host is now 'localhost' by default
       * non-default names for 'crate_map' and 'mvlc_config' file can be used
       * it is possible to run just by giving the --config_dir argument, if this
         directory contains a transceiver.cfg file with all required arguments
         and the 'crate_map' and 'mvlc_config' files
       * when TGV timestamps are incorrect (bad status), we no longer print a warning
         for every event; the 'bad rate' is shown as the percentage of all events
         since the last status update which had bad timestamps
       * PLUS: now in living colour...!
      c0455d1b
  12. Mar 21, 2024
  13. Mar 13, 2024
  14. Feb 23, 2024
  15. Feb 10, 2024
  16. Feb 09, 2024
  17. Feb 02, 2024
  18. Feb 01, 2024
  19. Jan 15, 2024
Loading