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
I have some solutions for how to organize better those information and I would like @hmgaspar , @EliasHasle , @icarofonseca , and all others in the project to identify the best solution based on the vesseljs main objective:
Insert the elements variables in the JSON of the ship and change the function loadShip to read those information. This solution could be applied to mooring lines or dynamical matrices, once they can be interpreted as part of the ship system information.
Create a function similar to loadShip to read the other elements. This solution could be applied if we interpreter the mooring as a different system from the ship and could prevent errors in loadShip.
Let elements in the own code, just transforming the global variable into smaller object oriented variables.
The text was updated successfully, but these errors were encountered:
I would recommend starting with 3, first focusing on structuring the code into a nice, reusable module. Do 2 if needed in the process. Then one can decide later whether it belongs in the ship or elsewhere.
The lines (mooring and equipment lines), dynamical matrices (masses, damping and restoration), and the equipment I am inserting for epoch project are disconnected with any external JSON file, creating a lot of global variables like in the examples that succeeded my 6DOF calculation:
https://github.com/shiplab/vesseljs/blob/master/examples/Ship_in_Ocean_dynamical.html
https://github.com/shiplab/vesseljs/blob/master/examples/Ship_in_Ocean_dynamical_MooringWave.html
https://github.com/shiplab/vesseljs/blob/master/examples/Ship_in_Ocean_dynamical_MooringWave_Parametric.html
I have some solutions for how to organize better those information and I would like @hmgaspar , @EliasHasle , @icarofonseca , and all others in the project to identify the best solution based on the vesseljs main objective:
The text was updated successfully, but these errors were encountered: