feelpp / mordicus Goto Github PK

By running pytest in a repertory other than home, it create 2 folders named feelppdb. One in the main repertory and other in the home directory. But all the data are stocked in the last one.

• #27
• #28
• #29
• #30

Creating of my first issue

• study https://docs.github.com/en/get-started/quickstart/hello-world

• documentation is here : https://mordicus.readthedocs.io/en/latest/
• safran examples: https://genericrom.readthedocs.io/en/latest/
• study https://genericrom.readthedocs.io/en/latest/_methods/index.html#noninstrusivity

• read https://docs.github.com/en/actions
• study mordicus actions
• propose updates
• added badges to README file

update the report for BPI and region grand est

the implementation is in https://github.com/feelpp/mordicus/tree/cemosis/src/poc-1/examples/Modules/Sorbonne

run the example or create a simple one

We need to make sure that Mordicus works in the python framework of Salome

• create a docker image with mordicus/salome
• add tests in ci for salome/mordicus

Set up auto test using NIRB methods

add nirb support from feelpp to mordicus

badges can be useful to check the health status and some metric of a software

pytest does not run properly currently

• dependence of basic tools
• dependence of feelpp

use try except block to avoid issues

• run pytests
• understand and document organisation of the code in the toplevel README

install Modicus python module using cmake

Make the implementation of NIRB methods by using Feelpp environment

use sphinx to build and then github actions to deploy the documentation to gh-pages

some feelpp tests need to be updated and fixed

Fix all the bugs comming from ESI test case

nirb needs to be tested to ensure proper results

fix all the bugs coming from Cemosis test cases.

reduced-basis-methods-for-time-dependent-problems.pdf

Patera_Rozza_-_RB_Approximation_and_a_posteriori_error_estimation_for_PPDE.pdf

add Mordicus core coverage in github ci

we can point to feelpp docs for nirb