Suggestion 1: There should be a toggle to display element local coordinate geometry. This would make local restraint summaries more useful. I would suggest the three lines with x,y,z indicators.

The control of the display be toggled between on, off, and active element(s) only.

Local axes should also be able to rotated by the user to fit their needs, and on a per-element basis.

Local axes should be able to be reset to program defaults.

Suggestion 2: The checkerbox arrow for Nozzle Limit can be replaced thusly.

Suggestion 3: Let the user have the option to input allowable nozzle moments in ft-lb instead of ft-in.

Suggestion 4: User defined nozzle limit databases would be helpful.

Suggestion 4: User defined nozzle limit databases would be helpful.

This is already possible.

You can create your own .eql file and place into the System folder.

Actually is a txt file with .eql extension

Regards

Dear Michael,
if I understand your suggestions, some of them are already available.

For example you can create a user defined set of units and define moments in ft-lb or Nm.

You can even create some sets of user define nozzle limit files, and replace the .eql file in the system directory.
I agree with you that this procedure is not always straightforward.


Regards
Corrado M.Vannella
www.vannella.com

That'll teach me to miss something right under my nose. Thanks, you two.

I suppose it would be nice if we could get an interpreter that knows custom ways to combine these loads similar to Goulds requirements.

Some pumps require double unity checks, and then some.

(SRSS (F)/Fmax) + (SRSS (M)/Mmax) < 1
(SRSS (F)/Famax) + (SRSS (M)/Mamax) <1
Abs(Fx)/(0.85 Fmax) + SRSS(My, Mz)/(0.64 Mmax) <1
Abs(Fx)/(0.85 Famax) + SRSS(My, Mz)/(0.64 Mamax) <1

Don't worry Michael, you often feed this forum with interesting posts.
Talking about your last question, I would postprocess the output in Excel and if necessary I would create a custom report and/or some suitable loadcases.

Regards

Corrado Vannella
www.vannella.com

That's indeed what we currently do. Being able to manipulate the local axes would reduce the error associated with data transfer for loads from CAESAR to other programs, whether it be NozzlePro, Excel, or other.