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

Add docs? (if needed) #30

Open
IAlibay opened this issue Jun 11, 2022 · 4 comments
Open

Add docs? (if needed) #30

IAlibay opened this issue Jun 11, 2022 · 4 comments

Comments

@IAlibay
Copy link
Member

IAlibay commented Jun 11, 2022

Adding this issue here as it might be a feature of the ongoing GSoC.

It might be worth consider what, if any, docs should be added / deployed for panedr.

@IAlibay
Copy link
Member Author

IAlibay commented Jun 11, 2022

General addition of class docstrings would be a good starting point @BFedder - it'll let you double check that what you are making the same assumptions about how the classes are behaving as how @jbarnoud wrote them.

@jbarnoud
Copy link
Collaborator

The code tries to follow the gromacs code as much as possible. It is a good place to start to understand.

@orbeckst
Copy link
Member

There should be minimal docs — we tend to preach that any package should have

  • docs
  • tests at sufficient coverage
  • defined API

so we should also have them for panedr.

@jbarnoud
Copy link
Collaborator

There used to be a single exposed function and it was documented in the readme 😛

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

3 participants