Dear STKO community,
I have been working on a simple 3D arch, but I am unable to open the output database - mpco cdata file. I have installed the external solvers from this link https://www.pucp.edu.pe/profesor/sabino ... ducciones/. When I select the solver, it shows auto-detected solvers, but they are not getting selected, so I selected manual and performed the analysis, but I couldn't get the output (postprocessing results). I have also attached the image in the zip file.
Additionally, I want to apply varying displacements (linear manner) in the longitudinal direction of the arch at each node. For this, I need to select each node. Can you please help me with how to select each node and apply displacements at each node?
Error regarding postprocessing is here
writing nodes...
Writing nodes belonging to geometries without element property assignment ...
pre-processing elements...
pre-processing module: ASDAbsorbingBoundary2DAuto
pre-processing module: ASDAbsorbingBoundary3DAuto
pre-processing module: RCJointModel3DElement
writing elements...
write geometry...
write interactions...
writing analysis steps...
Running Time-Increment Utility...
writing analysis_steps...
Done.Input file correctly written!
End Command: RunAnalysis
Command: SetContext_PostProcessor
End Command: SetContext_PostProcessor
Command: OpenDatabase
Cannot open output database "C:/Users/user/Downloads/STKO models/trial3Darch_unknLongdir.mpco.cdata"
Error: cannot open "C:/Users/user/Downloads/STKO models/trial3Darch_unknLongdir.mpco.cdata".
Abort Command: OpenDatabase
Command: SurfaceColorMap
Cannot create a plot without a Database
Abort Command: SurfaceColorMap
Thank you.
Issue in finding mpco database
Re: Issue in finding mpco database
The output file is the *.MPCO file. The *.MPCO.CDATA file is a support file that STKO will open automatically when you open the associated MPCO file.
Re: Issue in finding mpco database
Hi, i have the same problem.
Re: Issue in finding mpco database
What do you mean?
The problem was that the user was trying to open the wrong file (mpco.cdata instead of mpco)
The problem was that the user was trying to open the wrong file (mpco.cdata instead of mpco)