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

issues selecting particular sciunit artifact on repeat #6

Open
2 tasks
nicole-brewer opened this issue Jul 24, 2024 · 1 comment
Open
2 tasks

issues selecting particular sciunit artifact on repeat #6

nicole-brewer opened this issue Jul 24, 2024 · 1 comment
Assignees

Comments

@nicole-brewer
Copy link

nicole-brewer commented Jul 24, 2024

tldr

  • bug fix: recompile a more up to date version of sciunit to be included in Flinc
  • feature request: the ability to select certain sciunit artifacts when running the repeat kernel

Use Case

I'm using FLINC to run and repeat several different notebooks. Audit and repeat work just fine when I execute the first notebook. I shut down the repeat kernel and move on to a totally different second notebook. The audit kernel works just fine once again, but the repeat kernel fails. @sranasir suggested this is because the repeat kernel is defaulting to using the e1 artifact instead of using the e2 artifact.

Feature Request

The ideal scenario would to be able to select the sciunit artifact of my choosing. So I could select e2 when selecting a kernel. For my use case, I wouldn't mind if I only had this option programmatically.

Bug Fix

The ideal workaround would be to use sciunit to delete the e1 kernel in between executing the first notebook with the repeat kernel and executing the second notebook with audit kernel.

sciunit rm e1

@sranasir suggested that this should be possible with the most up to date version sciunit. That there was a bug related the execution counter so that even after e1 is deleted using sciunit rm e1, that the next run in the audit kernel produces an e2 instead of e1 again, which causes some discrepancy.

Current Workaround

Therefore, the actual current workaround is to manually delete the audit kernel using

rm -rf ~/sciunit/audit-kernel/
./install.sh

NOTE: My install.sh (in the chameleon branch of my personal fork) is slightly modified, but I think the behavior should be the same in both

@sranasir
Copy link
Contributor

Thank you for creating the issue as discussed. Meanwhile, I have updated the README so only one notebook per Sciunit project is run with audit and repeat kernels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants