Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible bug in drift recorder #138

Open
volkanozsarac opened this issue Jun 21, 2024 · 2 comments
Open

Possible bug in drift recorder #138

volkanozsarac opened this issue Jun 21, 2024 · 2 comments

Comments

@volkanozsarac
Copy link
Contributor

volkanozsarac commented Jun 21, 2024

Could it be possible that the drift recorder has a bug? It works for single iNode and jNode. However, it gives an error in the case of more than one iNodes and jNodes.

OK:

ops.recorder('Drift', '-file', drift_file_path, '-iNode', 10, '-jNode', 20, '-dof', 1, '-perpDirn', 3)

NOT OK:

ops.recorder('Drift', '-file', drift_file_path, '-iNode', 10, 20, '-jNode', 20, 30, '-dof', 1, '-perpDirn', 3)
WARNING: failed to get dof
WARNING failed to create recorder
Traceback (most recent call last):
  File "<string>", line 1, in <module>
opensees.OpenSeesError: See stderr output
@volkanozsarac volkanozsarac changed the title Possible bug on drift recorder Possible bug in drift recorder Jun 21, 2024
@mhscott
Copy link
Collaborator

mhscott commented Jun 21, 2024

The drift recorder only takes a single I node and single J node. Does the Tcl version accept multiple I and J nodes like you've shown?

@volkanozsarac
Copy link
Contributor Author

volkanozsarac commented Jun 21, 2024

The drift recorder only takes a single I node and single J node. Does the Tcl version accept multiple I and J nodes like you've shown?

Yes, it worked for my trials with Tcl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants