new_bbs

*Master Side of the recipe *

class lofarpipe.recipes.master.new_bbs.new_bbs

This bbs recipe still uses the oldstyle bbs with global control New versions will have stand alone capability

The bbs recipe coordinates running BBS on a group of MeasurementSets. It runs both GlobalControl and KernelControl; as yet, SolverControl has not been integrated.

Arguments

A mapfile describing the data to be processed.

Recipe inputs

Parameters:
  • control_exec(ExecField) BBS Control executable (ExecField)
  • data_mapfile(StringField) Full path to the mapfile containing the names of the data files that were processed by BBS (clobbered if exists) (StringField)
  • db_host(StringField) Database host with optional port (e.g. ldb001:5432) (StringField)
  • db_key(StringField) Key to identify BBS session (StringField)
  • db_name(StringField) Database name (StringField)
  • db_user(StringField) Database user (StringField)
  • gvds(StringField) Path for output GVDS file (StringField)
  • instrument_mapfile(FileField) Full path to the mapfile containing the names of the instrument model files generated by the parmdb recipe (FileField)
  • kernel_exec(ExecField) BBS Kernel executable (ExecField)
  • parset(FileField) BBS configuration parset (FileField)
  • sky_mapfile(FileField) Full path to the mapfile containing the names of the sky model files generated by the sourcedb recipe (FileField)

Recipe outputs (job.results[parameter])

Parameters:mapfile(FileField) Full path to a mapfile describing the processed data (FileField)

*node Side of the recipe *

class lofarpipe.recipes.nodes.new_bbs.new_bbs(job_id, host, port)
run(executable, infiles, db_key, db_name, db_user, db_host)

Depricated functionality

Previous topic

DPPP

Next topic

get_metadata

This Page