NetQASM outputs its logs to the log directory in two directories: a timestamped directory and a LAST directory, containing the logs of the last run.
Some time ago a change was reverted. After reverting the _instrs logs were renamed from <node>_instrs.yaml back to <app>_instrs.yaml (see PR #48).
This change does not seem to be working fully. If you run an application the timestamped folder contains the correctly named logs (<app>_instrs.yaml) while the LAST directory still contains the wrongly named logs (<node>_instrs.yaml). This causes issues for us in the quantum network explorer since we look in the LAST directory to find the logs of the last run.
To reproduce this I have added an application: application.zip. After running this example with NetQASM I have two log directories. The timestamped one containing the files alice_instrs.yaml and bob_instrs.yaml, and the LAST directory containing the files delft_instrs.yaml and leiden_instrs.yaml. I ran this example with NetQASM 0.13.1 and the new 0.13.2.
NetQASM outputs its logs to the log directory in two directories: a timestamped directory and a LAST directory, containing the logs of the last run.
Some time ago a change was reverted. After reverting the _instrs logs were renamed from
<node>_instrs.yamlback to<app>_instrs.yaml(see PR #48).This change does not seem to be working fully. If you run an application the timestamped folder contains the correctly named logs (
<app>_instrs.yaml) while the LAST directory still contains the wrongly named logs (<node>_instrs.yaml). This causes issues for us in the quantum network explorer since we look in the LAST directory to find the logs of the last run.To reproduce this I have added an application: application.zip. After running this example with NetQASM I have two log directories. The timestamped one containing the files
alice_instrs.yamlandbob_instrs.yaml, and the LAST directory containing the filesdelft_instrs.yamlandleiden_instrs.yaml. I ran this example with NetQASM 0.13.1 and the new 0.13.2.