Directory CCA/Components/Wasatch/Operators/

Total Files:
10
Deleted Files:
0
Lines of Code:
1483

[root]/CCA/Components/Wasatch/Operators

Lines of Code

CCA/Components/Wasatch/Operators/ Lines of Code

Developers

Author Changes Lines of Code Lines per Change
Totals 34 (100.0%) 70 (100.0%) 2.0
tsaad 6 (17.6%) 29 (41.4%) 4.8
jas 14 (41.2%) 20 (28.6%) 1.4
dav 4 (11.8%) 19 (27.1%) 4.7
ahumphrey 2 (5.9%) 2 (2.9%) 1.0
jsutherland 8 (23.5%) 0 (0.0%) 0.0

Most Recent Commits

dav 2016-09-06 12:58 Rev.: 55704


The main updates in this commit are to configure and the build system:
A number of bullet-proofing / clean-ups have been added to configure,
and the dependency of Arches on Wasatch has been removed. (Note,
Arches still needs to build TabProps/RadProps in the Wasatch 3P.) I
have tested this on several machines, but it is possible that it will
now catch some peoples' bad configure lines (that 'worked' before but
only accidentally). If your configure stops working because of this
commit, please let me know so I can help you fix it. -Dav

M configure
M configure.ac

- Force bad configure command line arguments to be errors instead of warnings.
This will help avoid users accidentally mis-typing an arg and not noticing.
The autoconf configure system does not normally allow this to happen as
their philosophy is that configure usually calls a sub-configure and passes
args down to it... Thus configure "ignores" bad args under the theory that
a "sub configure" will use them. However, we don't do this and this will
help catch configure command line typos and potentially save developers and
users a lot of headaches.

The bad news is that in order to get this functionality, we have
to hack the autconf'd generated configure script and add a
variable (enable_option_checking=fatal) at the top. I have added
a section to configure.ac with the information about doing this,
but anyone who re-generates configure needs to manually follow the
instructions.

- Configure now will immediately tell you if you have typed in an invalid
file/directory name (bad spelling, doesn't exist) for the --with flags.
Perviously this occurred manually each time (now it is part of the macro)
at the point in the configure script when the library was tested for.

- Fix handling of finding the C/C++ compilers and version checking better.
Configure now determines which compiler (eg: GCC, ICC, XLC) you are
using explicitly and can test for things (like version) appropriately.
The version check may still need to be updated a little.

- Updated the --with handling to know whether the flag was set or not. Previously
we were using a "" (blank) value, which was ambiguous.

- Flag --without as invalid on anything we don't explicitly handle (we
only handle without on a few things such as: --without-fortran or
--without-hypre).

- Allow the external Wasatch 3P to be specified on a single line (instead
of having a separate line for SpatialOps, ExprLib, etc) using
--with-wasatch3p=DIR. This will find all 4 W3P libs with one configure line.

- Got rid of IS_VS (wasn't set/used and don't know what it was for).

- While "no" and no (without quotes) are the same thing to configure, be consistent
and use "no" (with quotes) everywhere.

- Remove the BUILD_WASATCH_FOR_ARCHES logic, as we no longer need Wasatch to
be built for Arches.

- Clean up the left over files from relatively new MPI const test section.

- Fix the HAVE_ACCELERATE

