Menu

SVN archive Commit Log


Commit Date  
[r18643] by bugman

For the frame order displacement test suite data, an optimisation script has been added.

This is to verify this data through the auto-analysis, but it is not part of the test suite as these
tests are insanely slow (~8 hours on one machine).

2013-03-05 14:51:35 Tree
[r18642] by bugman

Large decrease in the time required for the pseudo-ellipse CaM frame order system test.

The number of integration points has been massively decreased from 1000 to 15 (all other tests are
50 points). This halves the time down to about half a minute on one machine.

2013-03-05 14:49:25 Tree
[r18641] by bugman

Decreased the total time required for the frame order system tests.

Instead of using all the PCS data, the PCS data subsets are now used. This decreases the total time
on one machine from 656.300 to 461.354 (total CPU seconds from profiling).

2013-03-05 14:40:48 Tree
[r18640] by bugman

Fixes for the chi2 values in the CaM frame order system tests.

As forwards rotations are now used for the average domain position, the low precision of the
quasi-random integration means that the chi2 value is slightly different.

2013-03-05 13:56:50 Tree
[r18639] by bugman

Converted all of the CaM frame order system test scripts for the new average position notation.

The reverse angles have been converted to forwards angles.

2013-03-05 13:40:04 Tree
[r18638] by bugman

Fix for the rigid frame order system test script for the frame_order.average_position user function.

The old frame_order.ave_pos_translation user function was being used.

2013-03-05 13:28:58 Tree
[r18637] by bugman

Removed all references to 'Monte Carlo integration' from the frame order target functions.

This was replaced by the quasi-random numerical integration a long time ago.

2013-03-05 13:04:05 Tree
[r18636] by bugman

Removed the remaining residual, slow frame order multi-processor code from the target functions.

2013-03-05 13:02:02 Tree
[r18635] by bugman

The CaM frame order system tests now use the obligatory frame_order.average_position user function.

2013-03-05 12:26:49 Tree
[r18634] by bugman

The grid search for the frame order auto-analysis with translation is now handled differently.

This is to avoid getting trapped into a local minimum. The grid for this split into a grid search
over the rotational space first, then a grid search over the translation. This is repeated for good
measure. This is much more accurate and reliable for finding the global minimum and is also much
faster.

2013-03-05 10:52:41 Tree
Older >
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.