Describe the solution you'd like
In the design of the web interface and the back-end interface we haven't given any thought on the best schema for handling data from federates when they are iterating at a single tilmestep. I suspect the database will just add new records for pubs/subs at a single timestep but presenting this, even in a table view, can be confusing and less than helpful.
Federates do have an understanding of the integration count but this value is unique to the federate. This can be useful information in sorting out the data but because it is not a unique value, it isn't enough in itself to help sort out the order of the data being exchanged between federates.
Describe the solution you'd like In the design of the web interface and the back-end interface we haven't given any thought on the best schema for handling data from federates when they are iterating at a single tilmestep. I suspect the database will just add new records for pubs/subs at a single timestep but presenting this, even in a table view, can be confusing and less than helpful.
Federates do have an understanding of the integration count but this value is unique to the federate. This can be useful information in sorting out the data but because it is not a unique value, it isn't enough in itself to help sort out the order of the data being exchanged between federates.