RE; ProfileSPDLinDirectSolver::solve() - aii < minDiagTol (i, aii): (73, -5.54971e-13)

Post Reply
ryancwl95
Posts: 98
Joined: Mon Sep 25, 2023 12:42 am

RE; ProfileSPDLinDirectSolver::solve() - aii < minDiagTol (i, aii): (73, -5.54971e-13)

Post by ryancwl95 » Mon Oct 30, 2023 12:50 pm

Hi admin,

While running a consolidation problem of a soil column using Linear elastic material and SSPbrickUP Element, I encountered this warning/problem.
Screenshot 2023-10-30 124850.png
Screenshot 2023-10-30 124850.png (8 KiB) Viewed 5206 times
Could you explain in detail what the warning means? and perhaps some troubleshooting measures. Thank you:)

STKO Team
Posts: 3066
Joined: Tue Oct 29, 2019 8:45 am

Re: RE; ProfileSPDLinDirectSolver::solve() - aii < minDiagTol (i, aii): (73, -5.54971e-13)

Post by STKO Team » Tue Oct 31, 2023 3:15 pm

it's saying that your model is singular.
double check your boundary conditions

ryancwl95
Posts: 98
Joined: Mon Sep 25, 2023 12:42 am

Re: RE; ProfileSPDLinDirectSolver::solve() - aii < minDiagTol (i, aii): (73, -5.54971e-13)

Post by ryancwl95 » Sun Nov 05, 2023 9:33 pm

Hi,

Thank you for your reply.

When generating sp fixities in tcl file, and the input script describes (for the same node) 2 fixity inputs, which takes priority, or do they merge?

For eg,
fix 211 0 0 0 1
fix 211 1 1 0 0

When opensees reads the tcl file(example), does the fixity for node 211 follows the first input of "0 0 0 1" or the second input "1 1 0 0", or does merge to be 1 1 0 1.

kesavapraba
Posts: 468
Joined: Sat Mar 28, 2020 2:25 pm

Re: RE; ProfileSPDLinDirectSolver::solve() - aii < minDiagTol (i, aii): (73, -5.54971e-13)

Post by kesavapraba » Tue Nov 07, 2023 10:03 am

Please be aware that if you attempt to apply a single-point (SP) constraint (fixity) to a degree of freedom (DOF) of a node where an SP constraint is already specified, OpenSees will generate an error
Domain::addSP_Constraint - cannot add as node already constrained in that dof by existing SP_Constraint
In your situation, SP constraints should be combined since you try to apply the constraints at the DOFs that have "0". So, No error would appear and they should be combined together.
:: With best wishes ::
Prabakaran Kesavan

ryancwl95
Posts: 98
Joined: Mon Sep 25, 2023 12:42 am

Re: RE; ProfileSPDLinDirectSolver::solve() - aii < minDiagTol (i, aii): (73, -5.54971e-13)

Post by ryancwl95 » Wed Nov 15, 2023 1:29 pm

Also, just an additional question,

Is there a function to reset the displacement before executing a new analysis? or is it automatic, i.e displacement of the 2nd analysis is independent of the 1st analysis.

kesavapraba
Posts: 468
Joined: Sat Mar 28, 2020 2:25 pm

Re: RE; ProfileSPDLinDirectSolver::solve() - aii < minDiagTol (i, aii): (73, -5.54971e-13)

Post by kesavapraba » Wed Nov 15, 2023 8:05 pm

I am sorry that your question is not clear to me. To what state do you want to reset the displacement of the system, Initial? Anyway, you can use reset command to bring your system to its original state (although there are some limitations, please check the link below).

https://openseespydoc.readthedocs.io/en ... reset.html

Moving on from first stage to 2nd stage of the analysis (as you pointed out), the displacement and loads are carried forward and loads are maintained constant for the 2nd analysis if you enable loadConst with pseudoTime=0.
:: With best wishes ::
Prabakaran Kesavan

Post Reply