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
core.log and sim.log just contain the logging information from the core and the simulator. You can use --debug to get more verbose logs, but then the files get large very quickly
We should somehow what the user excected to see, what the information tell, and so on. Mhhh. probably generated a README.md into each scenario, printing a template README decsribe all files and what inside each file? Just brainstorming how to support the user of the simulator ...
The "result set" for
make fast
is "somehow" minimal:003-profile-core
core.log
contains just thestarting DMPR core
message, but then the simulation should be longer or b) shorter (because nothing is generated)profile
is binary data - nobody will know what it is ...002-disappearing-node
core.log
is senselesssim.log
is fine. But I miss the video (see other issue)The text was updated successfully, but these errors were encountered: