-
Notifications
You must be signed in to change notification settings - Fork 38
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
Errors in checking peak_position availability using select_runs #388
Comments
The following doesn't work. (And the error does not go away by rerun it as described)
|
The example of course should have been: st.set_context_config(
dict(
check_available=(
'peak_positions_gcn',
'peak_positions_mlp',
'peak_positions_cnn',
'peak_basics')
))
some_mode=st.select_runs(run_mode='some_mode', exclude_tags=('messy', 'bad'))
mask_available = some_mode.peak_positions_gcn_available.values
some_mode_with_pp=some_mode[mask_available]
some_mode_with_pp |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The select_runs function was behaving weirdly:
Every first time
st.select_runs(run_mode, available = 'peak_positions')
is run, with or without specified run_mode, it will return an error like:The error message persists as the
available
argument is switched among 'peak_positions', 'peak_position_bla'. However if now I add in (a valid)run_mode
argument the error message goes away and the output dataframe looks nice.It is the same if I begin with a
run_mode
input, see the error message, and then delete therun_mode
argument. After the error is gone I can add back therun_mode
with no problem.Also it is the same if I begin with one
run_mode
input, see the error message, and change to another run_mode.The problem can be solved even if after seeing the error message I run exactly the same code in another block in my notebook...
The text was updated successfully, but these errors were encountered: