> But that's a different error. Have you tried to look up what error code 60
> means in SLEPc?
Here is the entire error. I was interpreting the error was the “Nonconforming
object size”, which is the error I was reporting. I will research the error 60
in Slepc, thank you!
[0]PETSC ERROR:
On 1/8/21 3:58 PM, Zachary 42! wrote:
Yes, the error comes when I try to use the Slepc solver (the matrix builds
without errors). Running the attached file (Sorry, I’v been experimenting
trying to get things working so I think I should include what I am testing
now), At the bottom of the
No, that's not what you want. You need to partition the columns in the same way as you partition the vectors you want to multiply the matrix by. We generally partition the vectors in the same way as the rows of the matrix, and so then you also have to choose the same partitioning for the columns
You said “the local number of columns also needs to add up to the global
number of columns” but my desired layout is local_num_columns ==
global_num_columns.
No, that's not what you want. You need to partition the columns in the same
way as you partition the vectors you want to multiply
On 1/8/21 10:19 AM, Alberto Salvadori wrote:
thank you for the hint. I looked at setp 47 sparsity pattern. If I understood
it right,
the main difference stands in the locally_relevant_dofs, which are no longer
extracted and used.
Rather, the sparsity pattern is based on the whole dof_handler,
On 1/8/21 12:15 PM, Lixing Zhu wrote:
This way I can freely use bubble functions and only construct local K and F of
FE_1. However, one issue is that, apparently, triangulation.cell does not
support cell->get_dof_indices(local_dof_indices). Is there any way to call the
DOFhandler by the cell
On 1/7/21 10:22 PM, Lixing Zhu wrote:
You are right. I am not bounded by the memory at this moment. The only
potential issue I can think of at this stage is the computation of the error
norm. Technically, if I feed the slots in global RHS corresponding to bubble
support as zero, the solution
Hi W and Jean-Paul,
Thanks again for your suggestions.
I realized that the bubble functions that I prefer are actually the shape
functions from other standard elements. Thus I only need to define two sets
of FE (i.g. FE_1 and FE_b). Then I use the iterator from triangulation as
for (const
Dear Behrooz,
The problem here is that your Trilinos installation includes the
SEACASChaco package. We'd discovered that there's a common global symbol
that both ADOL-C and Trilinos-SEACASChaco emit, which causes some very
strange issues when using ADOL-C. Naturally, we had to make sure that
Wolfgang,
thank you for the hint. I looked at setp 47 sparsity pattern. If I
understood it right,
the main difference stands in the locally_relevant_dofs, which are no
longer extracted and used.
Rather, the sparsity pattern is based on the whole dof_handler, as per the
instruction
Hi W.,
Apologies for not asking a specific question. Your help with the SparseMatrix
constructor still left me confused and I was hoping for clarity. ( To answer
your question, the code ran without error but the error came back once I tried
to use Slepc. )
You said “the local number of
Dear Wolfgang,
Thank you for your response. I am working on phase-stability in materials,
for smooth initial conditions it produces the correct phase but for random
initialization it produces a phase which I am not expecting. The phases are
every sensitive to the initial-conditions used. If I
12 matches
Mail list logo