Log of /branches/diaplayground/escriptcore/test/python/test_linearPDEs.py
Parent Directory
| 
Revision Log
Revision
5136 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Sep 9 07:13:55 2014 UTC
(4 years, 5 months ago)
by
caltinay
File length: 202517 byte(s)
Diff to
previous 4940
ripley now supports paso solvers again and returns an appropriate matrix type
id. Changed the getSystemMatrixTypeId() method to take a full SolverBuddy
instance and made some other simplifications.
Revision
4821 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Apr 1 04:58:33 2014 UTC
(4 years, 10 months ago)
by
sshaw
Original Path:
trunk/escriptcore/test/python/test_linearPDEs.py
File length: 201789 byte(s)
Diff to
previous 4786
moved SolverOptions to c++, split into SolverOptions for the options and SolverBuddy as the state as a precursor to per-pde solving... does break some use cases (e.g. pde.getSolverOptions().DIRECT will now fail, new value access is with SolverOptions.DIRECT), examples and documentation updated to match
Revision
4255 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Wed Feb 27 03:06:21 2013 UTC
(5 years, 11 months ago)
by
jfenwick
Original Path:
trunk/escript/test/python/test_linearPDEs.py
File length: 229190 byte(s)
Diff to
previous 4242
Hopefully, this will address the interpolation problems.
New canInterpolate() function exposed to python which calls probeInterpolation
AbstractDomain now has an additional virtual.
preferredIntrpolationOnDomain()
This will return 0 if interpolation is impossible, 1 if possible and preferred.
It will return -1 if interpolation is possible and preferred in the
oposite direction.
A value of -1 does not say that the proposed interpolation is possible or not.
Rather it indicates "please use the other way".
If you really _need_ to test it that way, use probeInterpolationOnDomain
Revision
4018 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Oct 11 04:43:39 2012 UTC
(6 years, 4 months ago)
by
jfenwick
Original Path:
trunk/escript/test/python/test_linearPDEs.py
File length: 197909 byte(s)
Diff to
previous 4005
Used "new" raise syntax in a few places
Fixed some tabbing
Fixed some funnies involving changes to xrange/range
added a quick and nasty __hash__ function to Symbol
def __hash__(self):
return id(self)
This does mean that __hash__ and == do not match exactly. Not sure if that matters for our purposes
Revision
1312 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Mon Sep 24 06:18:44 2007 UTC
(11 years, 5 months ago)
by
ksteube
Original Path:
trunk/escript/test/python/test_linearPDEs.py
File length: 66751 byte(s)
Diff to
previous 1072
The MPI branch is hereby closed. All future work should be in trunk.
Previously in revision 1295 I merged the latest changes to trunk into trunk-mpi-branch.
In this revision I copied all files from trunk-mpi-branch over the corresponding
trunk files. I did not use 'svn merge', it was a copy.
Revision
700 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Apr 6 00:13:40 2006 UTC
(12 years, 10 months ago)
by
gross
Original Path:
trunk/escript/test/python/test_linearPDEs.py
File length: 30949 byte(s)
Copied from:
trunk/escript/py_src/test_linearPDEs.py revision 699
Diff to
previous 637
A few changes in the build mechanism and the file structure so scons can build release tar files:
* paso/src/Solver has been moved to paso/src
* all test_.py are now run_.py files and are assumed to be passing python tests. they can run by
scons py_tests and are part of the release test set
* escript/py_src/test_ are moved to escript/test/python and are installed in to the build directory
(rather then the PYTHONPATH).
* all py files in test/python which don't start with run_ or test_ are now 'local_py_tests'. they are installed i
by not run automatically.
* CppUnitTest is now treated as a escript module (against previous decisions).
* scons realse builds nor tar/zip files with relvant source code (src and tests in seperate files)
the python tests don't pass yet due to path problems.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
enter a numeric revision.
