dzalkind
dzalkind
I pushed a fix in #302.
1. We use the chain [properties defined by the MoorDyn tool](https://github.com/NREL/MoorPy/blob/018e976d63f2b5d6c8e1ba26f87d5221590886e3/moorpy/MoorProps_default.yaml#L43). Input requirements are defined in the schema, [here are the mooring line properties](https://github.com/WISDEM/WISDEM/blob/0b3ac37b00778d7366de2084043c979183e2fc8c/wisdem/inputs/geometry_schema.yaml#L2040), inherited from WISDEM. Six lines should...
It seems like you may not have added additional mooring nodes with anchor points to the geometry input. If you share the mooring section of your geometry input, we can...
Hi, Sorry for the delay. I suspect the issue is that some of your anchors are at the same location. I'm not able to reproduce your issue with the snippet...
I think this issue has been resolved in the latest release. If not, please re-open it, and we'd be happy to help.
Hi @yonghoonlee, thanks for putting this PR together! It looks like nice work. Some notes and questions: - I added a few minor comments about code style and readability. -...
Hi @yonghoonlee, the comments should show up on this page (above): https://github.com/WISDEM/WEIS/pull/303
@yonghoonlee , should we keep this open or switch to the new one you're working on?
@yonghoonlee, is this happening on Kestrel or another linux machine?
Solution from @yonghoonlee `conda install -y petsc4py mpi4py mpich pyoptsparse # (Mac / Linux only)` (also install mpich)