Can you describe the use case here? Typically these files would save to the same directory as the output structure. Also, does this change fit Capytaine's new internal hydrostatics? I haven't run Capytaine since hydrostatics was included, so I'm not sure if that output format has changed at all

Use case is you can have your hydrostatics files saved in a separate location now (if you want to). This is handy for organizing data on a project I'm currently working on that has a lot of floating bodies.

@dav-og That makes sense, seems like a benefit to allow this for cases with many floating bodies. Last request, can you update the logic to make it backwards compatible with no sub directory input? This will only be an easy work around until other arguments are added to readCapytaine, but might be worthwhile until then

Adam

Thanks for the update! Approved and I will merge if there's nothing else.

Thanks @akeeste for pointing out the backwards compatibility.
I reviewed this PR yesterday and all looks good.

For the future, I think we could introduce a 'config' argument, that will be a structure for all bemio settings.
Although, the bemio related functions have arguments for changing parameters like time steps etc. it would be much easier to allow user to define fields in a config structure. That way the function call will not change if future parameters for bemio runs are introduced. Also, bemio calls for all BEM software will have the same arguments.

@salhus Agreed. I'd like to do this for the plotting functions too. I made a project card for Q2 to address this topic https://github.com/WEC-Sim/WEC-Sim/projects/58#card-86577803