Thanks again for making Rocketsled publicly available
When using it, it seemed to me that it would be useful for the user, in some cases, to have a look at all the x values that were tried during the optimization (and at the corresponding y values).
It is certainly possible to obtain this info from the database (by extracting the spec info of each workflow), but this might be cumbersome.
Would it make sense to add a method to the MissionControl class, that returns the x and y values as numpy arrays (of shape (n_launches, n_x), (n_launches, n_y) for instance)?
Thanks again for making Rocketsled publicly available
When using it, it seemed to me that it would be useful for the user, in some cases, to have a look at all the x values that were tried during the optimization (and at the corresponding y values).
It is certainly possible to obtain this info from the database (by extracting the spec info of each workflow), but this might be cumbersome.
Would it make sense to add a method to the MissionControl class, that returns the x and y values as numpy arrays (of shape (n_launches, n_x), (n_launches, n_y) for instance)?
Thanks again for making Rocketsled publicly available
When using it, it seemed to me that it would be useful for the user, in some cases, to have a look at all the x values that were tried during the optimization (and at the corresponding y values).
It is certainly possible to obtain this info from the database (by extracting the spec info of each workflow), but this might be cumbersome.
Would it make sense to add a method to the MissionControl class, that returns the x and y values as numpy arrays (of shape (n_launches, n_x), (n_launches, n_y) for instance)?