search

yexiang1992 / opstool

Pre-Processing, Post-Processing, and Visualization Tailored for OpenSeesPy
https://opstool.readthedocs.io/en/stable/
GNU General Public License v3.0
73 stars 13 forks source link

shear wall model visualization issue #39

Open izzettinalhalil opened 2 months ago

izzettinalhalil commented 2 months ago

Can I know the element types that opstool supports?

I am trying to visualize a model containing SFI_MVLEM shear wall model, but encouraged a problem as:

  1. the wall elements are not shown when I plot the model.
  2. when I try to plot response data, it gives me issue as:

"Model data saved in opstool_output/ModelData.hdf5! Traceback (most recent call last):

File ~\AppData\Roaming\Python\Python311\site-packages\spyder_kernels\py3compat.py:356 in compat_exec exec(code, globals, locals)

File e:\engineering\my phd\exp test\2015 10-story edefence test\numerical model\2015 edefence test full detailed 1.py:3108 ModelData.get_resp_step()

File ~\AppData\Roaming\Python\Python311\site-packages\opstool\vis\get_model_data.py:757 in get_resp_step self.get_node_resp_step(save_file=False, model_update=model_update)

File ~\AppData\Roaming\Python\Python311\site-packages\opstool\vis\get_model_data.py:437 in get_node_resp_step (node_disp, node_vel, node_accel, node_deform_coord) = get_node_resp(node_tags)

File ~\AppData\Roaming\Python\Python311\site-packages\opstool\vis_get_model_base.py:696 in get_node_resp node_deform_coord[i] = [disp[ii] + coord[ii] for ii in range(3)]

File ~\AppData\Roaming\Python\Python311\site-packages\opstool\vis_get_model_base.py:696 in node_deform_coord[i] = [disp[ii] + coord[ii] for ii in range(3)]

IndexError: list index out of range"

when I delete the shear walls and replace columns, it works fine.

izzettinalhalil commented 2 months ago

I found that when I use shear wall elements, the model generates many synthetic nodes, also nodes with negative tags. This is what does create the problem above.

yexiang1992 commented 6 days ago

I found that when I use shear wall elements, the model generates many synthetic nodes, also nodes with negative tags. This is what does create the problem above.

Sorry for taking so long to reply, as I have been very busy with work recently. opstool has been significantly updated, you can check if the latest version can solve the problem. If not, we should study this element specifically. In fact, opstool does not target a specific OpenSees element type, it uses a general finite element mesh type. Whether adding nodes inside the SFI_MVLEM element causes more visualization problems needs further study. Best wishes.