← Back to team overview

opensand team mailing list archive

New environment plane: Defined probes and events

 

Hello all,

Since the new environment plane is approaching completion, we “ported”
the current defined probes, events and errors into the new system, but
we think they should be partially redefined:
 - Some current probes and events are not used at all in the system ;
   other seem to be used but actually seem non-functional. See the
   attached file for details. Which ones should be kept?

 - The new environment plane support disabled-by-default probes and
   debugging events ; both are not sent over the network by default and
   should not have a perceptible performance hit. These items could be
   added to some parts of the simulation program to help debugging.

 - Only probes defined in blocks which are actually used for a
   simulation will be displayed in the manager’s interface. This means
   that only probes useful for a specific configuration will be
   displayed; thus, configuration-specific probes can be added without
   risking cluttering the user interface.

 - Some probes are put directly into a core library (for instance, the
   ones integrated into the DAMA library), which is relatively
   invasive. They should probably be moved out into a component block.

Thus, we are requesting feedback on which probes and events should go
into the OpenSAND platform alongside with the new environment plane.

Regards,
Vincent Duvert

Attachment: probes_usage.xls
Description: MS-Excel spreadsheet


Follow ups