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
It makes no sense to require definition of basePath if there is no particle or mesh data. External field data has its own path called externalFieldPath.
Proposal: Make basePath required only if there is particle or mesh data.
The text was updated successfully, but these errors were encountered:
Thank you for the proposal.
I think an alternative with could be to just allow to define the meshesPath to ./, which means it is the exact basePath without further nesting.
External field data has its own path called externalFieldPath.
I don't understand this, that's not in the base standard.
@ax3l I'm sorry I'm not following what you are proposing. What does meshesPath have to do with this? My understanding was that meshes were for internal fields and not external fields.
It makes no sense to require definition of
basePath
if there is no particle or mesh data. External field data has its own path calledexternalFieldPath
.Proposal: Make
basePath
required only if there is particle or mesh data.The text was updated successfully, but these errors were encountered: