source: inundation/ga/storm_surge/pmesh/documentation/issues.txt @ 420

Last change on this file since 420 was 420, checked in by duncan, 20 years ago

update

File size: 7.1 KB
Line 
1CURRENT PMESH ISSUES
2
3$Revision: 1.29 $
4$Date: 2004/09/27 12:35:23 $
5
6OPEN - issues that have not beeen resolved
7
8Issue:A .tsh file loaded into pmesh after smoothing will not have the
9outline info, since this is removed when smoothing.  If this is a
10problem, refactor loadASCII so it can write the outline as well.
11
12Issue: Why is triangle att's set as a list and returned as a list of
13lists, when loading from a .tsh file?  Note: a change of this might
14also affect the 'triangle' glue code.
15Note: This also happens to triangle atts!
16
17Issue:vertices at the bottom of the canvas can be hard to visualise,
18since you don't know if all vertices are on the screen. 
19
20
21Issue: If there is a large scale grid, how many triangles can be
22generated?  with a normalised grid there's a limit of 22674.
23Using a 100 * 100 domain, a max triangle area of 0.01 produced
241,048,576 triangles.
25
26Issue: The mesh produced by triangle isn't of high quality near a low
27angle formed by two user segments.
28Reason:triangle
29Tried:  Tried the triangle flags L,i,V (for info).  Using box.poly on
30nautilus.  Couldn't get a better quality mesh.
31
32Issue: Get the naming right for mesh/triangulation/user/generated.
33How about "outline + triangulation = mesh"
34
35Issue: S/W - too many methods with the same name on differnent classes
36eg editWindow.  Makes things confusing.
37
38Issue: Normalise seems broken - what is it doing to the attributes?
39
40Issue: In the shallow_water functions for pmesh, make the
41volume.interpolate_cons_quantitie call more automatic
42
43Issue: Need tests for pmesh functions in  shallow_water.py
44
45Issue: Calling autoSegment when not in the pmesh directory will not
46work, since it calls the hull.exe, assuming it's in the current dir
47Importance: medium
48Suggested Action: Have the current dir change to the pmesh dir , run
49hull, then change back
50
51Bug: Calling 'Generate Mesh' on empty document or If there are no
52enclosed regions will cause trianglulation to crash pmesh.
53Importance: Medium
54Suggested Action: Catch them (with try) and do nothing
55notes:   Fixing the 'Generate Mesh' crash is a P3 requirement.
56
57The zoom in/out is jittery
58
59The initial mesh window coordinates are in the fourth quadrant.
60
61When adding segments, vertices are hard to select (with the mouse).
62
63Deleting a selected object is done with the scroll bar, not the
64delete key.
65
66Issue: triangle calculates incorrect attribute values, some of the time.
67Importance: Medium
68Suggested Action: Preprocess data to smoth it out.
69
70Issue: Hill.exe (alpha shape) - gives an assertion error if points are
71too close together?. 
72Importance: Low
73Suggested Action: when using the results from hull.exe, check if it
74has given any results and throw a friendly message if there are no results.
75
76Issue: pmesh can not be automatically installed in windows and linux.
77Installs best in Linux. 
78Importance: Low
79Suggested Action: delve into setup more so it works with a variety of
80compilers.
81
82Issue: two vertices can be ontop of one another
83Importance: Low
84Suggested Action: See how it goes when used.  The cost of checking
85probably doesn't outwiegh the benifit.
86action taken: When loading an xya file duplicate vertices are removed.
87
88
89Issue: When calculating mesh, have the pointer turn into an hour glass
90Importance: Low
91
92Issue:  Maybe triangle doesn't normalise meshes away from the origin,
93resulting in round-off error.
94Importance: Low Low
95Suggested Action: Normalise in pmesh, before passing to triangle.
96
97Issue:hull.exe generates files that it doesn't clean up eg called
98s1f8, se4, etc. These seem to turn up in a root directory
99Importance: Low
100
101
102Issue: Middle magnifying glass icon does not describe what it will do.
103Importance: Low Low
104
105Issue When starting generate mesh, the cursor doesn't start in the
106first box.
107Importance: Low
108
109Issue:Implememt the following with mesh gen minimum angle, 0 - 32
110nothing;32-40 warning message, may not converge; 40 - error message
111Importance: Low
112
113****************
114CLOSED - issues that have  beeen resolved
115************
116
117Issue: The default region button cannot be selected after loading a file.
118Reason: Unknown. 
119Importance: Low
120
121Issue: The vertices were being sorted when loading .xya files
122Time to complete : 5hrs
123Issue: In load ascii all text reading of lines using find must ltrim
124beforehand
125
126Issue: pmesh -when loading/saving the dir should be the dir where the
127file lives.  Not always the current dir.
128
129Issue: Tags for specifying boundary conditions should be arbitrary
130Background: Domain has the functionality for using arbitrary keys
131when associating boundary objects to boundary values.
132Triangle, which pmesh is based on, uses integers only.
133It would be nice to have mnemonic names for boundaries throughout.
134Importance: Mid
135Status: Unresolved
136
137Issue: Calling save the first time seemingly does nothing
138Importance: Low
139Suggested Action: Call save_as when save is clicked the first time.
140
141
142Bug: Calling Zoom functions on empty document
143causes an AttributeError Exceptions.
144Importance: Medium
145Suggested Action: Catch them (with try) and do nothing
146notes: the zoom crash is not reproducable.  Fixing the 'Generate Mesh' crash
147is a P3 requirement.
148
149When doing mesh generation, no default values (min angle, max area)
150are shown. - Low priority for Chris
151
152
153Cursor shape changes when it shouldn't.
154
155Issue: Help message and status message are the same.  Remove one
156Importance: Low
157Suggested Action: Remove the status info
158
159
160Issue: Selecting nodes require that boundary is selected precisely.
161Importance: High
162Suggested Action: Allow click in interior of square.
163
164Bug: Entering negative value for area is allowed.
165Importance: Medium
166Suggested Action: Check input and return error message
167
168
169Issue: Minimum angle needs a specification of what interval is allowed.
170It seems to pick a default value if angle is out of bounds.
171Action: angles <0.0, >90.0 not allowed
172
173Bug: Entering zero for area causes crash.
174Importance: Medium
175Suggested Action: Check input and return normal error message
176
177
178Issue: Re-generating grids goes slower and slower when repeated.
179Importance: Low
180Suggested Action: Check that old grid gets removed from memory.
181Action taken: cleaned up how visualised objects are handled
182
183
184Issue: nothing says what mode(seg or vertex) pmesh is in
185Importance: Low
186Action taken: Have the buttons stay 'down', to depict mode.
187
188 
189
190Issue: Meaning of 1 x zoom is not intuitive.
191Related issue: Absolute scale should be reported in status bar
192Importance: Medium
193 Action taken : Zoom x 1  gives a zoom corresponding
194to the opening screen.
195
196Vertices and segments that have a triangle on top of them are hard to
197select/see.  Ole suggested that there be the capability to view/hide the mesh.
198 Action taken :put segs/vertices on top
199
200
201NOTES
202The arrow and postscript bottons currently do nothing.
203
204
205-----------------------------------------------
206NEW REQUIREMENTS
207
208Introduce 'eraser tool'. When selected left clicking any object will remove it.
209
210Allow generated grid to be cleared (or hidden).
211
212
213
214CVS INFORMATION FOR THIS FILE
215$Source: /var/lib/cvs/pmesh/documentation/issues.txt,v $
Note: See TracBrowser for help on using the repository browser.