#1665: move higher order restriction parameters from CarpetLib to Carpet
----------------------+-----------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: defect | Status: new
Priority: optional | Milestone:
Component: Carpet | Version: development version
Keywords: |
----------------------+-----------------------------------------------------
currently they are handled in an usual manner in that they are direct
parameters of CarpetLib. The other similar parameters (eg
prolongation_order_space) are parameters of Carpet which tells CarpetLib
what to do.
This will deprecate the parameters in CarpetLib and may also remove the
{{{use_higher_order_parameter}}} altogether since it can be deduced from
{{{restriction_order_space}}}.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1665>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1666: Consider using BitBucket "pull request" feature
----------------------------------+-----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit trac | Version: development version
Keywords: |
----------------------------------+-----------------------------------------
BitBucket allows a user to create a fork (or branch) of a repository and
request that it be pulled into the master branch. Comments can be made on
the pull request, and the discussion of the change will then be on the
BitBucket website, rather than in TRAC. Pull requests are more convenient
than patches, as there is no need to manually download and apply patch
files, and there is a clear audit trail of what was reviewed and when.
However, since not all the ET repositories are in BitBucket, this would
lead to fragmentation of the review process, with some changes being
discussed in TRAC and some in BitBucket.
(See the discussion at
http://lists.einsteintoolkit.org/pipermail/users/2014-October/003816.html
regarding notifications of pull requests.)
Discuss.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1666>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1719: Automatically run build and test on pull requests
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Server Infrastructure | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
It would be desirable to have the Jenkins build-and-test system
automatically run for pull requests, so that it is clear that they can be
merged without breaking anything. I don't know whether this is possible
with Bitbucket, but Bitbucket does have Jenkins support and I've seen the
"build-and-test of pull requests idea" work well with projects hosted on
GitHub. See the Homebrew project for a good example. (imported from
https://trac.einsteintoolkit.org/ticket/1666#comment:1)
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1719>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1669: No check for installed libraries in ExternalLibraries/pciutils
-----------------------------------------+----------------------------------
Reporter: joachim.frieben@… | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: pciutils |
-----------------------------------------+----------------------------------
It seems that the configure script in ExternalLibraries/pciutils does not
look for an installed instance of pciutils. Therefore, the package is
built from scratch even if as in my case both required packages pciutils
and pciutils-devel are installed. It would be nice to have this check as
it is usually the case for other external libraries. Thanks!
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1669>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1672: Simfactory: add --basedir=@BASEDIR@ to all submit scripts
---------------------------------+------------------------------------------
Reporter: bmundim | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version: development version
Keywords: Simfactory basedir |
---------------------------------+------------------------------------------
I would like to add the option, --basedir=@BASEDIR@, choosing the
simulation directory to all simfactory submit scripts at
./mdb/submitscripts. I hope they become more homogeneous with respect to
features simfactory already supports.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1672>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1679: Update OpenMPI, hwloc
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
Thorns MPI and hwloc should be updated to current version.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1679>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1680: GetComponents: do not hardcode svn --non-interactive
-------------------------------------------+--------------------------------
Reporter: bmundim | Owner: eric9
Type: defect | Status: new
Priority: minor | Milestone:
Component: GetComponents | Version: development version
Keywords: GetComponents non interactive |
-------------------------------------------+--------------------------------
While testing the ET new trunk on my laptop running Kubuntu,
I noticed that GetComponents fails to download thorns from
private svn repositories:
svn: E170001: Unable to connect to a repository at URL
'https://svn.blabla/trunk'
svn: E170001: OPTIONS of 'https://svn.blabla/trunk': authorization failed:
Could not authenticate to server: rejected Basic challenge
(https://svn.aei.mpg.de)
The solution for this was to strip out the svn option --non-interactive
hardcoded in GetComponents. kwallet would then ask for my password (only
once)
in order to unlock my svn passwords and the checkout would proceed
normally.
Note that I have configured ~/.subversion/config to store my passwords on
kwallet:
password-stores = kwallet
other users could have used gnome-keyring, keychain, etc.
It would be nice then to allow the user to use --non-interactive option or
not
instead of keeping it hardcoded. Any thoughts against it? or better
suggestions
on handling private svn repos?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1680>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1691: Time integration of grid arrays with MoL is incorrect when there is more
than one component per process
--------------------+-------------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Cactus | Version: development version
Keywords: |
--------------------+-------------------------------------------------------
MoL integrates its variables in local mode (loop over components), and
grid arrays are stored per process, so MoL integrates evolved grid arrays
multiple times, leading to wrong results, if there is more than one
component per process. I believe the best solution is to move integration
of grid arrays into a separate function, scheduled in a different mode
(MoL_AddArrays), either global or local. However, a quick short-term
"fix" is to copy the check that Slab makes that it is running with only a
single component per process. Users can then work around the problem by
running on more processes, and won't get silent wrong results.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1691>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1719: spam test ticket
-----------------------+----------------------------------------------------
Reporter: anonymous | Owner:
Type: defect | Status: new
Priority: unset | Milestone:
Component: Other | Version: development version
Keywords: |
-----------------------+----------------------------------------------------
Avangar Technologies announces the beginning of a new unprecendented
global employment campaign.
reviser yeller winers butchery twenties
Due to company's exploding growth Avangar is expanding business to the
European region.
During last employment campaign over 1500 people worldwide took part in
Avangar's business
and more than half of them are currently employed by the company. And now
we are offering you
one more opportunity to earn extra money working with Avangar
Technologies.
druggists blame classy gentry Aladdin
We are looking for honest, responsible, hard-working people that can
dedicate 2-4 hours of their
time per day and earn extra £300-500 weekly. All offered positions are
currently part-time
and give you a chance to work mainly from home.
lovelies hockey Malton meager reordered
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1719>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1707: Delay build of GSL until after CST has finished
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
See
<https://svn.cactuscode.org/projects/ExternalLibraries/GSL/branches/eschnett
/delayed-build>.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1707>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit