Skip to content
 
NEST Simulator Documentation recording_backend_screen – Recording backend screen - Write data to the terminal Description ~~~~~~~~~~~ When initially conceiving and debugging simulations, it can be useful to check recordings in a more ad hoc fashion. The recording backend screen can be used to dump all recorded data onto the console for quick inspection. The first field of each record written is the node ID of the neuron the event originated from, i.e., the source of the event. This is followed by the time of the measurement, the recorded floating point values, and the recorded integer values. The format of the time field depends on the value of the property time_in_steps. If set to false (which is the default), time is written as one floating point number representing the simulation time in ms. If time_in_steps is true, the time of the event is written as a value pair consisting of the integer simulation time step and the floating point offset in ms from the next grid point. .. note:: Using this backend for production runs is not recommended, as it may produce huge amounts of console output and considerably slow down the simulation. Parameter summary ~~~~~~~~~~~~~~~~~ precision controls the number of decimal places used to write decimal numbers to the terminal. time_in_steps A boolean (default: false) specifying whether to print time in steps, i.e., in integer multiples of the resolution and an offset, rather than just in ms.
Type to start searching
    NEST Simulator
    logo
    • NEST docs home
    • Model directory
    NEST Simulator
    • USAGE
    • Install
    • Tutorials and Guides
    • Examples
    • Models
    • Python API
    • Glossary
    • NEST performance results
    • Cite NEST
    • License
    • COMMUNITY
    • Contact us
    • Contribute
    • What's new?
    • NEST Homepage
    • Acknowledgments
    • RELATED PROJECTS
    • NEST Desktop
    • NESTML
    • NESTGPU
    • NEST NEAT
    • Show Source

    recording_backend_screen – Recording backend screen - Write data to the terminal Description ~~~~~~~~~~~ When initially conceiving and debugging simulations, it can be useful to check recordings in a more ad hoc fashion. The recording backend screen can be used to dump all recorded data onto the console for quick inspection. The first field of each record written is the node ID of the neuron the event originated from, i.e., the source of the event. This is followed by the time of the measurement, the recorded floating point values, and the recorded integer values. The format of the time field depends on the value of the property time_in_steps. If set to false (which is the default), time is written as one floating point number representing the simulation time in ms. If time_in_steps is true, the time of the event is written as a value pair consisting of the integer simulation time step and the floating point offset in ms from the next grid point. .. note:: Using this backend for production runs is not recommended, as it may produce huge amounts of console output and considerably slow down the simulation. Parameter summary ~~~~~~~~~~~~~~~~~ precision controls the number of decimal places used to write decimal numbers to the terminal. time_in_steps A boolean (default: false) specifying whether to print time in steps, i.e., in integer multiples of the resolution and an offset, rather than just in ms.¶

    "Previous" mcculloch_pitts_neuron – Binary deterministic neuron with Heaviside activation function
    "Next" recording_backend_mpi – Recording backend mpi - Send data with MPI Description ~~~~~~~~~~~ .. admonition:: Availability This stimulation backend is only available if NEST was compiled with support for MPI. The mpi recording backend sends collected data to a remote process using MPI. There are two ways to set the MPI port. If both are set, option A has precedence 1. The address is supplied via the recording backends “mpi_address” status property. 2. The name of the MPI port to send data to is read from a file for each device configured to use this backend. The file needs to be named according to the following pattern: :: {data_path}/{data_prefix}{label}/{node_id}.txt The data_path and data_prefix are global kernel properties, while label is a property of the device in question and node_id its node ID. This path can only be set outside of a Run context (i.e. after Prepare() has been called, but Cleanup() has not). Communication Protocol ~~~~~~~~~~~~~~~~~~~~~~ The following protocol is used to exchange information between both MPI processes. The protocol is described using the following format for the MPI messages: (value, number, type, source/destination, tag) 1) Prepare : Connection of MPI port included in the port_file (see below) 2) Run begin: Send at each beginning of the run (true, 1, CXX_BOOL, 0, 0) 3) Run end : Receive at each ending of the run (true, 1, CXX_BOOL, 0, 0) 4) Run end : Send shape of the data of the run (shape, 1,INT, 0, 0) 5) Run end : Send data of the data of the run (data, shape, DOUBLE, 0, 0) 6) Run end : Send at each ending of the run (true, 1, CXX_BOOL, 0, 1) 7) Cleanup : Send at this en of the simulation (true, 1, CXX_BOOL, 0, 2) Data format ~~~~~~~~~~~ The format of the data sent is an array consisting of (id device, id node, time is ms).
    Impressum | Data Protection | Attribution for images and icons