Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
gmsh
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Larry Price
gmsh
Commits
3fb27f42
Commit
3fb27f42
authored
17 years ago
by
Christophe Geuzaine
Browse files
Options
Downloads
Patches
Plain Diff
*** empty log message ***
parent
de17c629
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/TODO
+5
-20
5 additions, 20 deletions
doc/TODO
with
5 additions
and
20 deletions
doc/TODO
+
5
−
20
View file @
3fb27f42
$Id: TODO,v 1.61 2007-09-18 16:26:04 geuzaine Exp $
$Id: TODO,v 1.62 2007-09-24 07:32:09 geuzaine Exp $
********************************************************************
add set<BarycenterData> in VertexArray so that we can do automatic
boundary constructions (should probably be ON by default for 3D scalar
rendering when explode==1). Transfer data to actual arrays in
VertexArray::finalize()
********************************************************************
********************************************************************
...
@@ -44,7 +37,8 @@ add support for Patran mesh files
...
@@ -44,7 +37,8 @@ add support for Patran mesh files
********************************************************************
********************************************************************
reinterface Triangle for plane surfaces
reinterface Triangle for plane surfaces and/or for the generation of
the initial mesh
********************************************************************
********************************************************************
...
@@ -85,7 +79,7 @@ cases
...
@@ -85,7 +79,7 @@ cases
********************************************************************
********************************************************************
implement STL remeshing
re-
implement STL remeshing
********************************************************************
********************************************************************
...
@@ -187,7 +181,7 @@ strategy
...
@@ -187,7 +181,7 @@ strategy
********************************************************************
********************************************************************
add/restore Parametric curve type
(
us
e
MathEval
!)
add/restore Parametric curve type us
ing
MathEval
********************************************************************
********************************************************************
...
@@ -216,14 +210,6 @@ a straightforward way or using 3D textures)
...
@@ -216,14 +210,6 @@ a straightforward way or using 3D textures)
********************************************************************
********************************************************************
"first order" quad/hexa/prism/pyramid mesh visu can actually be wrong,
as we assume the faces are plane--which they don't have to be. We
should subdivide in 2 triangles. And remove the va_quad vertex array
altogether! (ps: should be careful about element boundary drawing;
should then be done like we do it for 2nd order elements)
********************************************************************
Yves Krahenbuhl wrote:
Yves Krahenbuhl wrote:
> Lors de la creation des elements du 2eme ordre, et selon la courbure
> Lors de la creation des elements du 2eme ordre, et selon la courbure
...
@@ -232,4 +218,3 @@ Yves Krahenbuhl wrote:
...
@@ -232,4 +218,3 @@ Yves Krahenbuhl wrote:
> faudrait peut-etre faire apparaitre un message d'erreurs / ou se
> faudrait peut-etre faire apparaitre un message d'erreurs / ou se
> restreindre (automatiquement ou non) a une interpolation lineaire
> restreindre (automatiquement ou non) a une interpolation lineaire
> entre les points en question.
> entre les points en question.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment