Skip to content
Snippets Groups Projects

Simulator loader RR input

Open Alejandro Homs Puron requested to merge simulator-loader-rr-input into develop

Add rank_in_filename_format_implies_rr_input option:

  • If true, each recv ignore the RR settings and read the input sequentially

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • requested review from @debionne

  • There is no issue associated with this PR so I am guessing that this allows to use input files that are already "sliced in a RR way" (output of Lima2) so that they are read without skipping params.xfer.time_slice.stride (aka sequentially).

    Why make this implicit and gives another meaning/function to the format string parameter? Also { rank } (mind the whitespaces) is a perfectly valid format string but will be missed by find("{rank}"). IMHO, we should no try to guess anything from the format string.

    What is missing in the client to provide the proper simulator reader parameters for this use case? I guess this is due to the current limitation of having a single set of parameters for all receivers...

  • This functionality allows using the Simulator in Round-Robin (RR), full frame dispatch mode by sourcing files that were already generated by multiple data receivers in RR configuration. It avoids the creation of a sequential, interlaced file stream, either directly or through a VDS (master) file

Please register or sign in to reply
Loading