Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to 0.3.0 #8

Open
6 tasks
ahojukka5 opened this issue Jan 3, 2018 · 0 comments
Open
6 tasks

Changes to 0.3.0 #8

ahojukka5 opened this issue Jan 3, 2018 · 0 comments

Comments

@ahojukka5
Copy link
Member

ahojukka5 commented Jan 3, 2018

Some of changes are probably breaking backward compatibility. New ideas welcome.

  • Give connectivity as tuple + other things that does not need calculations.

  • Element id required, change problem.elements from array to dict? In output writing we need some order anyway and id-numering elements is quite standard in other FEMs.

  • Naming: element.properties -> element.basis.

  • More intelligent way to calculate global dofs. Give unknown field name of problem with a tuple of symbols, (:u1, :u2, :u3) for vector field, :T for temperature field and so on. Or ("Displacement 1", "Displacement 2"). For hybrid problems, e.g. displacement + pressure, have ((:u1, :u2, :u3), :p). The question is how to set up this information to BoundaryProblems and how to update elements after global solution.

  • A separate algorithm to calculate global dofs for each element before assembly.

  • Just like element.fields, also solver and problem have equivalent way to create and update fields.

@ahojukka5 ahojukka5 changed the title Use Tuples Changes to 0.2.0 Jan 6, 2018
@ahojukka5 ahojukka5 changed the title Changes to 0.2.0 Changes to 0.3.0 Sep 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant