CBC.Solve

A common file/method naming structure should be enforced across different projects

Registered by Harish Narayanan

Currently, twist and flow have a different file hierarchy and different names for methods in classes. This should be unified.

Blueprint information

Status:
Started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Harish Narayanan
Definition:
Discussion
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Harish Narayanan

Related branches

Sprints

Whiteboard

My currently proposed file hierarchy looks like the following. It would be good to discuss it here before I change everything to meet this spec.

twist/
 problem_definitions.py (HyperElasticity, (ViscoElasticity), ...)
 solution_algorithms.py (HyperElasticitySolver, ...)
 material_models.py (neoHookean, MooneyRivlin, Biderman, ...)
 kinematics.py (Strain measures, Transformations between configurations, ...)

flow/
 problem_definitions.py (NavierStokes (Generally))
 solution_algorithms (NavierStokesSolver1, NavierStokesSolver2, ...)
 material_models.py (Newtonian, GradeTwo, ...)
 kinematics.py (Strain rate measure, ...)

Coming to think of it, I also propose that kinematics.py be moved to 'common.'

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.
Edit subscription

Subscribers

No subscribers.