Trac January 2012

trac@lists.einsteintoolkit.org

1 participants
151 discussions

[Einstein Toolkit] #492: Cannot add attachments to tickets "IOError: Client read error (Timeout?) "
by Einstein Toolkit 17 Apr '12

17 Apr '12

#492: Cannot add attachments to tickets "IOError: Client read error (Timeout?) " ----------------------------------+----------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- This evening I am unable to add attachments to any tickets. After selecting the attachment file, clicking on the button to actually upload it leads to the error message below. This has happened before, but in those cases the attachment was added successfully despite the error message. In this case, no attachment appears. I have tried several times, and none of them worked. Mod_python error: "PythonHandler trac.web.modpython_frontend" Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/mod_python/apache.py", line 299, in HandlerDispatch result = object(req) File "/usr/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line 149, in handler gateway.run(dispatch_request) File "/usr/lib/python2.4/site-packages/trac/web/wsgi.py", line 89, in run response = application(self.environ, self._start_response) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 481, in dispatch_request return _dispatch_request(req, env, env_error) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 557, in _dispatch_request send_internal_error(env, req, sys.exc_info()) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 635, in send_internal_error description_en = get_description(lambda s, **kw: safefmt(s, kw)) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 631, in get_description req_args=pformat(req.args), sys_info=sys_info, File "/usr/lib/python2.4/site-packages/trac/web/api.py", line 212, in __getattr__ value = self.callbacks[name](self) File "/usr/lib/python2.4/site-packages/trac/web/api.py", line 195, in 'args': lambda req: arg_list_to_args(req.arg_list), File "/usr/lib/python2.4/site-packages/trac/web/api.py", line 212, in __getattr__ value = self.callbacks[name](self) File "/usr/lib/python2.4/site-packages/trac/web/api.py", line 560, in _parse_arg_list fs = cgi.FieldStorage(fp, environ=self.environ, keep_blank_values=True) File "/usr/lib64/python2.4/cgi.py", line 526, in __init__ self.read_multi(environ, keep_blank_values, strict_parsing) File "/usr/lib64/python2.4/cgi.py", line 646, in read_multi environ, keep_blank_values, strict_parsing) File "/usr/lib64/python2.4/cgi.py", line 528, in __init__ self.read_single() File "/usr/lib64/python2.4/cgi.py", line 661, in read_single self.read_lines() File "/usr/lib64/python2.4/cgi.py", line 683, in read_lines self.read_lines_to_outerboundary() File "/usr/lib64/python2.4/cgi.py", line 710, in read_lines_to_outerboundary line = self.fp.readline() File "/usr/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line 50, in readline return self.req.readline(size) IOError: Client read error (Timeout?) -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/492> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #533: Want graphical TRAC statistics
by Einstein Toolkit 17 Apr '12

17 Apr '12

#533: Want graphical TRAC statistics -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: Other | Version: Keywords: | -------------------------+-------------------------------------------------- It would be nice to have a few graphs on the TRAC front page showing some statistics, e.g. number of important open tickets, mean time before a ticket is closed, etc. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/533> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #358: FAQ entry
by Einstein Toolkit 17 Apr '12

17 Apr '12

#358: FAQ entry ----------------------------+----------------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus website | Version: Keywords: | ----------------------------+----------------------------------------------- For a new FAQ: Q: I get errors like "/usr/include/H5Dpublic.h:145: error: too many arguments to function ‘hid_t H5Dopen1(hid_t, const char*)’" A: The HDF5 library you use is either version 1.6 or defaults to it. If it is version 1.6.x, update to 1.8.x. If it is 1.8.x and it defaults to the 1.6 API version, you might be out of luck, especially on Debian Squeeze systems, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537414. What you can then do is to remove (comment) out the macro H5_USE_16_API_DEFAULT in /usr/include/H5pubconf.h. This isn't pretty, but is really a bug in the package and has to be fixed there. There is no way to switch to the new API on those systems, other than specifying the API version of each symbol separately, which would be even messier. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/358> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 8

[Einstein Toolkit] #576: Einstein toolkit installation problems
by Einstein Toolkit 17 Apr '12

17 Apr '12

#576: Einstein toolkit installation problems -----------------------------+---------------------------------------------- Reporter: Vassilios Mewes | Type: defect Status: new | Priority: major Milestone: | Component: Other Version: ET_2011_05 | Keywords: fortran 77 compilation errors -----------------------------+---------------------------------------------- Hello! I am trying to install the Einstein toolkit. I followed the instructions on the wiki (improved tutorial for new users) i am using the following command to build the configuration: ./simfactory/bin/sim build firsttry --thornlist=manifest/einsteintoolkit.th --optionlist=/home/vass/.cactus/config there are compilation errors of F77 sourcefiles, i tried both gfortran and the older g77 compiler, both give me numerous errors. I am using Ubuntu 11.04 x64... this is my configuration file (for some reason, cactus won't find gfortran unless i specify it in the configuration file, which i believe it should?): CPP = cpp FPP = cpp CC = gcc CXX = g++ F77 = gfortran F90 = gfortran ffppflags= -traditional MPI=OpenMPI here are the error messages when trying to build: above here it is building zlib and HDF5 and so on..i think these are all build correctly.. Checking consistency... Creating Thorn-Flesh bindings... Creating implementation bindings... Creating parameter bindings... Creating variable bindings... Creating schedule bindings... Creating function bindings... CST finished. Checking status of thorn Boundary ________________________________________________________________________ Checking status of thorn CoordBase ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn ADMCoupling ________________________________________________________________________ Checking status of thorn ADMMacros ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn AEILocalInterp ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn BLAS ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn Fortran ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn CarpetLib ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn IOUtil ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn CarpetEvolutionMask ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn zlib ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn CarpetMask ________________________________________________________________________ Checking status of thorn GSL ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn CarpetTracker ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn Constants ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn CoordGauge ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn SphericalSurface ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn DistortedBHIVP ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn EOSG_Base ________________________________________________________________________ Preprocessing /home/vass/Cactus/arrangements/EinsteinInitialData/DistortedBHIVP/src/DistortedBHIVP.F ________________________________________________________________________ Compiling /home/vass/Cactus/arrangements/EinsteinInitialData/DistortedBHIVP/src/DistortedBHIVP.F Preprocessing /home/vass/Cactus/arrangements/EinsteinInitialData/DistortedBHIVP/src/Stab3d.F Compiling /home/vass/Cactus/arrangements/EinsteinInitialData/DistortedBHIVP/src/Stab3d.F /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:476.6: 123 format(1x, 'Pars: amp',f8.5,' eta0',f8.5,' c',f8.5,' sigma',f8.5,' 1 Error: Bad continuation line at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:476.6: 123 format(1x, 'Pars: amp',f8.5,' eta0',f8.5,' c',f8.5,' sigma',f8.5,' 1 Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:477.6: &n',i3) 1 Error: Bad continuation line at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:477.6: &n',i3) 1 Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:519.2: qf(i,j,k) = amp*(1.00000000000000d0+c*cos(phigrd(k))**2)* 1 Error: Non-numeric character in statement label at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:521.72: $ /sigma**2)))*sin(qgrd(j))**n 1 Error: Unexpected STATEMENT FUNCTION statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:522.2: qfetaeta(i,j,k) = amp*(1.00000000000000d0+c*cos(phigrd(k)) 1 Error: Non-numeric character in statement label at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:529.72: $ )*sin(qgrd(j))**n 1 Error: Unexpected STATEMENT FUNCTION statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:530.2: qfqq(i,j,k) = amp*(-1.00000000000000d0+n)*n*(1.00000000 1 Error: Non-numeric character in statement label at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:538.72: $ /sigma**2)))*sin(qgrd(j))**n 1 Error: Unexpected STATEMENT FUNCTION statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:539.2: qfphi(i,j,k) = -2.00000000000000d0*amp*c*cos(phigrd(k))*(exp(- 1 Error: Non-numeric character in statement label at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:542.72: $ )*sin(phigrd(k))*sin(qgrd(j))**n 1 Error: Unexpected STATEMENT FUNCTION statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:543.2: qfphiphi(i,j,k) = -2.00000000000000d0*amp*c*cos(phigrd(k))**2* 1 Error: Non-numeric character in statement label at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:548.72: $ sin(phigrd(k))**2*sin(qgrd(j))**n 1 Error: Unexpected STATEMENT FUNCTION statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/Stab3d.f:105.6: 10 call usermv(cc,cn,cs,ce,cw,ct,cb,x,Ap,im,jm,km) 1 Error: Bad continuation line at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/Stab3d.f:105.6: 10 call usermv(cc,cn,cs,ce,cw,ct,cb,x,Ap,im,jm,km) 1 Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/Stab3d.f:138.4: 1 continue 1 Error: Non-numeric character in statement label at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/Stab3d.f:138.4: 1 continue 1 Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/Stab3d.f:181.72: goto 10 1 Error: Label 10 referenced at (1) is never defined /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/Stab3d.f:181.72: goto 10 1 Error: Label 10 referenced at (1) is never defined /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/Stab3d.f:194.72: if (rnorm .gt. tol) goto 1 1 Error: Label 1 referenced at (1) is never defined make[3]: *** [Stab3d.F.o] Error 1 make[3]: *** Waiting for unfinished jobs.... /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:1289.6: 110 continue 1 Error: Bad continuation line at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:1289.6: 110 continue 1 Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/DistortedBHIVP/DistortedBHIVP.f:474.17: write(*,123)amp,eta0,c,sigma,n 1 Error: FORMAT label 123 at (1) not defined Checking status of thorn EOSG_Polytrope ________________________________________________________________________ make[3]: *** [DistortedBHIVP.F.o] Error 1 make[2]: *** [make.checked] Error 2 make[1]: *** [/home/vass/Cactus/configs/firsttry/lib/libthorn_DistortedBHIVP.a] Error 2 make[1]: *** Waiting for unfinished jobs.... as thornlist i am using the einsteintoolkit.th thornlist as downloaded. the compilation errors are not exclusive to the distortedBHIVP file, when i comment this file to be build in the thornlist, other files won't be compiled as well... might be a system error, as i already had problems downloading the toolkit, it wouldn't download completely, but left out LocalInterp and LocalReduce for some strange reason. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/576> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #714: TmunuBase: stress_energy_storage should be a restricted parameter
by Einstein Toolkit 16 Apr '12

16 Apr '12

#714: TmunuBase: stress_energy_storage should be a restricted parameter -----------------------------------+---------------------------------------- Reporter: bmundim | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: TmunuBase | -----------------------------------+---------------------------------------- Hi, I was trying to use the stress_energy_storage parameter in TmunuBase to determine when to schedule or not a routine calculating the magnetic pressure (and friends). If storage is allocated for Tmunu then the magnetic pressure is calculated in the same routine. Otherwise, a separate routine would calculate the magnetic pressure. Keeping the routines always separate wouldn't be efficient when we do need the calculation and storage of Tmunu. Anyway, in order to do so, I needed to set stress_energy_storage as a restricted parameter (patch attached) in TmunuBase. Is there any reason for keeping this parameter private? Thanks. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/714> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #674: unable to create ticket unless logged in as real user
by Einstein Toolkit 13 Apr '12

13 Apr '12

#674: unable to create ticket unless logged in as real user ----------------------------------+----------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- I seem to be unable to create (or comment) on tickets unless I am logged in as a real user. Trac offers a feld "username or email" presumably to allow non-registered users to commnet and/or report errors. If I enter either "rhaas" or "roland" into that field I get: {{{ Trac Error Submission rejected as potential spam }}} It would be good I believe to let users report errors without having to create an account first. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/674> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 12

[Einstein Toolkit] #547: WALLTIME_HOURS incorrect
by Einstein Toolkit 09 Apr '12

09 Apr '12

#547: WALLTIME_HOURS incorrect ------------------------+--------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- The SimFactory variable WALLTIME_HOURS should be expanded to the walltime of the job, not the walltime which was requested on the command line. If the user specifies more walltime than the queue allows, SimFactory splits the job into several restarts to give the total walltime requested. However, parameter files expect WALLTIME_HOURS to be the walltime of the job, not of the simulation. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/547> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #646: PITTNullCode/NullNews does not build on BlueGene/P
by Einstein Toolkit 03 Apr '12

03 Apr '12

#646: PITTNullCode/NullNews does not build on BlueGene/P -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- PITTNullCode/NullNews does not build on BlueGene/P; the C++ STL reports an error. The reason seems to be that NULL is interpreted as integer constant instead of a pointer. An explicit case solves this problem there: {{{ Index: src/set_pointers.h =================================================================== --- src/set_pointers.h (revision 3) +++ src/set_pointers.h (working copy) @@ -1,9 +1,9 @@ // define pointer array for past timelevels! - vector<CCTK_REAL*> uBondiP(max_timelevels, NULL); - vector<CCTK_COMPLEX*> Psi4P(max_timelevels, NULL); - vector<CCTK_COMPLEX*> NewsP(max_timelevels, NULL); - vector<CCTK_COMPLEX*> NewsBP(max_timelevels, NULL); + vector<CCTK_REAL*> uBondiP(max_timelevels, (CCTK_REAL*)NULL); + vector<CCTK_COMPLEX*> Psi4P(max_timelevels, (CCTK_COMPLEX*)NULL); + vector<CCTK_COMPLEX*> NewsP(max_timelevels, (CCTK_COMPLEX*)NULL); + vector<CCTK_COMPLEX*> NewsBP(max_timelevels, (CCTK_COMPLEX*)NULL); // Get current timelevel... // We assume here that the two vars uBondi[0] amd uBondi[1] are right next to each }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/646> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #221: Simfactory should complain about unused arguments
by Einstein Toolkit 20 Mar '12

20 Mar '12

#221: Simfactory should complain about unused arguments ------------------------+--------------------------------------------------- Reporter: eschnett | Owner: mthomas Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- When more arguments are given to simfactory that it uses, it should complain with an error message. For example, "sim stop sim1 sim2" stops simulation sim1 and ignores the argument sim2. Instead, it should output an error message if the argument sim2 is ignored. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/221> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 8

[Einstein Toolkit] #623: use GRHydro_polytrope_handle whenever prim2conpolytrope is called
by Einstein Toolkit 13 Feb '12

13 Feb '12

#623: use GRHydro_polytrope_handle whenever prim2conpolytrope is called --------------------+------------------------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Other | Version: Keywords: | --------------------+------------------------------------------------------- Currently GRHydro uses grhydro_eos_handle in both Primitive2Conservative and Primitive2ConservativePoly and relies on grhydro_eos_handle being an actual handle to the 2d polytype in the later. This means that calling Primitive2ConservativePoly from within a run with grhydro_eos_type == "General" uses the wrong handle (namely the general eos). This is not normally a problem since Primitive2ConservativePoly is only ever called if grhydro_eos_type == "polytype", with the exception of EoSChangeGammaK which always calls Primitive2ConservativePoly (and has to call a polytype routine). There are basically two ways to make this work in this case: * use GRHydro_polytrope_handle in Primitive2ConservativePoly * call prim2conPoly from within EoSChangeGammaK The first option has the disadvantage that this is not what Conservative2Primitive does. The second has the disadvantage that EoSChangeGammaK has to also recompute Yecons (and any other new conservatives we might define) on top of calling prim2conPoly. Any comments? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/623> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

← Newer
1
...
9
10
11
12
13
14
15
16
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac January 2012