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

Python bindings for pre-/post-processing #9015

Closed
8 tasks done
agrayver opened this issue Nov 7, 2019 · 4 comments
Closed
8 tasks done

Python bindings for pre-/post-processing #9015

agrayver opened this issue Nov 7, 2019 · 4 comments
Labels

Comments

@agrayver
Copy link
Contributor

agrayver commented Nov 7, 2019

@dealii

I have decided to turn this into a meta-issue that will track my efforts towards a better python support in deal.II.

If anyone has something to add, feel free.

@agrayver
Copy link
Contributor Author

agrayver commented Nov 7, 2019

@Rombur I see you already implemented merge/shift -- do you see any caveats for other functions?

@Rombur
Copy link
Member

Rombur commented Nov 7, 2019

Being able to do step-49 in python would be really great! I think that it should be straight forward. You should be able to follow the recipe used for the functions that have already been ported but let me know if you encounter any problem.

@agrayver
Copy link
Contributor Author

I would like to consult regarding the nature and place of the new python tutorials (step-49, step-53 initially). They will replicate the functionality of the original programs, using the python bindings and will be presented using the python notebooks.

Should they be placed next to the C++ programs, in the corresponding folders?

@Rombur @masterleinad ping

@Rombur
Copy link
Member

Rombur commented Jan 21, 2020

I think they should go with the other python notebooks in contrib/python-bindings/notebooks and I would add a section in the C++ tutorials that links to the python notebooks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants