Learning Forum

[shk1048]

I have a encryted file and just wanted to be sure if it also works with lstasc?

[Imtiaz Gandikota]

It will work if the material belongs to non-design parts. ls-tasc will simply copy the input deck to lst_inc.k file.

[shk1048]

I have added the impact load case now! The dyna file of the impactor case works well when I run it in dyna. But when I use it in lstasc It shows me that the part is out of range? What does it mean and I think the part id which has this error is been created by lstasc.

Executing with LSTC network license
[STDOUT]
[STDOUT]*** Error 20216 (STR+216)
[STDOUT]part # 995068 is out-of-range
[STDOUT]2.000E+00 2.000E+00 2.000E+00 2.000E+00 0.000E+00 0.000E+00 0.000E+00 0.000E+0
[STDOUT]input phase will continue if possible
[STDOUT] forrtl: severe (174): SIGSEGV, segmentation fault occurred

[Imtiaz Gandikota]

Please check if *PART and *MAT definition for part 995068 is correct. This should be in file "lst_mat.k" which is an include file for DynaOpt.inp.

[shk1048]

It seems to be fine for me!!

[shk1048]

The part added by the topology software

[Imtiaz Gandikota]

Part # 995068 is out of range message means part id=995068 is referenced in the input but it does not exist. My guess is "lst_mat" file is not being read when you run the job.
In DynaOpt.inp file, what is the part id in *ELEMENT_SOLID? My guess is its probably 995068. If that is the case, check the *INCLUDE card. If you're running ls-tasc without any queuing options, the include cards are written with relative paths and maybe this is causing an issue and lst_mat file, located in directory one level up, is not being read.

[shk1048]

Correct! The part id in *ELEMENT_SOLID is the part 995068. But it is also the same for stiffness cases and it worked. Only when I have added an additional include for the impactor I have this error. I understood that the *MAT is not read. But what is the need of queuing option here, can you eloborate it more. I am using a local workstation to run and not using it in cluster. I tried direct ways but nothing worked.

Thanks in advance

[shk1048]

I have removed the encryped material card include and added materials manually and the simulation started to work. I think the encrypted material include for the impactor which I used was not accepted or might have cause some trouble.

[shk1048]

Does it mean that my encrypted file is not read? and is outdated?
But the file worked when I run with a dyna solver.

[Imtiaz Gandikota]

I think you can ignore this warning. The file was probably encrypted using older version of keys (R7 and below) and you are running later versions of ls-dyna.
Regarding the part range issue, it is difficult to debug it without checking the files. In general, ls-tasc will simply copy encrypted part of the input to lst_inc.k file, it will not try to process/read/modify this part of input. ls-tasc is only modifying the design part, its material, and maybe some contact cards involving the design part so I expect rest of the input to be same (i.e. comparing input in DynaOpt.inp, lst_inc.k, and lst_mat.k vs. original input file). Please compare 0.1 input files with original input file and check what changed, especially with impactor input.
If you think ls-tasc is not copying impactor input to lst_inc.k correctly, I suggest a workaround. Place the impactor input in a separate file and DO NOT add this as an include file to your main k file that you read in as ls-tasc load case. Now when you run ls-tasc, it will not copy impactor input to lst_inc.k. In your ls-tasc solver command, use a script. This script should edit ../lst_inc.k and add two lines (*include, ../../impactor.k) before running ls-dyna solver command for DynaOpt.inp.