- Update --enable-wasatch_3p to take a list of libs to build (in the case you only
wish to build a subset. Eg: --enable-wasatch_3p=radprops,tabprops
Pass list of libs to the build_wasatch_3p.sh script.

4 lines of code changed in 2 files:

  • CCA/Components/Wasatch/Operators: sub.mk (new)
ahumphrey 2016-06-13 11:46 Rev.: 55440

Replace usage of NULL macro (type int) with nullptr (pointer literal of type: nullptr_t).

nullptr is implicitly convertible and comparable to any pointer type or pointer-to-member type, but is not implicitly comparable to integral types, except that it is convertible to bool (explicitly).

2 lines of code changed in 2 files:

  • CCA/Components/Wasatch/Operators: UpwindInterpolant.cc (+2 -2)
dav 2016-05-16 14:48 Rev.: 55353


Fix the problem with fortran .h files (in Arches) not being generated correctly (on the binary
side) when CUDA is turned on.

Update the make system so that the dependency rules for CUDA enabled files are created
automatically. The user no-longer has to specify that each CUDA_ENABLED_SRCS .cu file
depends on the corresponding .cc file. Updated both Wasatch and Arches to use the
new approach.

M Makefile.in

- Add a 'function' (make-cuda-target) that will create CUDA dependency rules automatically,
instead of having the developer have to list the rules manually. This function must
be called in each sub.mk file that creates a CUDA_ENABLED_SRCS list.
- Remove all .cu and (mostly fortran) .h files from the <bin> side when
"make cleanreally" is called.

M configure
M configure.ac

- Put in check to verify that Uintah and Wasatch 3P are both (or neither) being
built with CUDA.
- Will also add Candera check once I get more info.

A include/sci_defs/wasatch_testdefs.h.in

- Place PoKitt and Candera defines in new (configure generated binary side) wasatch_defs.h
file.

M CCA/Components/Arches/sub.mk

- Fix fortran .h file dependency problem. Note, these dependencies are have been (and
continue to be) manually entered into the sub.mk file. However, previously, they
used multiple lines (eg: Source.$(OBJEXT) was written 5 times. You don't need to
do this, you can just list it once and then put all the files it depends on.

When building without CUDA, the fortran .h files are needed to create
the object files (eg: Source.o). However, if CUDA is turned on, then they are
needed to create the CUDA .cu file (eg: <bin>/Source.cu). Perviously, at least
on some machines (though the problem should have shown up on all machines?), the fortran
.h files were not being generated.

It appears that currently Arches/sub.mk is the only directory that has CUDA files that
are dependent on fortran .h files. If this occurs in other sub-dirs for Arches (as
CUDA is added to the code), then the same approach should be taken in those files.

M CCA/Components/Arches/ChemMix/sub.mk
M CCA/Components/Arches/CoalModels/sub.mk
M CCA/Components/Arches/LagrangianParticles/sub.mk
M CCA/Components/Arches/Operators/sub.mk
M CCA/Components/Arches/ParticleModels/sub.mk
M CCA/Components/Arches/PropertyModels/sub.mk
M CCA/Components/Arches/PropertyModelsV2/sub.mk
M CCA/Components/Arches/SourceTerms/sub.mk
M CCA/Components/Arches/Task/sub.mk
M CCA/Components/Arches/Transport/sub.mk
M CCA/Components/Arches/TransportEqns/sub.mk
M CCA/Components/Arches/Utility/sub.mk
M CCA/Components/Arches/WallHTModels/sub.mk
M CCA/Components/Wasatch/Expressions/BoundaryConditions/sub.mk
M CCA/Components/Wasatch/Expressions/MMS/sub.mk
M CCA/Components/Wasatch/Expressions/PostProcessing/sub.mk
M CCA/Components/Wasatch/Expressions/Turbulence/sub.mk
M CCA/Components/Wasatch/Expressions/sub.mk
M CCA/Components/Wasatch/Operators/sub.mk
M CCA/Components/Wasatch/Transport/sub.mk
M CCA/Components/Wasatch/sub.mk

- Call make system function make-cuda-target to generate CUDA .cu dependencies.

9 lines of code changed in 1 file:

  • CCA/Components/Wasatch/Operators: sub.mk (+9 -13)
dav 2016-04-25 16:50 Rev.: 55230


Fix the ability to make just Arches (--enable-arches instead of having to --enable-all-components).

M configure
M configure.ac

- Force the use of CMake 3.1+ if building Wasatch or VisIt).
- Add in RadProps info to W3P check.

M CCA/Components/Wasatch/Transport/sub.mk
M CCA/Components/Wasatch/Expressions/sub.mk
M CCA/Components/Wasatch/Operators/sub.mk
M CCA/Components/Arches/CoalModels/sub.mk
M CCA/Components/Arches/sub.mk

- Remove superfluous white space.
- Alphabetize.
- Fix comment typo (cut/paste error).
- Untabify (as appropriate).

M CCA/Components/Wasatch/sub.mk

- Same as above and:
- Fix the problem where CUDA_ENABLED_SRCS was not set if just building Arches.
- A number of files (eg: BCHelper.cc) were listed twice in the list of sources.

M Core/Grid/UnknownVariable.h

- Remove warning (Exception is now in the Uintah namespace so don't need to qualify it).

6 lines of code changed in 1 file:

  • CCA/Components/Wasatch/Operators: sub.mk (+6 -16)
jsutherland 2016-04-18 18:02 Rev.: 55205

Eliminate conflict between Wasatch's Extrapolate operator and SpatialOps' Extrapolant operator. We should consolidate these if possible...

0 lines of code changed in 8 files:

  • CCA/Components/Wasatch/Operators: Extrapolant.cc (changed), Extrapolant.h (changed), OperatorTypes.h (new), Operators.cc (changed)
tsaad 2016-03-25 17:20 Rev.: 55127

one more try at fixing Arches build

2 lines of code changed in 1 file:

  • CCA/Components/Wasatch/Operators: sub.mk (+2 -2)
tsaad 2016-03-25 15:24 Rev.: 55122

GPU-ready particle operators. Commit on behalf of Dr. Babak Goshayeshi.

8 lines of code changed in 2 files:

  • CCA/Components/Wasatch/Operators: Operators.cc (+3 -2), sub.mk (+5 -6)
jas 2016-03-15 18:24 Rev.: 55024

Move non-conflicting classes that were in SCIRun namespace to Uintah namespace.

10 lines of code changed in 1 file:

  • CCA/Components/Wasatch/Operators: Operators.cc (+10 -10)
tsaad 2016-02-23 14:45 Rev.: 54885

cleanup a bunch of header inclusions and move some code around to simplify operator usage

19 lines of code changed in 3 files:

  • CCA/Components/Wasatch/Operators: OperatorTypes.h (+19), Operators.h (new)
jas 2016-01-08 15:45 Rev.: 54640

Update copyright date to 2016.

10 lines of code changed in 13 files:

  • CCA/Components/Wasatch/Operators: Extrapolant.cc (+1 -1), Extrapolant.h (+1 -1), FluxLimiterInterpolant.cc (+1 -1), FluxLimiterInterpolant.h (+1 -1), OperatorTypes.h (+1 -1), Operators.cc (+1 -1), Operators.h (+1 -1), UpwindInterpolant.cc (+1 -1), UpwindInterpolant.h (+1 -1), sub.mk (+1 -1)
Generated by StatSVN 0.7.0