-
Notifications
You must be signed in to change notification settings - Fork 1
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
Odin simulation workflow loader and hardcoded choppers. #50
base: main
Are you sure you want to change the base?
Conversation
35641c5
to
3373436
Compare
48e5ddd
to
fbcd34f
Compare
abc9270
to
d79d60c
Compare
0c1ae84
to
c65afcc
Compare
d79d60c
to
d919f67
Compare
(cherry picked from commit 280da3c341cf0d8bf0b7a46a51586b564da33b72)
d919f67
to
b18fc87
Compare
" .values\n", | ||
" )\n", | ||
" return sc.vectors(dims=['event'], values=var, unit='m')\n" | ||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel that most of the code at the start of this notebook should be part of a submodule in the package, and not in the notebook?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, as Søren wanted everything before December,
I thought we don't have time to make them as a module, write test and documentation.
Also, McStas format is not stable at the moment so I didn't want to start working on a mcstas IO module...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
" return RectInfo(x_range.min(), x_range.max(), y_range.min(), y_range.max())\n", | ||
"\n", | ||
"\n", | ||
"class MergedRectanglesTool(ToggleTool):\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also think this code should go in a submodule, so we can just simply import the tool in the notebook?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. Then I'll do that in plopp maybe...?
Related to #20, #26 and Related to one of milestone for p6
The notebook is for P6 milestone report so it is expected to be refactored and integrated into a module as a reusable workflow.
#56 should be merged first.