Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starter fails with lsdyna keyword *NODE_TRANSFORM #2581

Open
hdrz opened this issue May 6, 2024 · 10 comments
Open

Starter fails with lsdyna keyword *NODE_TRANSFORM #2581

hdrz opened this issue May 6, 2024 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@hdrz
Copy link

hdrz commented May 6, 2024

Describe the bug
When including *NODE_TRANSFORM in the input .k file, starter fails with exit code 3.

To Reproduce
Just use this keyword, as in the attached example.

Expected behavior
The nodes in the node-set should transform (in this case rotate).

Desktop (please complete the following information):

  • Version [commit id] - 81eea05
  • Hardware [which CPU] - Any x86_64, tried on few, intel and amd
  • Configuration [number of OpenMP threads, and MPI tasks] - Starter with any np or nt

Additional context
Add any other context about the problem here.
test.zip

@sebastienVilleneuve
Copy link
Contributor

Hi,

Rotation angle is null in your model.
only 2 first fields of the DEFINE_TRANSFORMATION card 'a1' & 'a2' are filled , then this card is understood as transformation using points 1 & 2 ( that are not existing in the model)
Could you retry with a non null value ?

regards,
Sébastien

@hdrz
Copy link
Author

hdrz commented May 6, 2024

Hi,
From the user guide for the a1 field:
image
So with only a1,a2,a3 filled, a1 and a2 hold node numbers, while a3 holds the angle. In the model attached nodes 1 & 2 exist.

I didn't try the full option of rotate yet, it might work, but this is definitely a bug (in the implementation or the ref guide..)

Thank you,
Hadar

@sebastienVilleneuve sebastienVilleneuve added the bug Something isn't working label May 6, 2024
@sebastienVilleneuve sebastienVilleneuve self-assigned this May 6, 2024
@sebastienVilleneuve
Copy link
Contributor

Ok , Thanks for the details,
I will check

Sébastien

@sebastienVilleneuve
Copy link
Contributor

sebastienVilleneuve commented May 6, 2024

Hi,

some more information :

In Dyna manual , DEFINE_TRANSFORMATION makes reference to points, defined in option itself, not to nodes
image

I think there is a pb in user guide , this should be point instead of nodes

@hdrz
Copy link
Author

hdrz commented May 6, 2024

Yes that is true, but according to the ref manual of radioss it works differently in radioss. Also, the option to use POINT is not present in radioss, again according to ref manual.

Can you clarify this issue?
Thank you

Also, there is an option in dyna ROTATE3NA which works with nodes, just like it should with ROTATE in radioss

@sebastienVilleneuve
Copy link
Contributor

sebastienVilleneuve commented May 6, 2024

I confirm , doc is wrong ,

POINT is missing , & ROTATE is using POINTs , not NODEs.
We will update the doc.

Sébastien

@hdrz
Copy link
Author

hdrz commented May 6, 2024

OK that clarifies the issue.
At this point I would like to ask to add the option ROTATE3NA, which sometimes makes life a lot easier.
Thanks again!

@sebastienVilleneuve
Copy link
Contributor

sebastienVilleneuve commented May 6, 2024

ROTATE3NA is already supported , this will also be updated in the doc.
I will close this issue

Sébastien

@hdrz
Copy link
Author

hdrz commented May 6, 2024

Just now tried with the option ROTATE3NA, starter stops with exit code 3.
I simply modified the test.k file and tried to run it.

However if I add two POINT lines ROTATE works beautifully.

@sebastienVilleneuve
Copy link
Contributor

Ok , I will take care of ROTATE3NA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants