Git Product home page Git Product logo

Comments (5)

rodrigomoliveira1 avatar rodrigomoliveira1 commented on August 21, 2024

rotor_convergence.py

This is the first version. The docstring provides further information about the input / output data.

This code also introduce a different way to input the rotor variables. Instead of entering the elements itself, the user may now divides the rotor in regions (as many you want).
For example: if we got a shaft that has 3 sections with different diameters, we could divide the shaft in 3 regions (it could be more regions).

The user defines the number of regions, lenght and diameter. The number of elements per regions will be calculated.

So, why that? Because it spares time to build the model and make things more intuitive. It takes longer to enter a 100 element' model than a 10 regions rotor with 10 elements each.
For now, all the regions will have the same number of elements, and if a region has much larger elements than others, the solution is divide this particular region in more regions.

If you like this way, we could adapt it better and for now on, use this method to input the rotor's data.

from ross.

rodrigomoliveira1 avatar rodrigomoliveira1 commented on August 21, 2024

-> TODO

  • Return the convergence analysis graphs: Relative Error vs Number of Elements and Natural Frequency vs Number of Elements

  • Improve the elements distribution per region. Different number of elements per region.

  • Build elements with different lenghts.

from ross.

rodrigomoliveira1 avatar rodrigomoliveira1 commented on August 21, 2024

-> TODO

  • Return the convergence analysis graphs. (check)

  • Create a classmethod to build the rotor with sections (or regions) in rotor_assembly.py.

  • The class convergence should be a method only, instead of a class.

from ross.

rodrigomoliveira1 avatar rodrigomoliveira1 commented on August 21, 2024

-> TODO

  • Return the convergence analysis graphs. (check)

  • Create a classmethod to build the rotor with sections (or regions) in rotor_assembly.py. (check)

  • The class convergence should be a method only, instead of a class. (check)

All the changes marked as "check" are done in rotor.assembly.py.
This commit has been uploaded in rotor-analysis branch. There is a need for adding pytest codes to check these analysis yet. Besides, the rotor_convergence file will be deleted once the tests are done.

from ross.

raphaeltimbo avatar raphaeltimbo commented on August 21, 2024

Closed by PR #52

from ross.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.