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
Currently, we only return min and max for the different axes in a GridBackend. We should consider two things:
Provide an additional Sequence[str] determining what type of axes it is,
e.g., log, linear, something_else. It should appear in the docs what is possible.
Provide additional attribute axes_values. If this is present discard
above's logic so that this axes_values are used.
I think the latter point would even provide the possibility to use non-uniform grids.
The updated protocol would be something like this:
No. It still applies. I wanted to include information from the backend if the axis type is not linear. This is currently not addressed, and we should have this somewhere in the backend if we want to have a logarithmic radius simulation 😉 .
Currently, we only return
min
andmax
for the different axes in aGridBackend
. We should consider two things:Sequence[str]
determining what type of axes it is,e.g.,
log
,linear
,something_else
. It should appear in the docs what is possible.axes_values
. If this is present discardabove's logic so that this
axes_values
are used.I think the latter point would even provide the possibility to use non-uniform grids.
The updated protocol would be something like this:
The text was updated successfully, but these errors were encountered: