I realize AttachGHS is an old code in Rhino. However, it is widely used by naval architects and it remains a very relevant tool to GHS users! After 15 years of using AttachGHS, I have a few upgrades to propose:
-
Add a top-level “vessel” hierarchy to the current “tree” in attachGHS to allow multiple different attachtGHS models within the same rhino file. As the top level of organization, each “vessel” instance in the tree would contain all of the current subcategories currently in attachGHS, so there would be no dependency or shared assets within attachGHS across vessels (such as shapes - those would be re-created and independent for each vessel). The point of this feature is to have multiple versions of a vessel within the same rhino file, to facilitate the “design spiral”. (Copies of the entire rhino file simply to support different attachgGHS versions is not always ideal for version control or file management)
-
Add a “duplicate” feature within attachGHS to allow vessels (see above), Hull Items, Tank Items, Sail Items, to be duplicated in the tree as a starting point for a new version of that item.
-
Add the ability to define deck edges in attachGHS.
-
Add the ability to define “color” for tank contents.
-
Fix save as partmaker file, as this functionality occasionally creates files that cannot be read by GHS.
-
Improve the automatic station generation to look at rate of change of shapes in y and z (or rate of change of cross sectional area) to determine optimal placement of stations and add the ability to maintain a user-defined maximum spacing of stations in x.
Thanks for reading!