petrobras / ross

ROSS is a library written in Python for rotordynamic analysis.
https://ross.readthedocs.io
Apache License 2.0
129 stars 101 forks source link

Improve documentation #236

Closed flaviorangel closed 4 years ago

flaviorangel commented 5 years ago

This issue is related to issue #223. In order to publish in Joss, we need to improve our documentation. Every function/method must be documented, including inputs, outputs, and an example. I'll be listing here the functions/methods that need their documentation to be improved (and why).

flaviorangel commented 5 years ago

In rotor_assembly.py:

flaviorangel commented 5 years ago

In bearing_seal_element.py:

From BearingElement class:

From class SealElement

flaviorangel commented 5 years ago

In disk_element.py:

flaviorangel commented 5 years ago

In element.py:

flaviorangel commented 5 years ago

In materials.py:

flaviorangel commented 5 years ago

In results.py:

From class Results:

From class CampbellResults:

From class FrequencyResponseResults

From class ForcedResponseResults

From class ModeShapeResults:

From class StaticResults:

From class ConvergenceResults:

From class TimeResponseResults:

flaviorangel commented 5 years ago

In shaft_element.py:

From class ShaftElement:

From class ShaftTaperedElement:

flaviorangel commented 5 years ago

In utils.py:

flaviorangel commented 5 years ago

In fluid_flow.py:

flaviorangel commented 5 years ago

Because there are so many different files to work on, and more than one person working on them, we agreed to let the others know in which file we are working on. So I'm on bearing_seal_element.py

rodrigomoliveira1 commented 5 years ago

I'm working on rotor_assembly.py

flaviorangel commented 5 years ago

So I'm on bearing_seal_element.py

bearing_seal_element.py is almost done. A few functions still need attention though: the ones from _Coefficient class, as I wasn't sure on how to explain them; and the "patch" functions, which I found it hard to create an example to.

I'll be working on disk_element.py

rodrigomoliveira1 commented 5 years ago

I've been working on results.py documentation and I wanted to raise two issues:

flaviorangel commented 5 years ago

I'll be working on element.py. There is an open PR for materials.py, so we got it all covered.

flaviorangel commented 5 years ago
  • I did not improved anything in class Results because it's obsolete and it's going to be removed soon.

Okay. Once it is removed, we no longer have to worry about it.

  • I did not implemented any example because if we calls rotor_example() in results.py, we get a recursive error. We cannot import rotor_assembly.py in results.py if rotor_assembly.py already imports results.py

This is a tricky one. I'm not sure how we should handle this. Maybe we could leave it without examples and see if the reviewers will require some.

raphaeltimbo commented 4 years ago

I believe we can close this for now.