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