Import/Export Force vectors

Posted by: viv0102

Import/Export Force vectors - 09/25/20 06:22 AM

Hi there!

In CAESAR, We have an excellent option to bulk import and export displacement vectors from .csv/.disp files through the "Tools > Import/Export Displacements" option.
This is really useful for cases such as FPSO, Bridge lines analysis where we have to input imposed structural displacements for every pipe support.

Is there a similar option to import/export Force vectors in bulk also?

We often do quasi-static equivalent analysis of dynamic loadings such as slug, surge etc. And we have custom macros already that calculates the force vectors at each node.
When you have a complex system with 50+ bends and branches, we have to manually input forces in various vectors (F1 to F9) for every bend. It is a pain to do this and track changes especially when you have multiple CAESAR files for one system (Design slug, accidental slug etc).

If not, I wonder if anyone has found a simpler way to input these force vectors in bulk (assuming force; vector; node number table is available from a custom macro).

(BTW, bravo on the feature introduced in a recent version where we can visibly see the force vector arrows for each vector in the graphical model. Extremely useful for checking if the input is correct and that no forces cancel each other out in the same vector!)
Posted by: Naren

Re: Import/Export Force vectors - 09/28/20 07:41 AM

I am sure, this will be a future option available in CAESAR II.
Posted by: Michael_Fletcher

Re: Import/Export Force vectors - 09/28/20 09:18 AM

I suspect the easiest way for Hexagon to enable this for the user is to "turn forces on for all elements." Presumably we can copy/paste wholesale here, or, if not, allow us to import a csv.

But in the absence of that...

My first guess would be to check what information gets lost in the CAESAR neutral file export/import. Maybe it can be injected via Excel or something else.

My second guess would be to have Excel take over the keyboard/mouse, but this is a potentially dangerous proposition, and will not take kindly to different users' setups, moving of dialogue boxes, etc.