You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request: high priority
The tag output_type should have an option to log just the metrics and nothing else. In the documentation, the option of summary describes it as "a CSV file of the mission metrics will be created" but it also generates the frames.bin, shapes.bin, and a few other files which for some missions can take up more memory space than needed.
I'm running hundreds of thousands of scrimmage missions in a bulk simulation runs which can fill up memory space with these extra files that are generated. I've only handled this issue by reading in the metrics as they are generated and deleting the logs as I go. I would also appreciate if there are any other suggestions for a better way of handling collecting large amounts of metrics without bogging down the memory space as generating these logs and deleting it right after is not ideal.
The text was updated successfully, but these errors were encountered:
Feature request: high priority
The tag output_type should have an option to log just the metrics and nothing else. In the documentation, the option of summary describes it as "a CSV file of the mission metrics will be created" but it also generates the frames.bin, shapes.bin, and a few other files which for some missions can take up more memory space than needed.
I'm running hundreds of thousands of scrimmage missions in a bulk simulation runs which can fill up memory space with these extra files that are generated. I've only handled this issue by reading in the metrics as they are generated and deleting the logs as I go. I would also appreciate if there are any other suggestions for a better way of handling collecting large amounts of metrics without bogging down the memory space as generating these logs and deleting it right after is not ideal.
The text was updated successfully, but these errors were encountered: