| 1 | CURRENT PMESH ISSUES |
|---|
| 2 | |
|---|
| 3 | OPEN - issues that have not beeen resolved |
|---|
| 4 | |
|---|
| 5 | Issue: On the cluster, if storm_surge/pmesh is in the pythonpath (and |
|---|
| 6 | not storm_surge?), pmesh.mesh fails by trying to load pmesh |
|---|
| 7 | visualisation stuff. Pmesh shouldn't be trying to load anyhow. |
|---|
| 8 | |
|---|
| 9 | Issue: crash if file>filter alpha boundary if there is no alpha |
|---|
| 10 | boundary. |
|---|
| 11 | |
|---|
| 12 | Issue: Add export seg outline file back into pmesh |
|---|
| 13 | |
|---|
| 14 | Issue: triangles_to_polySet (outlining the current set) sometimes |
|---|
| 15 | duplicates vertices. Now that is fixed, but segments that overlap (ie |
|---|
| 16 | one big line that gets little ones drawn on it) break triangle. |
|---|
| 17 | |
|---|
| 18 | Suggested action: make a dictionary of Hough transforms (parametric |
|---|
| 19 | lines i.e. angle, x-intercept) of the segments. Check any that take up |
|---|
| 20 | the same space. Fix overlapping lines. |
|---|
| 21 | |
|---|
| 22 | Issue: Red mesh selected for refinement seems to be 'behind' the green |
|---|
| 23 | mesh after selecting all then clearing the selection. |
|---|
| 24 | Importance: low |
|---|
| 25 | Suggested Action: Fixed BUT now it draws the greens behind the reds. |
|---|
| 26 | It is much less obvious now though. |
|---|
| 27 | The only way to fix it for good is to colour in the triangles - that |
|---|
| 28 | is the only way to guarantee you know what each triangle is. |
|---|
| 29 | |
|---|
| 30 | |
|---|
| 31 | Issue: Ole thought that the regional mesh max areas were incorrect |
|---|
| 32 | when a .tsh file was loaded. Maybe it was that the overall max area |
|---|
| 33 | is not saved. It's hard coded in MeshGenDialog. |
|---|
| 34 | Importance: Medium |
|---|
| 35 | Suggested Action: Fix when .tsh goes NETCDF |
|---|
| 36 | |
|---|
| 37 | Issue: Catch error if .tsh file is a bad format. |
|---|
| 38 | suggestion: quick and dirty try - except |
|---|
| 39 | Importance: Medium |
|---|
| 40 | |
|---|
| 41 | Issue (new feature): Have visualisation of verts be turned on and |
|---|
| 42 | off. This will speed things up. |
|---|
| 43 | Importance: low |
|---|
| 44 | |
|---|
| 45 | Issue (new feature): Hve .tsh as a netscf fie, instead of an ascii |
|---|
| 46 | file. |
|---|
| 47 | Importance: Medium |
|---|
| 48 | |
|---|
| 49 | Issue: When a file is saved as and then saved later, sometimes the |
|---|
| 50 | file name is not known. Is it that 'clear' is removing the name |
|---|
| 51 | (which it should). |
|---|
| 52 | |
|---|
| 53 | Issue:A .tsh file loaded into pmesh after smoothing will not have the |
|---|
| 54 | outline info, since this is removed when smoothing. If this is a |
|---|
| 55 | problem, refactor loadASCII so it can write the outline as well. |
|---|
| 56 | Suggested Action: Document use |
|---|
| 57 | |
|---|
| 58 | Issue:vertices at the bottom of the canvas can be hard to visualise, |
|---|
| 59 | since you don't know if all vertices are on the screen. |
|---|
| 60 | Suggested Action: have a 5% border |
|---|
| 61 | Importance: low to not do |
|---|
| 62 | |
|---|
| 63 | Issue: The mesh produced by triangle isn't of high quality near a low |
|---|
| 64 | angle formed by two user segments. |
|---|
| 65 | Reason:triangle |
|---|
| 66 | Tried: Tried the triangle flags L,i,V (for info). Using box.poly on |
|---|
| 67 | nautilus. Couldn't get a better quality mesh. |
|---|
| 68 | |
|---|
| 69 | Issue: Get the naming right for mesh/triangulation/user/generated. |
|---|
| 70 | How about "outline + triangulation = mesh" |
|---|
| 71 | Importance: Medium -low |
|---|
| 72 | |
|---|
| 73 | Issue: S/W - too many methods with the same name on differnent classes |
|---|
| 74 | eg editWindow. Makes things confusing. |
|---|
| 75 | Importance: low |
|---|
| 76 | |
|---|
| 77 | Issue: Normalise seems broken - what is it doing to the attributes?. |
|---|
| 78 | Suggested Action: remove! |
|---|
| 79 | |
|---|
| 80 | Bug: Calling 'Generate Mesh' on empty document or If there are no |
|---|
| 81 | enclosed regions will cause trianglulation to crash pmesh. |
|---|
| 82 | Importance: low - not do, but document |
|---|
| 83 | Suggested Action: Catch them (with try) and do nothing |
|---|
| 84 | notes: Fixing the 'Generate Mesh' crash is a P3 requirement. |
|---|
| 85 | |
|---|
| 86 | The zoom in/out is jittery |
|---|
| 87 | |
|---|
| 88 | The initial mesh window coordinates are in the fourth quadrant. |
|---|
| 89 | |
|---|
| 90 | Deleting a selected object is done with the scroll bar, not the |
|---|
| 91 | delete key. |
|---|
| 92 | |
|---|
| 93 | Issue: triangle calculates incorrect attribute values, some of the time. |
|---|
| 94 | Importance: Medium |
|---|
| 95 | Suggested Action: Preprocess data to smoth it out. |
|---|
| 96 | |
|---|
| 97 | Issue: pmesh can not be automatically installed in windows and linux, |
|---|
| 98 | triangle doesn't compile easily. |
|---|
| 99 | Installs best in Linux. |
|---|
| 100 | Importance: Low |
|---|
| 101 | Suggested Action: delve into setup more so it works with a variety of |
|---|
| 102 | compilers. |
|---|
| 103 | |
|---|
| 104 | Issue: two vertices can be ontop of one another |
|---|
| 105 | Importance: Low |
|---|
| 106 | Suggested Action: See how it goes when used. The cost of checking |
|---|
| 107 | probably doesn't outwiegh the benifit. |
|---|
| 108 | action taken: When loading an xya file duplicate vertices are removed. |
|---|
| 109 | |
|---|
| 110 | |
|---|
| 111 | Issue: When calculating mesh, have the pointer turn into an hour glass |
|---|
| 112 | Importance: Low |
|---|
| 113 | |
|---|
| 114 | **************** |
|---|
| 115 | CLOSED - issues that have beeen resolved |
|---|
| 116 | ************ |
|---|
| 117 | Issue: If some triangles have tags and others don't then the data |
|---|
| 118 | structure (a list of lists) is dificult to use in Numeric. |
|---|
| 119 | Solution - use a list structure, instead of list of lists |
|---|
| 120 | Closed - used a list structure, instead of list of lists |
|---|
| 121 | |
|---|
| 122 | Issue (Ole): I couldn't get pmesh to write mesh in the .msh format |
|---|
| 123 | Importance: Mid |
|---|
| 124 | Suggested action: Either |
|---|
| 125 | 1: Equip scripted mesh generation with functionality for tagging |
|---|
| 126 | 2: Allow pmesh to store as msh |
|---|
| 127 | 3: Have a tsh2msh converter |
|---|
| 128 | Closed: Couldn't be reproduced. suggested action 2 has already been |
|---|
| 129 | implemented. More investigation required before calling an issue an issue.. |
|---|
| 130 | |
|---|
| 131 | Issue: After selecting all for refinement then clearing the selection |
|---|
| 132 | segments (blue lines) can not be selected. |
|---|
| 133 | Importance: High |
|---|
| 134 | Suggested Action:Fixed |
|---|
| 135 | Reason: |
|---|
| 136 | |
|---|
| 137 | Issue: Refined triangles don't have the correct region information. |
|---|
| 138 | Importance: High |
|---|
| 139 | Suggested Action: Fixed |
|---|
| 140 | Reason: I don't think 'refine' fixes triangle attributes |
|---|
| 141 | |
|---|
| 142 | |
|---|
| 143 | Issue: Pmesh won't save a refined mesh. |
|---|
| 144 | Importance: High |
|---|
| 145 | Reason: Refine_triangle.getNewVertex was not appending to mesh.meshVertices, |
|---|
| 146 | nor was it assigning an index to the vertex. |
|---|
| 147 | |
|---|
| 148 | Issue When starting generate mesh, the cursor doesn't start in the |
|---|
| 149 | first box. |
|---|
| 150 | Importance: Low |
|---|
| 151 | Action: fixed |
|---|
| 152 | |
|---|
| 153 | Issue: Why is triangle att's set as a list and returned as a list of |
|---|
| 154 | lists, when loading from a .tsh file? Note: a change of this might |
|---|
| 155 | also affect the 'triangle' glue code. |
|---|
| 156 | Note: This also happens to triangle atts! (?) |
|---|
| 157 | action: triangle att's set as a list of lists |
|---|
| 158 | |
|---|
| 159 | Issue:Implememt the following with mesh gen minimum angle, 0 - 32 |
|---|
| 160 | nothing;32-40 warning message, may not converge; 40 - error message |
|---|
| 161 | Importance: Low |
|---|
| 162 | Action: done |
|---|
| 163 | |
|---|
| 164 | Issue: Middle magnifying glass icon does not describe what it will do. |
|---|
| 165 | Importance: Low Low |
|---|
| 166 | action: too unimportant to do |
|---|
| 167 | |
|---|
| 168 | Issue: Maybe triangle doesn't normalise meshes away from the origin, |
|---|
| 169 | resulting in round-off error. |
|---|
| 170 | Importance: Low Low |
|---|
| 171 | Suggested Action: closed since this didn;t seem to be a problem. |
|---|
| 172 | |
|---|
| 173 | Issue:hull.exe generates files that it doesn't clean up eg called |
|---|
| 174 | s1f8, se4, etc. These seem to turn up in a root directory |
|---|
| 175 | Importance: Low |
|---|
| 176 | |
|---|
| 177 | Issue: Hull.exe (alpha shape) - gives an assertion error if points are |
|---|
| 178 | too close together?. |
|---|
| 179 | Importance: Low |
|---|
| 180 | Suggested Action: when using the results from hull.exe, check if it |
|---|
| 181 | has given any results and throw a friendly message if there are no results. |
|---|
| 182 | |
|---|
| 183 | Issue: When adding segments, vertices are hard to select (with the mouse). |
|---|
| 184 | |
|---|
| 185 | Issue: Calling autoSegment when not in the pmesh directory will not |
|---|
| 186 | work, since it calls the hull.exe, assuming it's in the current dir |
|---|
| 187 | Importance: medium |
|---|
| 188 | Suggested Action: Have the current dir change to the pmesh dir , run |
|---|
| 189 | hull, then change back |
|---|
| 190 | action: contractor is making alpha shape in python |
|---|
| 191 | |
|---|
| 192 | Issue: In the shallow_water functions for pmesh, make the |
|---|
| 193 | volume.interpolate_cons_quantitie call more automatic |
|---|
| 194 | |
|---|
| 195 | Issue: Need tests for pmesh functions in shallow_water.py |
|---|
| 196 | |
|---|
| 197 | Issue: If there is a large scale grid, how many triangles can be |
|---|
| 198 | generated? with a normalised grid there's a limit of 22674. |
|---|
| 199 | Using a 100 * 100 domain, a max triangle area of 0.01 produced |
|---|
| 200 | 1,048,576 triangles. |
|---|
| 201 | |
|---|
| 202 | Issue: Internal boudaries get an empty string as tag (per default?) |
|---|
| 203 | Background: The notion of defaiults values for internal boundaries was removed, but this one seems to have taken its place. The following hack will |
|---|
| 204 | remove the tag: |
|---|
| 205 | #for b in domain.boundary.keys(): |
|---|
| 206 | # if domain.boundary[b] == '': |
|---|
| 207 | # del domain.boundary[b] |
|---|
| 208 | # |
|---|
| 209 | #domain = Domain(domain.coordinates, domain.triangles, domain.boundary) |
|---|
| 210 | Importance: high |
|---|
| 211 | |
|---|
| 212 | |
|---|
| 213 | Issue: The default region button cannot be selected after loading a file. |
|---|
| 214 | Reason: Unknown. |
|---|
| 215 | Importance: Low |
|---|
| 216 | |
|---|
| 217 | Issue: The vertices were being sorted when loading .xya files |
|---|
| 218 | Time to complete : 5hrs |
|---|
| 219 | Issue: In load ascii all text reading of lines using find must ltrim |
|---|
| 220 | beforehand |
|---|
| 221 | |
|---|
| 222 | Issue: pmesh -when loading/saving the dir should be the dir where the |
|---|
| 223 | file lives. Not always the current dir. |
|---|
| 224 | |
|---|
| 225 | Issue: Tags for specifying boundary conditions should be arbitrary |
|---|
| 226 | Background: Domain has the functionality for using arbitrary keys |
|---|
| 227 | when associating boundary objects to boundary values. |
|---|
| 228 | Triangle, which pmesh is based on, uses integers only. |
|---|
| 229 | It would be nice to have mnemonic names for boundaries throughout. |
|---|
| 230 | Importance: Mid |
|---|
| 231 | Status: Unresolved |
|---|
| 232 | |
|---|
| 233 | Issue: Calling save the first time seemingly does nothing |
|---|
| 234 | Importance: Low |
|---|
| 235 | Suggested Action: Call save_as when save is clicked the first time. |
|---|
| 236 | |
|---|
| 237 | |
|---|
| 238 | Bug: Calling Zoom functions on empty document |
|---|
| 239 | causes an AttributeError Exceptions. |
|---|
| 240 | Importance: Medium |
|---|
| 241 | Suggested Action: Catch them (with try) and do nothing |
|---|
| 242 | notes: the zoom crash is not reproducable. Fixing the 'Generate Mesh' crash |
|---|
| 243 | is a P3 requirement. |
|---|
| 244 | |
|---|
| 245 | When doing mesh generation, no default values (min angle, max area) |
|---|
| 246 | are shown. - Low priority for Chris |
|---|
| 247 | |
|---|
| 248 | |
|---|
| 249 | Cursor shape changes when it shouldn't. |
|---|
| 250 | |
|---|
| 251 | Issue: Help message and status message are the same. Remove one |
|---|
| 252 | Importance: Low |
|---|
| 253 | Suggested Action: Remove the status info |
|---|
| 254 | |
|---|
| 255 | |
|---|
| 256 | Issue: Selecting nodes require that boundary is selected precisely. |
|---|
| 257 | Importance: High |
|---|
| 258 | Suggested Action: Allow click in interior of square. |
|---|
| 259 | |
|---|
| 260 | Bug: Entering negative value for area is allowed. |
|---|
| 261 | Importance: Medium |
|---|
| 262 | Suggested Action: Check input and return error message |
|---|
| 263 | |
|---|
| 264 | |
|---|
| 265 | Issue: Minimum angle needs a specification of what interval is allowed. |
|---|
| 266 | It seems to pick a default value if angle is out of bounds. |
|---|
| 267 | Action: angles <0.0, >90.0 not allowed |
|---|
| 268 | |
|---|
| 269 | Bug: Entering zero for area causes crash. |
|---|
| 270 | Importance: Medium |
|---|
| 271 | Suggested Action: Check input and return normal error message |
|---|
| 272 | |
|---|
| 273 | |
|---|
| 274 | Issue: Re-generating grids goes slower and slower when repeated. |
|---|
| 275 | Importance: Low |
|---|
| 276 | Suggested Action: Check that old grid gets removed from memory. |
|---|
| 277 | Action taken: cleaned up how visualised objects are handled |
|---|
| 278 | |
|---|
| 279 | |
|---|
| 280 | Issue: nothing says what mode(seg or vertex) pmesh is in |
|---|
| 281 | Importance: Low |
|---|
| 282 | Action taken: Have the buttons stay 'down', to depict mode. |
|---|
| 283 | |
|---|
| 284 | |
|---|
| 285 | |
|---|
| 286 | Issue: Meaning of 1 x zoom is not intuitive. |
|---|
| 287 | Related issue: Absolute scale should be reported in status bar |
|---|
| 288 | Importance: Medium |
|---|
| 289 | Action taken : Zoom x 1 gives a zoom corresponding |
|---|
| 290 | to the opening screen. |
|---|
| 291 | |
|---|
| 292 | Vertices and segments that have a triangle on top of them are hard to |
|---|
| 293 | select/see. Ole suggested that there be the capability to view/hide the mesh. |
|---|
| 294 | Action taken :put segs/vertices on top |
|---|
| 295 | |
|---|
| 296 | |
|---|
| 297 | NOTES |
|---|
| 298 | The arrow and postscript bottons currently do nothing. |
|---|
| 299 | |
|---|
| 300 | |
|---|
| 301 | ----------------------------------------------- |
|---|
| 302 | NEW REQUIREMENTS |
|---|
| 303 | |
|---|
| 304 | Introduce 'eraser tool'. When selected left clicking any object will remove it. |
|---|
| 305 | |
|---|
| 306 | Allow generated grid to be cleared (or hidden). |
|---|
| 307 | |
|---|
| 308 | |
|---|
| 309 | |
|---|
| 310 | CVS INFORMATION FOR THIS FILE |
|---|
| 311 | $Source: /var/lib/cvs/pmesh/documentation/issues.txt,v $ |
|---|
