Seismic Analysis Error in OpenSees SP using LK Bottom Condition
Posted: Mon Apr 10, 2023 9:53 am
Dear STKO,
I am writing to seek your advice on an issue I have encountered while conducting a seismic analysis using OpenSees SP.
Specifically, I have defined a Lysmer-Kuhlemeyer (LK) bottom condition to implement the seismic input in my numerical model for a soil domain. However, when I attempt to run the analysis, I receive the following error message: 'WARNING ZeroLength::setDomain() - Nd1: 2 does not exist in model for ZeroLength ele: 6052.' (Please see the attached image for further information).
Interestingly, when I change the solver to OpenSeesmp, this error is eliminated. Moreover, I have also noticed that in Youngkyu's quick questions forum (viewtopic.php?f=39&t=1953), a similar LK bottom boundary is adopted, and when I run his model in OpenSees SP, the error is not raised.
Therefore, I suspect that there may be some additional errors in my model, which are causing this issue. I would be grateful if you could offer some guidance or suggestions on how to resolve this error.
Thank you very much for your time and assistance.
Sincerely,
Jiaxing
My model is here:
I am writing to seek your advice on an issue I have encountered while conducting a seismic analysis using OpenSees SP.
Specifically, I have defined a Lysmer-Kuhlemeyer (LK) bottom condition to implement the seismic input in my numerical model for a soil domain. However, when I attempt to run the analysis, I receive the following error message: 'WARNING ZeroLength::setDomain() - Nd1: 2 does not exist in model for ZeroLength ele: 6052.' (Please see the attached image for further information).
Interestingly, when I change the solver to OpenSeesmp, this error is eliminated. Moreover, I have also noticed that in Youngkyu's quick questions forum (viewtopic.php?f=39&t=1953), a similar LK bottom boundary is adopted, and when I run his model in OpenSees SP, the error is not raised.
Therefore, I suspect that there may be some additional errors in my model, which are causing this issue. I would be grateful if you could offer some guidance or suggestions on how to resolve this error.
Thank you very much for your time and assistance.
Sincerely,
Jiaxing
My model is here: