Replies: 1 comment
-
That sounds reasonable. The logic is here https://github.com/QCoDeS/Qcodes/blob/master/qcodes/logger/logger.py#L312 it should be possible to extend the filename with either a counter, thread/processid or something similar to that |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, Qcodes saves the command history for each jupyter session running in a single file - usually stored at ~/.qcodes/command_history.log. When a session is restarted, the command history continues appended to the same file.
It might be preferrable to have a separate command_history log file created for each new jupyter session. In particular when running multiple consoles (e.g. if running analysis in one and measurement in the other), to have a separate history for each one rather than having them interleaved, making it difficult to reconstruct a session.
Beta Was this translation helpful? Give feedback.
All reactions