Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Fast Test Results #22

Open
hgn opened this issue Sep 18, 2017 · 4 comments
Open

Make Fast Test Results #22

hgn opened this issue Sep 18, 2017 · 4 comments

Comments

@hgn
Copy link
Member

hgn commented Sep 18, 2017

The "result set" for make fast is "somehow" minimal:

  • 003-profile-core

    • core.log contains just the starting DMPR core message, but then the simulation should be longer or b) shorter (because nothing is generated)
    • sim.log is similar
    • profile is binary data - nobody will know what it is ...
  • 002-disappearing-node

    • the image is great, no really I like it :-)
    • core.log is senseless
    • sim.log is fine. But I miss the video (see other issue)
@reisub-de
Copy link
Contributor

Profile generates a pstats file from the python profiler. I will make that more clear.

002 should generate a video, see #20

@reisub-de
Copy link
Contributor

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

@hgn
Copy link
Member Author

hgn commented Sep 19, 2017

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 ...

@reisub-de
Copy link
Contributor

Good idea, will take a look at that

reisub-de pushed a commit to reisub-de/dmpr-simulator that referenced this issue Oct 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants