Replies: 2 comments 1 reply
-
Unfortunately, I do not believe there is any central guidance on how to transition from Epetra to Tpetra. Though this would have been useful, it just did not happen. :( As you may know many of the interfaces are similar between Epetra and Tpetra with the obvious difference of templating, but with enough differences to require careful changes. I would suggest that you reach out to the Tpetra team, @trilinos/tpetra, for specific questions. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Is the text "@trilinos/tpetra" supposed to link to something on Github? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've started an attempt to port an old code from Epetra to Tpetra, since Epetra is being deprecated, and I've found is that constructing various object in Tpetra, especially distributed graphs and matrices, takes more upfront information (e.g., max number of entries per row, which off-process rows are available to share, etc.) than it does in Epetra.
Is there any somewhat "canonical" guide on how to work around such difficulties? I've seen various scattered sources with fragments of information, some of which may be more current than others, but not anything like a reference that illustrates what to do to port code using Epetra objects to their Tpetra counterparts.
Beta Was this translation helpful? Give feedback.
All reactions