You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is rather inconvenient, since those NaNs cause issues in pypesto.visualize.sampling.sampling_prediction_trajectories later on:
File/venv/lib/python3.11/site-packages/pypesto/visualize/sampling.py:901, insampling_prediction_trajectories(ensemble_prediction, levels, title, size, axes, labels, axis_label_padding, groupby, condition_gap, condition_ids, output_ids, weighting, reverse_opacities, average, add_sd, measurement_df)
887_plot_trajectories_by_condition(
888summary=summary,
889condition_ids=condition_ids,
(...)
898grouped_measurements=grouped_measurements,
899 )
900elifgroupby==OUTPUT:
-->901_plot_trajectories_by_output(
902summary=summary,
903condition_ids=condition_ids,
904output_ids=output_ids,
905axes=axes,
906levels=levels,
907level_opacities=level_opacities,
908labels=labels,
909variable_colors=variable_colors,
910average=average,
911add_sd=add_sd,
912grouped_measurements=grouped_measurements,
913 )
915iftitle:
916fig.suptitle(title)
File/venv/lib/python3.11/site-packages/pypesto/visualize/sampling.py:435, in_plot_trajectories_by_output(summary, condition_ids, output_ids, axes, levels, level_opacities, labels, variable_colors, average, add_sd, grouped_measurements)
432# Timepoints must match, or `upper_data` will be plotted at433# some incorrect time points.434ifnot (np.array(t_lower) ==np.array(t_upper)).all():
-->435raiseValueError(
436"The timepoints of the data for the upper and lower "437"percentiles do not match."438 )
439# Plot a shaded region between the data that correspond to the440# lower and upper percentiles.441ax.fill_between(
442t_lower_shifted,
443lower_data,
(...)
448lw=0,
449 )
ValueError: Thetimepointsofthedatafortheupperandlowerpercentilesdonotmatch.
I see no harm in using the actual timepoints instead of NaNs in the case of failed simulations and would suggest doing that.
The text was updated successfully, but these errors were encountered:
Currently, when
AmiciPredictor
processes a failed simulation, it sets the timepoints to NaN:pyPESTO/pypesto/predict/amici_predictor.py
Lines 375 to 377 in 82b7d5d
This is rather inconvenient, since those NaNs cause issues in
pypesto.visualize.sampling.sampling_prediction_trajectories
later on:I see no harm in using the actual timepoints instead of NaNs in the case of failed simulations and would suggest doing that.
The text was updated successfully, but these errors were encountered: