Activity

From 01 May 2016 to 30 May 2016

30 May 2016

22:18 Refactoring #1440 (Archived): cover Python examples by functional tests
Test should check that all examples execute without failure, and that they produce about the same detector image as b... wuttke
16:21 Bug #1439 (Resolved): put PythonAPI under CMake control
Currently, when API has changed, one needs to rm Core/PythonAPI/lib*. We should put the generation of these wrappers ... wuttke
16:18 Refactoring #1432: final polish of polyhedral form factor
rel err now <1e-11 wuttke
16:15 Bug #1423: == eliminate warnings ==
warnings come from cmake-called processes, but not from CMake wuttke
16:08 Envelope task #1438 (In Progress): === Physics ===
Physical modelling tasks, unless covered by more specific top-level enevelop tasks wuttke
15:15 Documentation #1412: avoid horizontal scrolling in code examples
no clue how to change the font size -> http://drupal.stackexchange.com/questions/202612/ wuttke
13:41 Refactoring #1071 (Resolved): Example scripts: No global import from Python module bornagain
Resolved in 3b5d014b0, using the regular expressions appended below, plus very little hand editing.
All scripts in...
wuttke
13:34 Refactoring #1071 (Sprint): Example scripts: No global import from Python module bornagain
wuttke
13:33 Documentation #1437 (Rejected): Release requirement: Update example scripts
During a sprint, examples are updated in Examples/python/...
Upon release, they need to be moved to the Drupal sit...
wuttke
13:19 Bug #1436 (Archived): repair ex06_Miscellaneous/AccessingSimulationResults.py: type object 'IHist...
broken after past refactoring
$ p2 AccessingSimulationResults.py
Traceback (most recent call last):
File "Acc...
wuttke
11:13 Documentation #1360: reequilibrate hierarchy levels in online docs
no objections raised, so we go for it wuttke
11:01 Bug #900: Custom form factors in python do not work with multithreading
Suggestion: Declare this a feature, update the documentation of CustomFormFactor, and close this issue. Serious work ... wuttke
10:18 Bug #1070: Unix should install to /usr/local/lib, not to versioned subdirectory
probably strong interdependence with #1256 wuttke
10:16 Bug #1070 (Rfc): Unix should install to /usr/local/lib, not to versioned subdirectory
wuttke
10:12 Documentation #1104 (Rfc): don't use version-dependent URLs in the online docs
wuttke

25 May 2016

16:31 Refactoring #1296 (Resolved): update internal information about performance tests
Information in README files updated.
Wiki main page provides links to README files.
wuttke
15:38 Feature #1290: === Core: framework ===
To keep the code base readable and maintainable wuttke

17 May 2016

14:13 Refactoring #1428 (Backlog): Compactify code that handles parameters (use abstract mechanism inst...
agreed in meeting today wuttke
14:13 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
By convention, all lengths are in nm, all angles are internally in rad. Therefore, we only need the physical dimensio... wuttke
14:10 Refactoring #1430 (Resolved): Consider moving FormFactor unit tests to a single functional test
The main concern will be resolved per issue #1433.
Renaming of subdirectories will follow later, when Core/ is res...
wuttke
13:59 Refactoring #1433 (Resolved): move massive numeric tests under 'make check' / 'ctest'
to be done when the polyhedral FF is stable (#1432) wuttke
13:56 Refactoring #1432 (Rejected): final polish of polyhedral form factor
* specific tests for frusta that are true pyramids
* exact treatment of vertices that coincide
* -improve edge sum ...
wuttke
11:42 Documentation #1431 (Resolved): simplify cross-referencing using package cleveref
wuttke

13 May 2016

17:10 Feature #1238: nicer layout for newsletter@bornagainproject.org (reopened: v1.6.0 round mail stil...
I really do not like the black topbar.
Plain ASCII would be nicer than this HTML.
wuttke
13:53 Refactoring #1424: reduce verbosity of googletest output
Feature request submitted at https://github.com/google/googletest/issues/771. wuttke

12 May 2016

13:21 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
So I withdraw default units from the current proposal. Are units acceptable for you? wuttke
13:12 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
Maybe this issue should also be split: default values vs units herck
13:11 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
> > It's not their responsibility.
>
> We are free to assign responsibilities to our creatures as we deem appropri...
herck
13:01 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
So yes, you want users to get default parametrized items. OK, I accept.
> Core form factors should not have any de...
wuttke
12:38 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
In GUI default values should be provided to reduce amount of clicks/typing. This allows to start a simulation with a ... pospelov
11:59 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
The very first question then: Is it actually appropriate for the GUI to assign default parameters to newly created it... wuttke
11:43 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
The {FF}Items need default values because the GUI needs to create them without user initialization. There is no need ... herck
11:39 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
interesting consequence. why not? wuttke
10:57 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...

> Each parameter should have a default value
What does it mean? "new FormFactorSphere()" becomes valid and becom...
pospelov
13:16 Refactoring #1430: Consider moving FormFactor unit tests to a single functional test
The number 200k comes from arbitrary choices and can be changed if time is a concern.
The tests are concerned with...
wuttke
13:00 Refactoring #1430: Consider moving FormFactor unit tests to a single functional test
I also agree that these tests conceptually do not belong to unit tests. It also obscures unit test coverage (having 2... herck
12:54 Refactoring #1430: Consider moving FormFactor unit tests to a single functional test
My previous reply disappeared since you commented same record I was commenting.
> Why do we actually have a functi...
pospelov
12:42 Refactoring #1430: Consider moving FormFactor unit tests to a single functional test
> [ RUN] OK is better than just [——]
Agree. Implemented in 91d8e8f5b0.
wuttke
12:36 Refactoring #1430: Consider moving FormFactor unit tests to a single functional test
Nothing in googletest says it is limited to unit tests, let alone to unit tests in the most narrow sense. Why do we a... wuttke
12:31 Refactoring #1430: Consider moving FormFactor unit tests to a single functional test
I put two issues in one, that's true. The major issue is to move Unit to Functional. pospelov
12:09 Refactoring #1430: Consider moving FormFactor unit tests to a single functional test
These are two different issues:
* Move extensive ff tests from Unit to Functional?
* Don't split Core/Unit tests in...
wuttke
10:43 Refactoring #1430 (Resolved): Consider moving FormFactor unit tests to a single functional test
I think that tests of form factor behaviour near singularity and along symmetry axes belongs to the functional tests,... pospelov

11 May 2016

18:28 Bug #1371: presence of some boost components not checked by cmake
Btw: testing under Debian is somewhat difficult because of the non-standard packaging of Boost. Reported at https://b... wuttke
17:39 Bug #1371 (Resolved): presence of some boost components not checked by cmake
Resolved in ac0d39e, using a patched FindBoost.cmake that is to be submitted to CMake: https://github.com/rleigh-dund... wuttke
18:10 Refactoring #1366: Revise boost libraries usage
Migration of regex from Boost to regex is suspended because compilers are not ready. => commit d14b964d17bb wuttke
17:34 Refactoring #1366: Revise boost libraries usage
Only now enacted the deletion of boost components regex and thread in cmake/modules/SearchInstalledSoftware.cmake. wuttke
14:36 Refactoring #1424 (Resolved): reduce verbosity of googletest output
wuttke
14:36 Refactoring #1424: reduce verbosity of googletest output
Solved in rather unexpected way in 24204e5, namely by brutally patching gtest. Inheriting outside gtest.cc from the d... wuttke
13:07 Bug #1429 (Resolved): Unit tests files are not shown in Qt Creator IDE
Solved in 03d6c5d, using 'add_custom_target' as suggested in http://stackoverflow.com/questions/28384935/qtcreator-cm... wuttke
08:48 Bug #1429 (Archived): Unit tests files are not shown in Qt Creator IDE
Files from UnitTests/TestCore directory (and similar) are not shown in "Project Structure" by Qt creator IDE. It is n... pospelov
12:39 Refactoring #1428: Compactify code that handles parameters (use abstract mechanism instead of tre...
To automatically generate Python constructors,
* either use named arguments
* or make sure that parameters are orde...
wuttke

10 May 2016

14:08 Refactoring #1428 (Archived): Compactify code that handles parameters (use abstract mechanism ins...
Each parameter should have -a default value and- a -unit- physical dimension, assigned upon registration.
This wil...
wuttke
12:47 Documentation #1279 (Archived): Inkscape tasks
wuttke
12:46 Documentation #1280 (Resolved): draw tetrahedron as seen from -x
Completed in 4003c83. wuttke

04 May 2016

19:16 Refactoring #1424 (Sprint): reduce verbosity of googletest output
with increasing number of tests, this is becoming urgent wuttke
14:19 Feature #1427: Implement new roughness calculation that is more stable for large roughness
Resolved in #d212f6feba85d4a7f41db0b15ae90a697e1acd01 herck
14:19 Feature #1427 (Resolved): Implement new roughness calculation that is more stable for large rough...
herck
14:18 Feature #1427 (Archived): Implement new roughness calculation that is more stable for large rough...
herck
 

Also available in: Atom