pymapdl icon indicating copy to clipboard operation
pymapdl copied to clipboard

[SUMMARY] MAPDL features/bugs implementation list

Open germa89 opened this issue 1 year ago • 5 comments

This issues is to keep track of the features/bugs that needs to be fixed in MAPDL. They might be tracked somewhere else as well, but this issue should raise visibility among PyMAPDL users.

  • [ ] PRIORITY [BUG] #3313
  • [ ] [BUG] Parsing issues when MAPDL logger is printing to console. See #3591
  • [ ] [BUG] #3248
  • [ ] [BUG] #3208
  • [ ] [FEAT] #3613
  • [ ] [FEAT] Release port before exiting #2564
  • [ ] [FEAT] #2021
  • [ ] [FEAT] #1038
  • [ ] [BUG] #2844
  • [ ] [FEAT] Attach a session ID in each gRPC message. See #2608
  • [ ] [BUG] Fix reading geometry files when using gRPC: https://github.com/ansys/pymapdl/issues/2948
  • [ ] [BUG] Fix MPREAD https://github.com/ansys/pymapdl/discussions/3333#discussioncomment-10257297
  • [ ] [BUG] #2933
  • [ ] [BUG] #1419
  • [ ] [FEAT] Transfer areas using the gRPC, so we do not need to re-mesh. https://github.com/ansys/pymapdl/issues/3613
  • [ ] [FEAT] Implement hash in the entities, so it changes when new geometry is added, or the existing is changed.
  • [ ] [FEAT] Hashing database so we can check first if there is changes in it or not before retriving mesh or data.
  • [ ] #3811
  • [ ] [FEAT] Retrieve entities IDs, and selected components using gRPC methods. Related to https://github.com/ansys/pymapdl/issues/3652

Ideally new features should couple with the MAPDL commands, so we do not duplicate code. Meaning, we are aiming to a code refactor more than coding new stuff.

Need to check

  • [ ] #1114
  • [ ] #3070

germa89 avatar Jan 29 '24 10:01 germa89

Hi German, So it looks like the issue is calling *VREAD in a loop; at some point MAPDL crashes (still not sure if it is PyMAPDL or MAPDL). For this case I got rid of all the loops to set parameters and used the good old method of defining a huge table as a CSV and read it all at once using *TREAD. Luckily it works! surprised 1 What does mapdl.parameters["SET_PARAM"] = ... use behind the scenes? I am assuming it does exactly what I tried using *VREAD; that is why I see the exact same behaviour / crash?

By @ayush-kumar-423 Related to #2844

germa89 avatar Mar 07 '24 13:03 germa89

Error running Ayush code:

 Server listening on : 0.0.0.0:50052
E0607 16:34:41.940439472    1545 proto_buffer_writer.h:67]   assertion failed: !byte_buffer->Valid()
forrtl: error (76): Abort trap signal
Image              PC                Routine            Line        Source             
libc.so.6          00007FFFBEE19520  Unknown               Unknown  Unknown
libc.so.6          00007FFFBEE6D9FC  pthread_kill          Unknown  Unknown
libc.so.6          00007FFFBEE19476  raise                 Unknown  Unknown
libc.so.6          00007FFFBEDFF7F3  abort                 Unknown  Unknown
libgrpc++.so.1.46  00007FFE9C67E894  Unknown               Unknown  Unknown
libGrpcMapdl.so    00007FFE9DCF51E9  _ZNSt17_Function_     Unknown  Unknown
libgrpcpp_channel  00007FFE9D2656A1  _ZN4grpc8internal     Unknown  Unknown
libgrpc++.so.1.46  00007FFE9C69C913  _ZN4grpc8internal     Unknown  Unknown
libgrpc++.so.1.46  00007FFE9C69BEAC  _ZN4grpc8internal     Unknown  Unknown
libGrpcMapdl.so    00007FFE9DD04E79  _ZN4grpc12ServerW     Unknown  Unknown
libGrpcMapdl.so    00007FFE9DC224DC  _ZN12C_StreamMgrC     Unknown  Unknown
libGrpcMapdl.so    00007FFE9DC22CFF  _ZNSt17_Function_     Unknown  Unknown
libGrpcMapdl.so    00007FFE9DC1F15C  _Z9WatchFileI12C_     Unknown  Unknown
libstdc++.so.6.0.  00007FFFFF66D253  Unknown               Unknown  Unknown
libc.so.6          00007FFFBEE6BAC3  Unknown               Unknown  Unknown
libc.so.6          00007FFFBEEFCA04  clone                 Unknown  Unknown
/ansys_inc/v242/ansys/bin/ansysdis242: line 77:   754 Aborted                 /ansys_inc/v242/ansys/bin/linx64/ansys.e -grpc
/ansys_inc/v242/ansys/bin/anssh.ini: line 96:   245 Illegal instruction     expr "$envval" : \"* > /dev/null

germa89 avatar Jun 07 '24 16:06 germa89

  • Check if there is a memory leak by running a script (with /clear, finish) many many times and check memory increase. Suggested by @koubaa

germa89 avatar Jul 17 '24 14:07 germa89

Running vm1 code as non-interactive, it got slow down, I kill python, and restart, and I saw this.

 Current ANSYS Traceback:
     ender                           
     slout                           
     Mapdl::SendCommand              
     slout                           
     Mapdl::SendCommand              
     slout                           
     Mapdl::SendCommand              
     slinquire                       
     Mapdl::SendCommand              
     GRPC_Start                      
     gRPCMapdlStart                  
     ANSYS

germa89 avatar Jul 24 '24 16:07 germa89