-
Notifications
You must be signed in to change notification settings - Fork 7
/
Copy pathDEVELOPMENT-NOTES
46 lines (27 loc) · 1.27 KB
/
DEVELOPMENT-NOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
* 2023-0107-2301-50-EST
Updated ERFA to 2.0.0. Had to define several version macro symbols by hand. Also
added header files to get DBL_EPSILON definition.
* 2019-1217-1615-10-EST
DartConfiguration.tcl in cmake-build directory has options concerning the build.
In particular for valgrind there is a
ValgrindCommandOptions: --track-origins=yes
but maybe I should use instead...
MemoryCheckCommandOptions: --track-origins=yes
Note: https://stackoverflow.com/questions/52730994/how-to-pass-arguments-to-memcheck-with-ctest
* 2019-0811-1815-DST
Which classes use or depend on SpatialIndex? We need to be concerned about default SpatialIndexes showing up.
RangeConvex.h:
const SpatialIndex * index_; // A pointer to the index
An index is passed into RangeConvex, which then uses it for intersections etc.
SpatialDomain.h:
const SpatialIndex *index; /// A pointer to the index
SpatialEdge.h:
SpatialIndex & tree_;
SpatialInterface.h:
SpatialIndex *index_;
STARE.h:
SpatialIndex sIndex;
* 2019-0810-2331-DST
Can we remove intervals from a range?
* 2019-0809-22231-DST
** Be very careful when calling HTM library from STARE, particularly when the HTM code makes SpatialIndexes. The legacy SpatialIndex default constructor is different from the SpatialIndex created by STARE.