Thread Content
After half a day of research and searching through various materials, the problem still wasn’t solved; everyone, let’s go down to the mortal world
It shouldn’t be possible to import it; I tried before and it didn’t work. PDSoft can do it, but the model exported has many discrepancies compared to the one created initially, so it needs to be checked again. The workload is also considerable
It can be imported, but errors are likely to occur
How was it imported? If an error occurs, it can be reviewed; it’s still better than getting it wrong,, Thanks:)
These are the steps found, but an error is still reported; Taking CaesarII as an example, modify the pds.cmd file by adding 2 lines: $ENV{'STRESSPATH'} ='C:\proj1\stress\out\\'; $ENV{'STRESSOPTION'} ='C:\proj1\stress\CAESARII.dat'; Create the directories C:\proj1\stress\ and C:\proj1\stress\out, then copy caesar.dat from c:\win32app\ingr\pdstress\dat\ to the C:\proj1\stress\ directory ; Change the path setting for the caesar.cde file in caesar.dat ; Copy c:\win32app\ingr\pdstress\dat\ caesar.cde to the C:\proj1\stress\ directory ; Enter the piping environment, revise the segment data, and modify the properties of the center line: stress_system_no: Enter a number; stress_reqmt: Select a status. Go to the pipe stress analysis model number: The model number to which the pipeline belongs ; Pipeline Name: Enter the given stress_system_no. If the 12 values associated with intergraph in the STRESSOPTION file CAESARII.dat are all 0, then you need to enter line_number_label or a part of it here; note that case sensitivity applies! *.n and *.h files are generated in the C:\proj1\stress\out directory as input files for the CaesarII software.