Changeset 1153
- Timestamp:
- Mar 29, 2005, 12:12:10 PM (20 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
inundation/ga/storm_surge/pmesh/documentation/issues.txt
r1126 r1153 2 2 3 3 OPEN - issues that have not beeen resolved 4 Issue: If some triangles have tags and others don't then the data 5 structure (a list of lists) is dificult to use in Numeric. 6 eg. 7 SyntaxError: invalid syntax 8 >>> a = array(['a','b']); print a 9 [a b] 10 >>> a = array(['a','b','']); print a 11 Traceback (most recent call last): 12 File "<stdin>", line 1, in ? 13 TypeError: an integer is required 14 >>> a = array([['a'],['b'],['']]); print a 15 Traceback (most recent call last): 16 File "<stdin>", line 1, in ? 17 TypeError: an integer is required 18 >>> a = array([['a'],['b'],['']]).astype(ListType); print a 19 Traceback (most recent call last): 20 File "<stdin>", line 1, in ? 21 TypeError: an integer is required 22 >>> a = array([['a'],['b'],['c']]).astype(ListType); print a 23 Traceback (most recent call last): 24 File "<stdin>", line 1, in ? 25 TypeError: an integer is required 26 >>> a = array(['a','b','']); print a 27 Traceback (most recent call last): 28 File "<stdin>", line 1, in ? 29 TypeError: an integer is required 30 >>> a = array(['a','b','c']); print a 31 [a b c] 32 >>> a = array([['a'],['b'],['c']]); print a 33 Traceback (most recent call last): 34 File "<stdin>", line 1, in ? 35 TypeError: an integer is required 36 >>> a = array([['a'],['a'],['a']]); print a 37 Traceback (most recent call last): 38 File "<stdin>", line 1, in ? 39 TypeError: an integer is required 40 >>> a = array([['a'],['a'],['a']]); print a 41 Traceback (most recent call last): 42 File "<stdin>", line 1, in ? 43 TypeError: an integer is required 44 >>> a = array([['a'],['a'],['a']], Character); print a 45 [[ [a]] 46 [ [a]] 47 [ [a]]] 48 >>> a = array([['a'],['a'],['']], Character); print a 49 Traceback (most recent call last): 50 File "<stdin>", line 1, in ? 51 TypeError: an integer is required 52 >>> a = array([['a'],['a'],['','a']], Character); print a 53 Traceback (most recent call last): 54 File "<stdin>", line 1, in ? 55 TypeError: an integer is required 56 >>> a = array([['a','j'],['a','j'],['j','a']], Character); print a 57 Traceback (most recent call last): 58 File "<stdin>", line 1, in ? 59 TypeError: an integer is required 60 >>> a = array(['a','a',''], Character); print a 61 [[a] 62 [a] 63 [ ]] 64 Solution - use a list structure, instead of list of lists 65 66 67 Issue: Red mesh selected for refinement seems to be 'behind' the green 68 mesh after selecting all then clearing the selection. 69 Importance: low 70 Suggested Action: Fixed BUT now it draws the greens behind the reds. 71 It is much less obvious now though. 72 73 74 Issue: Ole thought that the regional mesh max areas were incorrect 75 when a .tsh file was loaded. Maybe it was that the overall max area 76 is not saved. It's hard coded in MeshGenDialog. 77 Importance: Medium 78 Suggested Action: Fix when .tsh goes NETCDF 79 80 Issue: Catch error if .tsh file is a bad format. 81 suggestion: quick and dirty try - except 82 Importance: Medium 83 84 Issue (new feature): Have visualisation of verts be turned on and 85 off. This will speed things up. 86 Importance: low 87 88 Issue (new feature): Hve .tsh as a netscf fie, instead of an ascii 89 file. 90 Importance: Medium 91 92 Issue: When a file is saved as and then saved later, sometimes the 93 file name is not known. Is it that 'clear' is removing the name 94 (which it should). 95 96 Issue:A .tsh file loaded into pmesh after smoothing will not have the 97 outline info, since this is removed when smoothing. If this is a 98 problem, refactor loadASCII so it can write the outline as well. 99 Suggested Action: Document use 100 101 Issue:vertices at the bottom of the canvas can be hard to visualise, 102 since you don't know if all vertices are on the screen. 103 Suggested Action: have a 5% border 104 Importance: low to not do 105 106 Issue: The mesh produced by triangle isn't of high quality near a low 107 angle formed by two user segments. 108 Reason:triangle 109 Tried: Tried the triangle flags L,i,V (for info). Using box.poly on 110 nautilus. Couldn't get a better quality mesh. 111 112 Issue: Get the naming right for mesh/triangulation/user/generated. 113 How about "outline + triangulation = mesh" 114 Importance: Medium -low 115 116 Issue: S/W - too many methods with the same name on differnent classes 117 eg editWindow. Makes things confusing. 118 Importance: low 119 120 Issue: Normalise seems broken - what is it doing to the attributes?. 121 Suggested Action: remove! 122 123 Bug: Calling 'Generate Mesh' on empty document or If there are no 124 enclosed regions will cause trianglulation to crash pmesh. 125 Importance: low - not do, but document 126 Suggested Action: Catch them (with try) and do nothing 127 notes: Fixing the 'Generate Mesh' crash is a P3 requirement. 128 129 The zoom in/out is jittery 130 131 The initial mesh window coordinates are in the fourth quadrant. 132 133 Deleting a selected object is done with the scroll bar, not the 134 delete key. 135 136 Issue: triangle calculates incorrect attribute values, some of the time. 137 Importance: Medium 138 Suggested Action: Preprocess data to smoth it out. 139 140 Issue: pmesh can not be automatically installed in windows and linux, 141 triangle doesn't compile easily. 142 Installs best in Linux. 143 Importance: Low 144 Suggested Action: delve into setup more so it works with a variety of 145 compilers. 146 147 Issue: two vertices can be ontop of one another 148 Importance: Low 149 Suggested Action: See how it goes when used. The cost of checking 150 probably doesn't outwiegh the benifit. 151 action taken: When loading an xya file duplicate vertices are removed. 152 153 154 Issue: When calculating mesh, have the pointer turn into an hour glass 155 Importance: Low 156 157 **************** 158 CLOSED - issues that have beeen resolved 159 ************ 4 160 5 161 Issue (Ole): I couldn't get pmesh to write mesh in the .msh format … … 9 165 2: Allow pmesh to store as msh 10 166 3: Have a tsh2msh converter 11 12 13 Issue: Red mesh selected for refinement seems to be 'behind' the green 14 mesh after selecting all then clearing the selection. 15 Importance: low 16 Suggested Action: Fixed BUT now it draws the greens behind the reds. 17 It is much less obvious now though. 18 19 20 Issue: Ole thought that the regional mesh max areas were incorrect 21 when a .tsh file was loaded. Maybe it was that the overall max area 22 is not saved. It's hard coded in MeshGenDialog. 23 Importance: Medium 24 Suggested Action: Fix when .tsh goes NETCDF 25 26 Issue: Catch error if .tsh file is a bad format. 27 suggestion: quick and dirty try - except 28 Importance: Medium 29 30 Issue (new feature): Have visualisation of verts be turned on and 31 off. This will speed things up. 32 Importance: low 33 34 Issue (new feature): Hve .tsh as a netscf fie, instead of an ascii 35 file. 36 Importance: Medium 37 38 Issue: When a file is saved as and then saved later, sometimes the 39 file name is not known. Is it that 'clear' is removing the name 40 (which it should). 41 42 Issue:A .tsh file loaded into pmesh after smoothing will not have the 43 outline info, since this is removed when smoothing. If this is a 44 problem, refactor loadASCII so it can write the outline as well. 45 Suggested Action: Document use 46 47 Issue:vertices at the bottom of the canvas can be hard to visualise, 48 since you don't know if all vertices are on the screen. 49 Suggested Action: have a 5% border 50 Importance: low to not do 51 52 Issue: The mesh produced by triangle isn't of high quality near a low 53 angle formed by two user segments. 54 Reason:triangle 55 Tried: Tried the triangle flags L,i,V (for info). Using box.poly on 56 nautilus. Couldn't get a better quality mesh. 57 58 Issue: Get the naming right for mesh/triangulation/user/generated. 59 How about "outline + triangulation = mesh" 60 Importance: Medium -low 61 62 Issue: S/W - too many methods with the same name on differnent classes 63 eg editWindow. Makes things confusing. 64 Importance: low 65 66 Issue: Normalise seems broken - what is it doing to the attributes?. 67 Suggested Action: remove! 68 69 Bug: Calling 'Generate Mesh' on empty document or If there are no 70 enclosed regions will cause trianglulation to crash pmesh. 71 Importance: low - not do, but document 72 Suggested Action: Catch them (with try) and do nothing 73 notes: Fixing the 'Generate Mesh' crash is a P3 requirement. 74 75 The zoom in/out is jittery 76 77 The initial mesh window coordinates are in the fourth quadrant. 78 79 Deleting a selected object is done with the scroll bar, not the 80 delete key. 81 82 Issue: triangle calculates incorrect attribute values, some of the time. 83 Importance: Medium 84 Suggested Action: Preprocess data to smoth it out. 85 86 Issue: pmesh can not be automatically installed in windows and linux, 87 triangle doesn't compile easily. 88 Installs best in Linux. 89 Importance: Low 90 Suggested Action: delve into setup more so it works with a variety of 91 compilers. 92 93 Issue: two vertices can be ontop of one another 94 Importance: Low 95 Suggested Action: See how it goes when used. The cost of checking 96 probably doesn't outwiegh the benifit. 97 action taken: When loading an xya file duplicate vertices are removed. 98 99 100 Issue: When calculating mesh, have the pointer turn into an hour glass 101 Importance: Low 102 103 **************** 104 CLOSED - issues that have beeen resolved 105 ************ 106 167 Closed: Couldn't be reproduced. suggested action 2 has already been 168 implemented. More investigation required before calling an issue an issue.. 107 169 108 170 Issue: After selecting all for refinement then clearing the selection
Note: See TracChangeset
for help on using the changeset viewer.
