Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2018-12-20T18:43:11Zhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/4101Pliris: PR 73 - Package Warnings Fixes2018-12-20T18:43:11ZJames WillenbringPliris: PR 73 - Package Warnings Fixes*Created by: william76*
@trilinos/pliris
Pull Request #73 "Pliris Package Warnings Fixes" is really old and appears to be stale and/or abandoned. I'm closing that PR and creating this issue to link to it.
I'm doing this because...*Created by: william76*
@trilinos/pliris
Pull Request #73 "Pliris Package Warnings Fixes" is really old and appears to be stale and/or abandoned. I'm closing that PR and creating this issue to link to it.
I'm doing this because we need to close out some of the old PR's due to some GitHub limitations on the number of checks/hour that are allowed. The pull request autotester uses a polling model to check existing pull requests' status flags, etc. and we have occasionally hit that limit, which causes GitHub to reject the queries and can cause the Autotester to fail on a PR. If this PR needs to be brought back to life it can easily be reopened on the pull request page.
FYI: @jwillenbring @rrdrake @prwolfe https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4093MueLu: detect if input matrix is identity2019-01-03T23:11:25ZJames WillenbringMueLu: detect if input matrix is identity*Created by: jhux2*
A user recently tried to run MueLu on an identity matrix. For a large enough system, MueLu will coarsen to a zero-by-zero system, which causes problems. There should be a mechanism for detecting if all DOFs are bou...*Created by: jhux2*
A user recently tried to run MueLu on an identity matrix. For a large enough system, MueLu will coarsen to a zero-by-zero system, which causes problems. There should be a mechanism for detecting if all DOFs are boundary points, i.e., there are zero aggregates. One solution is to throw an exception during Dirichlet detection.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4092Framework: recent change affecting commit messages?2018-12-19T19:47:28ZJames WillenbringFramework: recent change affecting commit messages?*Created by: jhux2*
@trilinos/framework
The commit messages, as seen [here](https://github.com/trilinos/Trilinos/commits/develop), have changed over the past day or so. The most recent messages are of the form
`Merge pull reques...*Created by: jhux2*
@trilinos/framework
The commit messages, as seen [here](https://github.com/trilinos/Trilinos/commits/develop), have changed over the past day or so. The most recent messages are of the form
`Merge pull request #XXYY from <some branch>`
Previously, the messages had the first line of the actual commit message, which in my opinion is more helpful.
Is this due to an intentional change in the scripts, or is it perhaps just related to recent PR instabilities?https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4090Tpetra: Add macro for creating verbose debug output on a process2018-12-19T17:44:17ZJames WillenbringTpetra: Add macro for creating verbose debug output on a process*Created by: mhoemmen*
@trilinos/tpetra
See my comment on PR https://github.com/trilinos/Trilinos/pull/4089.
```c++
#define TPETRA_PRINTLN_LOCAL( out, myRank, stuff ) \
do { \
std::ostringstream tpl_out; \
tpl_out << "(...*Created by: mhoemmen*
@trilinos/tpetra
See my comment on PR https://github.com/trilinos/Trilinos/pull/4089.
```c++
#define TPETRA_PRINTLN_LOCAL( out, myRank, stuff ) \
do { \
std::ostringstream tpl_out; \
tpl_out << "(Proc " << myRank << ") " << stuff << std::endl; \
out << tpl_out.str (); \
} while (false)
```
This would factor out a common pattern inside Tpetra. It would work like `TEUCHOS_TEST_FOR_EXCEPTION`, in that `stuff` could be an expression like `"thing0: " << thing0 << ", thing1" << thing1`. https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4088Moocho: Build errors (INT_MIN missing)2018-12-19T16:51:32ZJames WillenbringMoocho: Build errors (INT_MIN missing)*Created by: mhoemmen*
See e.g., https://testing.sandia.gov/cdash/viewBuildError.php?buildid=4324923 . Not sure how to fix them, since Moocho does not live in the main Trilinos repository any more.
@trilinos/framework @jwillenbring ...*Created by: mhoemmen*
See e.g., https://testing.sandia.gov/cdash/viewBuildError.php?buildid=4324923 . Not sure how to fix them, since Moocho does not live in the main Trilinos repository any more.
@trilinos/framework @jwillenbring
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4087Xpetra: missing access routine getData for Xpetra::Vector2018-12-19T16:29:47ZJames WillenbringXpetra: missing access routine getData for Xpetra::Vector*Created by: mayrmt*
@trilinos/xpetra
@lucbv
## Expectations
It might be desired to have a specialized access routine `getData()` for the `Xpetra::Vector` that does not call the base class routine in `Xpetra::MultiVector`.
## ...*Created by: mayrmt*
@trilinos/xpetra
@lucbv
## Expectations
It might be desired to have a specialized access routine `getData()` for the `Xpetra::Vector` that does not call the base class routine in `Xpetra::MultiVector`.
## Current Behavior
To access the data in a `Xpetra::Vector`, one has to call the base class routine with argument `getData(0)` to access the data of the very first column in the multivector, although it is clear that the `Xpetra::Vector` only has one column.
## Motivation and Context
This would emphasize the fact that the `Xpetra::Vector` just has one column and make it more convenient to access its data.
## Definition of Done
- [ ] add `getData()` and `getDataNonConst()` to `Xpetra::Vector` class
- [ ] add documentation
- [ ] add test
## Possible Solution
The `Xpetra::Vector::getData()` could just call `Xpetra::MultiVector::getData(0)`.
## Additional Information
Please let me know if this idea is total nonsense or if there are reasons to *not* do that.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4085MueLu: enable 3D problems in HHG driver2018-12-19T07:10:05ZJames WillenbringMueLu: enable 3D problems in HHG driver*Created by: mayrmt*
@trilinos/muelu
## Expectations
Add support for three-dimensional problems to the HHG driver.
## Current Behavior
Support for 1D and 2D problems only.
## Motivation and Context
We need capabilities to d...*Created by: mayrmt*
@trilinos/muelu
## Expectations
Add support for three-dimensional problems to the HHG driver.
## Current Behavior
Support for 1D and 2D problems only.
## Motivation and Context
We need capabilities to deal with three-dimensional problems.
## Definition of Done
- [ ] Add an input generation mechanism for 3D problems.
- [ ] Add a 3D version `LID3Region()` of mapping from local IDs to region IDs.
## Possible Solution
- Input:
- This can either be Matlab based for testing and debugging purposes. However, larger problems cannot be done using the Matlab driver.
- Alternatively, we can base our input on Galeri, Pamgen, or some other tools by @lucbv.
- Mapping of local IDs to region IDs: We already have `LIDregion` and `LID2region` functions for 1D and 2D problems. The new 3D version `LID3region` might just look similar to those.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4071Framework: Change Autotester Default Behavior When Sub-Tests Fail2018-12-18T17:07:33ZJames WillenbringFramework: Change Autotester Default Behavior When Sub-Tests Fail*Created by: csiefer2*
@trilinos/framework
Since this is far from the first Intel compiler issue we've had, I propose adding logic to the PR system to have it approve PRs if the Intel compiler dies before reaching configure of Trili...*Created by: csiefer2*
@trilinos/framework
Since this is far from the first Intel compiler issue we've had, I propose adding logic to the PR system to have it approve PRs if the Intel compiler dies before reaching configure of Trilinos AND the gcc tests pass.
The logic behind this is to keep non-code Intel compiler fails from creating a "stop the line" condition in which framework team members need to drop everything and fix the Intel issue du jour.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4063Allow for KOKKOS_ARCH keyword in <build-name> string to be lower case and sep...2018-12-17T13:46:40ZJames WillenbringAllow for KOKKOS_ARCH keyword in <build-name> string to be lower case and separated by '_'*Created by: bartlettroscoe*
CC: @fryeguy52
## Description
The SPARC convention for the KOKKOS_ARCH name in their build strings is to use lower-case letters like `hsw` and `knl` vs. `HSW` and `KNL` and to use underscores '_' to s...*Created by: bartlettroscoe*
CC: @fryeguy52
## Description
The SPARC convention for the KOKKOS_ARCH name in their build strings is to use lower-case letters like `hsw` and `knl` vs. `HSW` and `KNL` and to use underscores '_' to separate arguments. Currently, the ATDM Trilinos build-name parsing system described [here](https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md#kokkos_arch) only support upper-case and camel-case names like `HSW`, `KNL`, and `Pascal60` and requires these to be preceded by a dash '-'. This is the last aspect of the currently ATDM Trilinos build name parsing system that does not match the preferences used by SPARC.
This story is to refactor the ATDM Trilinos parsing system (as implemented in `cmake/std/atdm/utils/set_build_options.sh`) to allow both the current upper-case and camel-case names separated by dashes '-' and to allow lower-case names separated by underscores '_'.
## Proposed Solution
The proposed solution is to write a bash function like
```
atdm_match_kokkos_arch_keyword <supported_kokkos_arc> <kokkos_arch_inout>
```
and then use it as:
```
ATDM_SUPPORTED_KOKKOS_ARCH_LIST=(
HSW
KNL
...
Pascal60
...
)
export ATDM_CONFIG_KOKKOS_ARCH=DEFAULT
for ATDM_SUPPPORTED_KOKKOS_ARCH in ${ATDM_SUPPORTED_KOKKOS_ARCH_LIST[@]} do ;
atdm_match_kokkos_arch_keyword ${ATDM_SUPPPORTED_KOKKOS_ARCH} ATDM_CONFIG_KOKKOS_ARCH
if [[ "${ATDM_CONFIG_KOKKOS_ARCH}" != "DEFAULT" ]] ; then
break
fi
done
```
The function `atdm_match_kokkos_arch_keyword` would check for `-<supported_kokkos_arc>` and `_<supported_kokkos_arc>` and then lower case `-<supported_kokkos_arc_lc>` and `_<supported_kokkos_arc_lc>`. If any of those matched, then it would update the variable `<kokkos_arch_inout>` to be `<supported_kokkos_arc>`. Easy as pie.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4060Tpetra: Add iallreduce overload that takes raw pointers2018-12-16T02:47:45ZJames WillenbringTpetra: Add iallreduce overload that takes raw pointers*Created by: mhoemmen*
@trilinos/tpetra @cgcgcg
PR https://github.com/trilinos/Trilinos/pull/4057 creates nonowning length-1 `Kokkos::View`s merely because the interface of `Tpetra::Details::iallreduce` demands it. Users will want...*Created by: mhoemmen*
@trilinos/tpetra @cgcgcg
PR https://github.com/trilinos/Trilinos/pull/4057 creates nonowning length-1 `Kokkos::View`s merely because the interface of `Tpetra::Details::iallreduce` demands it. Users will want to pass raw pointers into `iallreduce`, so we might as well give them an interface that supports it.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4056(RESOLVED but needs test) Tpetra:`transferAndFillComplete` causes MPI error a...2019-01-21T18:48:29ZJames Willenbring(RESOLVED but needs test) Tpetra:`transferAndFillComplete` causes MPI error at large communicator size.*Created by: cgcgcg*
@trilinos/tpetra @mhoemmen @DrBooom
## Current Behavior
Tpetra's `transferAndFillComplete` causes MPI error at large communicator size:
```
MPIR_MAXF_check_dtype(72): MPI_Op MPI_MAX operation not defined for ...*Created by: cgcgcg*
@trilinos/tpetra @mhoemmen @DrBooom
## Current Behavior
Tpetra's `transferAndFillComplete` causes MPI error at large communicator size:
```
MPIR_MAXF_check_dtype(72): MPI_Op MPI_MAX operation not defined for this datatype
Rank 31 [Thu Dec 13 20:42:18 2018] [c4-0c0s10n2] Fatal error in PMPI_Iallreduce: Invalid MPI_Op, error stack:
PMPI_Iallreduce(807).....: MPI_Iallreduce(sendbuf=0x7ffffffeb988, recvbuf=0x7ffffffeb98c, count=0, datatype=MPI_BYTE, op=MPI_MAX, comm=MPI_COMM_WORLD, request=0x7ffffffe72e8
) MPIR_MAXF_check_dtype(72): MPI_Op MPI_MAX operation not defined for this datatype
```
The error can also be reproduced at low small communicator size by passing
```
<Parameter name="MM_TAFC_OptimizationCoreCount" type="int" value="1"/>
```
in the parameter list.
I believe the issue might be here:
https://github.com/trilinos/Trilinos/blob/2da4a8a6dca7d679b24215151079c423fd4f664f/packages/tpetra/core/src/Tpetra_CrsMatrix_def.hpp#L93-L94
Shouldn't the views be created with a size argument? Cause it seems that the MPI_BYTE datatype that MPI complains about is set by default for views of length 0.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4042Zoltan test diff failures in targeted CUDA PR build Trilinos-atdm-white-ride-...2019-04-06T00:14:47ZJames WillenbringZoltan test diff failures in targeted CUDA PR build Trilinos-atdm-white-ride-cuda-9.2-release-debug-pt*Created by: bartlettroscoe*
CC: @trilinos/zoltan, @kddevin (Trilinos <product-area-name> Product Lead), @bartlettroscoe, @fryeguy52
## Next Action Status
<status-and-or-first-action>
## Description
As shown in [this query](...*Created by: bartlettroscoe*
CC: @trilinos/zoltan, @kddevin (Trilinos <product-area-name> Product Lead), @bartlettroscoe, @fryeguy52
## Next Action Status
<status-and-or-first-action>
## Description
As shown in [this query](https://testing.sandia.gov/cdash-dev-view/viewTest.php?onlyfailed&buildid=4287837) the tests:
* `Zoltan_ch_simple_zoltan_parallel`
* `Zoltan_ch_grid20x19_zoltan_parallel`
* `Zoltan_ch_ewgt_zoltan_parallel`
* `Zoltan_ch_nograph_zoltan_parallel`
fail in the build `Trilinos-atdm-white-ride-cuda-9.2-release-debug-pt` which is the current candidate CUDA PR build described in #2464. They have failed since we switched from a `debug` build to a `release-debug` build for the reasons described in https://github.com/trilinos/Trilinos/issues/2464#issuecomment-444637454. These are the only new tests that are failing since we switched from a `debug` to a `release-debug` build.
These all look to be "diff" failures like [here](https://testing.sandia.gov/cdash-dev-view/testDetails.php?test=61372846&build=4287837) showing:
```
DEBUG moving files: simple.out.4.3 output/simple.rib-partlocal4.4.3
DEBUG comparing files: answers/simple.rib-partlocal4.4.3 output/simple.rib-partlocal4.4.3
DEBUG comparing files: answers/simple.rib-partlocal4.drops.4.3 output/simple.rib-partlocal4.drops.4.3
DEBUG COMPARISON 1 1
Test simple:rib-partlocal4 FAILED (Diff failed on 1 files)
```
## Current Status on CDash
The current status of these tests/builds for the current testing day can be found at:
* [Zoltan tests in Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-release-debug-pt build over last two days](https://testing.sandia.gov/cdash/queryTests.php?project=Trilinos&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercount=3&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-release-debug-pt&field2=testname&compare2=65&value2=Zoltan_&field3=buildstarttime&compare3=83&value3=2%20days%20ago)
NOTE: Click "previous" to see the previous day's test results in case this build did not run today or add the filter ["Build Start Time", "is after", "2 weeks ago"] to see history of tests in previous days. (Or create any filters you want from there.)
## Steps to Reproduce
One should be able to reproduce these build errors on either 'white' or 'ride' by cloning the Trilinos git repo, checking out the 'develop' branch, creating a build directory, and then doing:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh cuda-9.2-release-debug
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_Zoltan=ON \
$TRILINOS_DIR
$ make NP=16
$ bsub -x -Is -q rhel7F -n 16 ctest -j16
```Initial cleanup of new ATDM builds of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/4038Xpetra/Epetra: link error in panzer test for intel debug static2019-04-26T16:35:24ZJames WillenbringXpetra/Epetra: link error in panzer test for intel debug static*Created by: bathmatt*
<!---
Provide a general summary of the issue in the Title above. If this issue
pertains to a particular package in Trilinos, it's worthwhile to start the
title with "PackageName: ".
-->
When I try to link p...*Created by: bathmatt*
<!---
Provide a general summary of the issue in the Title above. If this issue
pertains to a particular package in Trilinos, it's worthwhile to start the
title with "PackageName: ".
-->
When I try to link packages/panzer/adapters-stk/test/solver/PanzerAdaptersSTK_solver.exe I get a missing tpetra symbol for intel debug static, but intel opt static works.. No idea why. This is with a RHEL7 machine using all sems and Ross' new build scripts.
<!---
Note that anything between these delimiters is a comment that will not appear
in the issue description once created. Click on the Preview tab to see what
everything will look like when you submit.
-->
Here is the error message I see, no idea why the xpetra epetra map is looking for something tpetra??
```
packages/xpetra/src/libxpetra.a(Xpetra_EpetraMap.cpp.o): In function `Tpetra::Details::LocalMap<int, long, Kokkos::Device<Kokkos::OpenMP, Kokkos::HostSpace> >::LocalMap()':
```
Here is my link line
```
: && /projects/sems/install/rhel7-x86_64/sems/compiler/intel/17.0.1/openmpi/1.10.1/bin/mpicxx --std=c++11 -g -fopenmp -g packages/panzer/adapters-stk/test/solver/CMakeFiles/PanzerAdaptersSTK_solver.dir/solver.cpp.o packages/panzer/adapters-stk/test/solver/CMakeFiles/PanzerAdaptersSTK_solver.dir/__/__/__/__/phalanx/test/Utilities/Phalanx_UnitTestMain.cpp.o -o packages/panzer/adapters-stk/test/solver/PanzerAdaptersSTK_solver.exe packages/panzer/adapters-stk/src/libpanzer-stk.a packages/muelu/adapters/libmuelu-adapters.a packages/muelu/src/Interface/libmuelu-interface.a packages/muelu/src/libmuelu.a packages/teko/src/libteko.a packages/ifpack2/adapters/libifpack2-adapters.a packages/ifpack2/src/libifpack2.a packages/seacas/libraries/ioss/src/main/libio_info_lib.a packages/seacas/libraries/ioss/src/init/libIonit.a packages/seacas/libraries/ioss/src/transform/libIotr.a packages/seacas/libraries/ioss/src/heartbeat/libIohb.a packages/seacas/libraries/ioss/src/gen_struc/libIogs.a packages/seacas/libraries/ioss/src/generated/libIogn.a packages/seacas/libraries/ioss/src/visualization/libIovs.a packages/seacas/libraries/ioss/src/pamgen/libIopg.a packages/seacas/libraries/ioss/src/exo_fac/libIoexo_fac.a packages/seacas/libraries/ioss/src/exo_fpp/libIofx.a packages/seacas/libraries/ioss/src/exodus/libIoex.a packages/seacas/libraries/ioss/src/libIoss.a packages/seacas/libraries/exodus/libexodus.a packages/panzer/disc-fe/src/libpanzer-disc-fe.a packages/panzer/dof-mgr/src/libpanzer-dof-mgr.a packages/phalanx/src/libphalanx.a packages/panzer/core/src/libpanzer-core.a packages/piro/src/libpiro.a packages/muelu/adapters/libmuelu-adapters.a packages/muelu/src/Interface/libmuelu-interface.a packages/muelu/src/libmuelu.a packages/intrepid2/src/libintrepid2.a packages/sacado/src/libsacado.a packages/tempus/src/libtempus.a packages/rythmos/src/librythmos.a packages/nox/src-loca/src-thyra/liblocathyra.a packages/nox/src-loca/src-epetra/liblocaepetra.a packages/nox/src-loca/src-lapack/liblocalapack.a packages/nox/src-loca/src/libloca.a packages/nox/src-epetra/libnoxepetra.a packages/nox/src-lapack/libnoxlapack.a packages/nox/src/libnox.a packages/teko/src/libteko.a packages/ifpack2/adapters/libifpack2-adapters.a packages/ifpack2/src/libifpack2.a packages/zoltan2/src/libzoltan2.a packages/anasazi/tpetra/src/libanasazitpetra.a packages/anasazi/epetra/util/ModeLaplace/libModeLaplace.a packages/anasazi/epetra/src/libanasaziepetra.a packages/anasazi/src/libanasazi.a packages/stk/stk_io/stk_io/util/libstk_io_util.a packages/stk/stk_io/stk_io/libstk_io.a packages/seacas/libraries/ioss/src/main/libio_info_lib.a packages/seacas/libraries/ioss/src/init/libIonit.a packages/seacas/libraries/ioss/src/transform/libIotr.a packages/seacas/libraries/ioss/src/heartbeat/libIohb.a packages/seacas/libraries/ioss/src/gen_struc/libIogs.a packages/seacas/libraries/ioss/src/generated/libIogn.a packages/seacas/libraries/ioss/src/visualization/libIovs.a packages/seacas/libraries/ioss/src/pamgen/libIopg.a packages/seacas/libraries/ioss/src/exo_fac/libIoexo_fac.a packages/seacas/libraries/ioss/src/exo_fpp/libIofx.a packages/seacas/libraries/ioss/src/exodus/libIoex.a packages/seacas/libraries/ioss/src/libIoss.a packages/pamgen/src/libpamgen_extras.a packages/pamgen/src/libpamgen.a packages/stk/stk_mesh/stk_mesh/base/libstk_mesh_base.a packages/shards/src/libshards.a packages/stk/stk_topology/stk_topology/libstk_topology.a packages/stk/stk_util/stk_util/use_cases/libstk_util_use_cases.a packages/stk/stk_util/stk_util/registry/libstk_util_registry.a packages/stk/stk_util/stk_util/diag/libstk_util_diag.a packages/stk/stk_util/stk_util/environment/libstk_util_env.a packages/stk/stk_util/stk_util/parallel/libstk_util_parallel.a packages/stk/stk_util/stk_util/util/libstk_util_util.a /projects/sems/install/rhel7-x86_64/sems/tpl/boost/1.59.0/intel/17.0.1/base/lib/libboost_program_options.so /projects/sems/install/rhel7-x86_64/sems/tpl/boost/1.59.0/intel/17.0.1/base/lib/libboost_system.so packages/seacas/libraries/aprepro_lib/libaprepro_lib.a packages/seacas/libraries/exodus/libexodus.a -L/projects/sems/install/rhel7-x86_64/sems/tpl/hdf5/1.8.12/intel/17.0.1/openmpi/1.10.1/parallel/lib -L/projects/sems/install/rhel7-x86_64/sems/tpl/boost/1.59.0/intel/17.0.1/base/lib -L/projects/sems/install/rhel7-x86_64/sems/tpl/netcdf/4.4.1/intel/17.0.1/openmpi/1.10.1/exo_parallel/lib -L/lib -lboost_program_options -lboost_system -lnetcdf -lpnetcdf -lhdf5 -lcurl -lhdf5_hl -lz packages/stratimikos/src/libstratimikos.a packages/stratimikos/adapters/belos/src/libstratimikosbelos.a packages/stratimikos/adapters/amesos2/src/libstratimikosamesos2.a packages/stratimikos/adapters/aztecoo/src/libstratimikosaztecoo.a packages/stratimikos/adapters/amesos/src/libstratimikosamesos.a packages/stratimikos/adapters/ml/src/libstratimikosml.a packages/stratimikos/adapters/ifpack/src/libstratimikosifpack.a packages/amesos2/src/libamesos2.a packages/ml/src/libml.a packages/galeri/src-xpetra/libgaleri-xpetra.a packages/galeri/src-epetra/libgaleri-epetra.a packages/ifpack/src/libifpack.a packages/amesos/src/libamesos.a packages/common/auxiliarySoftware/SuiteSparse/src/libtrilinosss.a packages/belos/xpetra/src/libbelosxpetra.a packages/belos/tpetra/src/libbelostpetra.a packages/belos/epetra/src/libbelosepetra.a packages/belos/src/libbelos.a packages/xpetra/sup/libxpetra-sup.a packages/xpetra/src/libxpetra.a packages/thyra/adapters/tpetra/src/libthyratpetra.a packages/thyra/adapters/epetraext/src/libthyraepetraext.a packages/epetraext/src/libepetraext.a packages/thyra/adapters/epetra/src/libthyraepetra.a packages/thyra/core/src/libthyracore.a packages/rtop/src/librtop.a packages/tpetra/core/ext/libtpetraext.a packages/tpetra/core/inout/libtpetrainout.a packages/tpetra/core/src/libtpetra.a packages/kokkos-kernels/src/libkokkoskernels.a packages/kokkos/algorithms/src/libkokkosalgorithms.a packages/kokkos/containers/src/libkokkoscontainers.a packages/tpetra/classic/LinAlg/libtpetraclassiclinalg.a packages/tpetra/classic/NodeAPI/libtpetraclassicnodeapi.a packages/tpetra/classic/src/libtpetraclassic.a packages/aztecoo/src/libaztecoo.a packages/triutils/src/libtriutils.a packages/epetra/src/libepetra.a packages/teuchos/kokkoscomm/src/libteuchoskokkoscomm.a packages/teuchos/kokkoscompat/src/libteuchoskokkoscompat.a packages/teuchos/remainder/src/libteuchosremainder.a packages/teuchos/numerics/src/libteuchosnumerics.a packages/teuchos/comm/src/libteuchoscomm.a packages/teuchos/parameterlist/src/libteuchosparameterlist.a packages/teuchos/parser/src/libteuchosparser.a -mkl packages/teuchos/core/src/libteuchoscore.a packages/kokkos/core/src/libkokkoscore.a -ldl packages/zoltan/src/libzoltan.a -lm && :
```
<!---
Feel free to delete anything from this template that is not applicable to the
issue you are submitting.
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@trilinos/<teamName>
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Lables: Choose any applicable package names from the Labels drop-down on the
right. Additionally, choose a label to indicate the type of issue, for
instance, bug, build, documentation, enhancement, etc.
-->
## Expectations
<!---
Tell us what you think should happen, how you think things should work, what
you would like to see in the documentation, etc.
-->
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
## Motivation and Context
<!---
How has this expectation failure affected you? What are you trying to
accomplish? Why do we need to address this? What does it have to do with
anything? Providing context helps us come up with a solution that is most
useful in the real world.
-->
## Definition of Done
<!---
Tell us what needs to happen. If necessary, give us a task list along the
lines of:
- [ ] First do this.
- [ ] Then do that.
- [ ] Also this other thing.
-->
## Possible Solution
<!---
Not obligatory, but suggest a fix for the bug or documentation, or suggest
ideas on how to implement the addition or change.
-->
## Steps to Reproduce
<!---
Provide a link to a live example, or an unambiguous set of steps to reproduce
this issue. Include code to reproduce, if relevant.
1. Do this.
1. Do that.
1. Shake fist angrily at computer.
-->
## Your Environment
<!---
Include relevant details about your environment such that we can replicate this
issue.
-->
- **Relevant repo SHA1s:**
- **Relevant configure flags or configure script:**
- **Operating system and version:**
- **Compiler and TPL versions:**
## Related Issues
<!---
If applicable, let us know how this bug is related to any other open issues:
-->
* Blocks
* Is blocked by
* Follows
* Precedes
* Related to
* Part of
* Composed of
## Additional Information
<!---
Anything else that might be helpful for us to know in addressing this issue:
* Configure log file:
* Build log file:
* Test log file:
* When was the last time everything worked (date/time; SHA1s; etc.)?
* What did you do that made the bug rear its ugly head?
* Have you tried turning it off and on again?
-->
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4036Ifpack2: Build warning in test, suggesting incorrectness or unexpected behavior2018-12-12T00:36:08ZJames WillenbringIfpack2: Build warning in test, suggesting incorrectness or unexpected behavior*Created by: mhoemmen*
@trilinos/ifpack2
I get the following build warning with GCC 7.2 and CUDA (ATDM build):
```
.../Trilinos/packages/ifpack2/test/unit_tests/Ifpack2_UnitTestBlockTriDiContainerUtil.hpp: In lambda function:
/sc...*Created by: mhoemmen*
@trilinos/ifpack2
I get the following build warning with GCC 7.2 and CUDA (ATDM build):
```
.../Trilinos/packages/ifpack2/test/unit_tests/Ifpack2_UnitTestBlockTriDiContainerUtil.hpp: In lambda function:
/scratch/mhoemme/sparc/Trilinos/packages/ifpack2/test/unit_tests/Ifpack2_UnitTestBlockTriDiContainerUtil.hpp:249:34: warning: comparison of constant ‘1’ with boolean expression is always false [-Wbool-compare]
input.tolerance = norm_based > 1 ? tol : 0;
~~~~~~~~~~~^~~
```
It looks like this is an operator precedence issue.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4035Xpetra: Build warnings with GCC 7.2 and CUDA (ATDM build)2018-12-16T21:53:36ZJames WillenbringXpetra: Build warnings with GCC 7.2 and CUDA (ATDM build)*Created by: mhoemmen*
@trilinos/xpetra
```
.../Trilinos/packages/xpetra/src/CrsMatrix/Xpetra_TpetraCrsMatrix.hpp(955): warning: missing return statement at end of non-void function "Xpetra::TpetraCrsMatrix<Scalar, int, int, Xpetra:...*Created by: mhoemmen*
@trilinos/xpetra
```
.../Trilinos/packages/xpetra/src/CrsMatrix/Xpetra_TpetraCrsMatrix.hpp(955): warning: missing return statement at end of non-void function "Xpetra::TpetraCrsMatrix<Scalar, int, int, Xpetra::EpetraNode>::getLocalMatrix [with Scalar=double]"
detected during:
instantiation of "Xpetra::TpetraCrsMatrix<Scalar, int, int, Xpetra::EpetraNode>::local_matrix_type Xpetra::TpetraCrsMatrix<Scalar, int, int, Xpetra::EpetraNode>::getLocalMatrix() const [with Scalar=double]"
(613): here
instantiation of "Xpetra::TpetraCrsMatrix<Scalar, int, int, Xpetra::EpetraNode>::TpetraCrsMatrix(const Teuchos::RCP<const Xpetra::Map<int, int, Xpetra::EpetraNode>> &, size_t, Xpetra::ProfileType, const Teuchos::RCP<Teuchos::ParameterList> &) [with Scalar=double]"
.../Trilinos/packages/xpetra/src/CrsMatrix/Xpetra_CrsMatrixFactory.hpp(288): here
```https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4029Tpetra: "Default default" GlobalOrdinal type is int; should be 64 bits by def...2019-04-13T22:29:39ZJames WillenbringTpetra: "Default default" GlobalOrdinal type is int; should be 64 bits by default*Created by: mhoemmen*
@trilinos/tpetra @rppawlo
## Expectations
If you enable a 64-bit GlobalOrdinal type, then the default GlobalOrdinal type should be 64 bits.
## Current Behavior
Even if you enable (a) 64-bit GlobalOrdi...*Created by: mhoemmen*
@trilinos/tpetra @rppawlo
## Expectations
If you enable a 64-bit GlobalOrdinal type, then the default GlobalOrdinal type should be 64 bits.
## Current Behavior
Even if you enable (a) 64-bit GlobalOrdinal type(s), the default GlobalOrdinal type is still `int`, unless you explicitly disable GlobalOrdinal=int at configure time.
## Possible Solution
Change priority order of macros in Tpetra header file. Run downstream tests.
## Related Issues
* Blocks #2548
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4014Panzer: multiblock exodus unit test2018-12-06T21:03:03ZJames WillenbringPanzer: multiblock exodus unit test*Created by: rppawlo*
Need to add a panzer unit test to the stk_interface that exercises the exodus reader with multiblock where not all element blocks exist on every processor. We seem to have had a regression here.
Patched in #4013...*Created by: rppawlo*
Need to add a panzer unit test to the stk_interface that exercises the exodus reader with multiblock where not all element blocks exist on every processor. We seem to have had a regression here.
Patched in #4013
@bathmatt @eric-c-cyr https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3991MueLu: MueLu hangs when try to "export data" such as matrices after repartiti...2019-01-23T22:50:02ZJames WillenbringMueLu: MueLu hangs when try to "export data" such as matrices after repartitioning has occurred*Created by: pwxy*
MueLu hangs when try to "export data" such as matrices after repartitioning has occurred.
The MPI processes that have dropped out after repartitioning will throw and the run hangs:
```
p=3: *** Caught standard st...*Created by: pwxy*
MueLu hangs when try to "export data" such as matrices after repartitioning has occurred.
The MPI processes that have dropped out after repartitioning will throw and the run hangs:
```
p=3: *** Caught standard std::exception of type 'Teuchos::bad_any_cast' :
../../packages/muelu/src/Interface/../MueCentral/MueLu_VariableContainer.hpp:103:
Throw number = 17
Throw test that evaluated to true: data_->type() != typeid(T)
Error, cast to type Data<Teuchos::RCP<Xpetra::Matrix<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::OpenMP, Kokkos::HostSpace> > >> failed since the actual underlying type is 'Teuchos::RCP<Xpetra::Operator<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::OpenMP, Kokkos::HostSpace> > >!
This is develop Trilinos cloned this morning (Dec 4, 2018), SHA1 573e3290b0500eee45e582cb8fcee0b1c6476cec
Example MueLu_Driver.exe run that exhibits this issue:
mpirun -n 4 MueLu_Driver.exe --matrixType=Laplace3D --nx=50 --ny=50 --nz=4 --mx=2 --my=2 --mz=1
[ptlin@ceerws3709 scaling]$ cat scaling.xml
<ParameterList name="MueLu">
<!--
For a generic symmetric scalar problem, these are the recommended settings for MueLu.
-->
<!-- =========== GENERAL ================ -->
<Parameter name="verbosity" type="string" value="high"/>
<Parameter name="coarse: max size" type="int" value="1000"/>
<Parameter name="multigrid algorithm" type="string" value="sa"/>
<!-- reduces setup cost for symmetric problems -->
<Parameter name="transpose: use implicit" type="bool" value="true"/>
<!-- start of default values for general options (can be omitted) -->
<Parameter name="max levels" type="int" value="10"/>
<Parameter name="number of equations" type="int" value="1"/>
<Parameter name="sa: use filtered matrix" type="bool" value="true"/>
<!-- end of default values -->
<!-- =========== AGGREGATION =========== -->
<Parameter name="aggregation: type" type="string" value="uncoupled"/>
<Parameter name="aggregation: drop scheme" type="string" value="classical"/>
<!-- Uncomment the next line to enable dropping of weak connections, which can help AMG convergence
for anisotropic problems. The exact value is problem dependent. -->
<!-- <Parameter name="aggregation: drop tol" type="double" value="0.02"/> -->
<!-- =========== SMOOTHING =========== -->
<Parameter name="smoother: type" type="string" value="CHEBYSHEV"/>
<ParameterList name="smoother: params">
<Parameter name="chebyshev: degree" type="int" value="2"/>>
<Parameter name="chebyshev: ratio eigenvalue" type="double" value="7"/>
<Parameter name="chebyshev: min eigenvalue" type="double" value="1.0"/>
<Parameter name="chebyshev: zero starting solution" type="bool" value="true"/>
</ParameterList>
<!-- =========== REPARTITIONING =========== -->
<Parameter name="repartition: enable" type="bool" value="true"/>
<Parameter name="repartition: partitioner" type="string" value="zoltan2"/>
<Parameter name="repartition: start level" type="int" value="2"/>
<Parameter name="repartition: min rows per proc" type="int" value="800"/>
<Parameter name="repartition: max imbalance" type="double" value="1.1"/>
<Parameter name="repartition: remap parts" type="bool" value="false"/>
<!-- start of default values for repartitioning (can be omitted) -->
<Parameter name="repartition: remap parts" type="bool" value="true"/>
<Parameter name="repartition: rebalance P and R" type="bool" value="false"/>
<ParameterList name="repartition: params">
<Parameter name="algorithm" type="string" value="multijagged"/>
</ParameterList>
<!-- end of default values -->
<ParameterList name="export data">
<Parameter name="A" type="string" value="{2}"/>
</ParameterList>
</ParameterList>
[ptlin@ceerws3709 scaling]$
```
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3981Belos: Add a users guide2018-12-03T20:44:16ZJames WillenbringBelos: Add a users guide*Created by: mhoemmen*
@hkthorn @trilinos/belos
Requested by @vbrunini. Current source of Belos documentation is Doxygen: https://trilinos.org/docs/dev/packages/belos/doc/html/index.html . This is a good start, but it's missing th...*Created by: mhoemmen*
@hkthorn @trilinos/belos
Requested by @vbrunini. Current source of Belos documentation is Doxygen: https://trilinos.org/docs/dev/packages/belos/doc/html/index.html . This is a good start, but it's missing the following features:
1. "How do I create a solver factory?" (Our recent DII work obfuscated the class hierarchy a bit.)
2. "How do I make the solver that I want?", i.e., "What is the mapping from solver string names to solvers?"
3. "What is a set of parameters that all Belos solvers accept?"
4. "Given a Belos solver, what parameters does it accept?" (This information exists only in the Doxygen documentation; its location may not be obvious to users.)
We could start with the existing Doxygen documentation, as it's the easiest to find and already exists.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3959Website: Trilinos Capability Area Information Out of Date2018-12-08T17:52:21ZJames WillenbringWebsite: Trilinos Capability Area Information Out of Date*Created by: csiefer2*
Information on Trilinos product leads still lists the old capability areas:
https://trilinos.org/capability-areas/
https://trilinos.github.io/capability-areas.html
This leaves people who don't know who is i...*Created by: csiefer2*
Information on Trilinos product leads still lists the old capability areas:
https://trilinos.org/capability-areas/
https://trilinos.github.io/capability-areas.html
This leaves people who don't know who is in charge of what no way of finding that information out.
@trilinos/framework
@trilinos/linear-solvers
@trilinos/trilinos-web-portal