hexagon logo
Register Sign in
  • State Not Answered
  • Replies 8 replies
  • Subscribers 3 subscribers
  • Views 149 views
  • Users 0 members are here
Options
Related

Creating session file for pressure load mapping using PCL.

vishal.kalkunte
Hi,
 
I have a query regarding load and boundary conditions syntax using PCL.
 
Problem definition: I am creating a session file for GFEM to DFEM pressure mapping using PCL commands. My query is, how patran is writing PLOAD cards for a particular subcase as highlighted in below example.
 
Example : How these highlighted load ids are considered in Patran PCL. Kindly explain the load case id pattern being considered as this is required to loop for many load cases.
 
INTEGER loadsbcs_plot_scalar_table_id
lbc_create_scalar_table( "Pressure", 8, 0., "Top Surf Pressure", "Resultant", @
11, [4,5, 6, 7, 13, 19, 25, 31, 37, 43, 49], 1, [3], @
loadsbcs_plot_scalar_table_id )
 
PS: An example file would be great if you can share the loads case selection pattern using pcl.
 
Many Thanks in advance.
 
Vishal
Parents
  • 0
    Hi,
    With a new database Patran starts its internal IDs at 1 and they work upwards. However you should never rely on internal ID's as they are only for internal cross referencing. external labels are used to communicate with the outside world and these are the familiar names and numbers a user references through the gui.
     
    The logic of the gaps that you see, for this model, will have an explanation that is related to all the other types of LBC that you are loading into the database at the same time. You should not try to use this type of logic to guess what the ids will be that you want to use. Rather than write VBA that tries to guess internal IDs, you should use your VBA to write a session file that has function calls to query the db and extract the necessary information to build the arguments to the functions you want to make.
    The previous pcl function (to dump loadcase load ids) could, with some work, turn into a function that returns the number and string array of ids for a particular load type like pressure, This could be the arguments "11, [4,5, 6, 7, 13, 19, 25, 31, 37, 43, 49]" for the lbc_create_scalar_table function call.
     
    You will need to write PCL code to query the database(similar to this example) and call this from (or embed this in) the session file you are writing.
     
    I hope this helps you understand the logic of the internal IDs and also to appreciate that you should not try to guess what they will be but always query what they actually are. That way what ever happens internally in the db you session will find the right ids.
    best regards
    Arthur
     
     
     
Reply
  • 0
    Hi,
    With a new database Patran starts its internal IDs at 1 and they work upwards. However you should never rely on internal ID's as they are only for internal cross referencing. external labels are used to communicate with the outside world and these are the familiar names and numbers a user references through the gui.
     
    The logic of the gaps that you see, for this model, will have an explanation that is related to all the other types of LBC that you are loading into the database at the same time. You should not try to use this type of logic to guess what the ids will be that you want to use. Rather than write VBA that tries to guess internal IDs, you should use your VBA to write a session file that has function calls to query the db and extract the necessary information to build the arguments to the functions you want to make.
    The previous pcl function (to dump loadcase load ids) could, with some work, turn into a function that returns the number and string array of ids for a particular load type like pressure, This could be the arguments "11, [4,5, 6, 7, 13, 19, 25, 31, 37, 43, 49]" for the lbc_create_scalar_table function call.
     
    You will need to write PCL code to query the database(similar to this example) and call this from (or embed this in) the session file you are writing.
     
    I hope this helps you understand the logic of the internal IDs and also to appreciate that you should not try to guess what they will be but always query what they actually are. That way what ever happens internally in the db you session will find the right ids.
    best regards
    Arthur
     
     
     
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement