archive-fr.com » FR » O » OPUS-PROJECT.FR

Total: 702

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Contribution Overview
    few words there are three levels of integration from least to most integrated Opus Forum The contributor uses the forum space available in the OPUS web site to discuss and propose features or ideas in a completely free way from a simple algorithm to a bit of code or even a complete module albeit incompatible with other OPUS contributions Scripts articles commentaries concerning a method or its software development as well as preprints are typical ways to contribute at the Forum level Apart from adding features the contributor can also provide test cases usually industrial examples showing the way in which OPUS methods and tools can be used to solve a real life problem While not a software contribution this form of contribution is both important and precious Note however that a test case providing useful insights into uncertainty study is perfectly acceptable as a contribution even if it is not tailored to use the software features developed within OPUS The various contributions can be shared on the download tab Opus Contrib This is the main way in which features are supposed to be provided by the community Most of restricting rules proper to to the Lib level have been released The main points to note are contributions at this level can be written in any of the following supported languages C Python R Scilab Matlab Octave the contribution s quality is the contributor s responsibility it is up to him her to ensure the quality of the code the respect of the programming rules as well as the mathematical correctness different kinds of OPUS Contrib contribution types exist differentiated with respect to the integration with the others see Contribution Guide Opus Lib The code fulfills a high level of quality following established OPUS programming rules The contribution will from

    Original URL path: http://www.opus-project.fr/index.php/contributionmain/overview?tmpl=component&print=1&page= (2016-01-11)
    Open archived version from archive


  • Contribution Overview
    a few words there are three levels of integration from least to most integrated Opus Forum The contributor uses the forum space available in the OPUS web site to discuss and propose features or ideas in a completely free way from a simple algorithm to a bit of code or even a complete module albeit incompatible with other OPUS contributions Scripts articles commentaries concerning a method or its software development as well as preprints are typical ways to contribute at the Forum level Apart from adding features the contributor can also provide test cases usually industrial examples showing the way in which OPUS methods and tools can be used to solve a real life problem While not a software contribution this form of contribution is both important and precious Note however that a test case providing useful insights into uncertainty study is perfectly acceptable as a contribution even if it is not tailored to use the software features developed within OPUS The various contributions can be shared on the download tab Opus Contrib This is the main way in which features are supposed to be provided by the community Most of restricting rules proper to to the Lib level have been released The main points to note are contributions at this level can be written in any of the following supported languages C Python R Scilab Matlab Octave the contribution s quality is the contributor s responsibility it is up to him her to ensure the quality of the code the respect of the programming rules as well as the mathematical correctness different kinds of OPUS Contrib contribution types exist differentiated with respect to the integration with the others see Contribution Guide Opus Lib The code fulfills a high level of quality following established OPUS programming rules The contribution will

    Original URL path: http://www.opus-project.fr/index.php/contributionmain/overview?el_mcal_month=12&el_mcal_year=2015 (2016-01-11)
    Open archived version from archive

  • Contribution Overview
    In a few words there are three levels of integration from least to most integrated Opus Forum The contributor uses the forum space available in the OPUS web site to discuss and propose features or ideas in a completely free way from a simple algorithm to a bit of code or even a complete module albeit incompatible with other OPUS contributions Scripts articles commentaries concerning a method or its software development as well as preprints are typical ways to contribute at the Forum level Apart from adding features the contributor can also provide test cases usually industrial examples showing the way in which OPUS methods and tools can be used to solve a real life problem While not a software contribution this form of contribution is both important and precious Note however that a test case providing useful insights into uncertainty study is perfectly acceptable as a contribution even if it is not tailored to use the software features developed within OPUS The various contributions can be shared on the download tab Opus Contrib This is the main way in which features are supposed to be provided by the community Most of restricting rules proper to to the Lib level have been released The main points to note are contributions at this level can be written in any of the following supported languages C Python R Scilab Matlab Octave the contribution s quality is the contributor s responsibility it is up to him her to ensure the quality of the code the respect of the programming rules as well as the mathematical correctness different kinds of OPUS Contrib contribution types exist differentiated with respect to the integration with the others see Contribution Guide Opus Lib The code fulfills a high level of quality following established OPUS programming rules The contribution

    Original URL path: http://www.opus-project.fr/index.php/contributionmain/overview?el_mcal_month=2&el_mcal_year=2016 (2016-01-11)
    Open archived version from archive

  • Contribution process
    identification following a need emerging from the case studies the method to be implemented is identified Complete mathematical description of the method for this part the references are found Among all the sources the most obvious are scientific articles and books The references should cover the whole algorithms and concepts involved in the development of the function Structured mathematical description this document describes the mathematical process followed by the method This description is self sufficient homogeneous in terms of notations and as structured as possible to make the emergence of concepts as easy as possible The software conception is based on this document Software conception from the structured mathematical description it is then easier to choose the objects that are implemented It highlights the services attached to the objects the dependencies with other objects and or the possibility to use existing objects Development when the conception is done the development starts It consists in the implementation of the objects and algorithms Opus has a set of development rules that should be followed in all cases but must be followed if the contribution is to be integrated at the Opus Lib level See the Programming Rules guide and following articles for more detail Test cases and unitary validation this step is required in order to demonstrate that the development is correct Each object and methods should be tested and validated with comparisons with analytical methods or reference methods Documentation of the development a documentation of the development is required in order to secure the development and its maintainability There are several types of documentation Reference documentation it contains the mathematical basis of the method developed It is based on the structured mathematical description Architecture documentation it describes the architecture of the different objects developed and their link with the existing version

    Original URL path: http://www.opus-project.fr/index.php/contributionmain/levels?tmpl=component&print=1&page= (2016-01-11)
    Open archived version from archive

  • Opus Contrib
    be written in any of the following supported languages C Python R Scilab Matlab Octave The contribution s quality is the contributor s responsibility it is up to him her to ensure the quality of the code the respect of the programming rules as well as the mathematical correctness Different kinds of OPUS Contrib contribution types exist differentiated with respect to the integration with the others Integration the package is created using the OPUS module system basically a C module with the corresponding Python layer and written according to the relevant rules however the contributor chooses not to aim at OPUS Lib for a variety of reasons e g releasing some constraints due to programming quality Compatibility the package is compatible with the rest of OPUS i e written using a language or formalism allowing it to directly interact with OPUS This means either 1 a C code which can use all Lib and C Contrib features The code may be contributed with or without the corresponding Python layer 2 a Python script which can use all of the Lib and all installed Python features C Python features and Opus style modules from Contrib 3 a Scilab script using OPUS

    Original URL path: http://www.opus-project.fr/index.php/contributionmain/72-opuscontrib (2016-01-11)
    Open archived version from archive

  • Opus Forum
    OPUS contributions Scripts articles commentaries concerning a method or its software development as well as preprints are typical ways to contribute at the Forum level Apart from adding features the contributor can also provide test cases usually industrial examples showing the way in which OPUS methods and tools can be used to solve a real life problem While not a software contribution this form of contribution is both important and

    Original URL path: http://www.opus-project.fr/index.php/contributionmain/73-opusforum (2016-01-11)
    Open archived version from archive

  • Test Cases
    test cases While not a software contribution in the strict sense this form of contribution is both important and precious and deserves its own article A test case is usually an industrial example showing the way in which the platform can be used to solve a real life problem The manner and production of such a test case is detailed in the Contribution Guide but in a nutshell the process should be along the lines of Clearly define the problem that will be solved as it was in real life prior to resolution context quantity of interest available data expected difficulties and possible solutions expected results and corresponding interpretation Gather the real life data used in a format usable by Opus ideally CSV Explain the method used to solve the real life problem from raw data to the final quantity of interest and its interpretation Identify the corresponding features from Opus and formulate the associated series of commands Check that the results obtained meet the real life results At this point the test case is ready to be submitted to the consortium and if accepted will either be uploaded as a webpage with associated data files and command checklist or

    Original URL path: http://www.opus-project.fr/index.php/contributionmain/76-testcases (2016-01-11)
    Open archived version from archive

  • Contribution process
    Functional identification following a need emerging from the case studies the method to be implemented is identified Complete mathematical description of the method for this part the references are found Among all the sources the most obvious are scientific articles and books The references should cover the whole algorithms and concepts involved in the development of the function Structured mathematical description this document describes the mathematical process followed by the method This description is self sufficient homogeneous in terms of notations and as structured as possible to make the emergence of concepts as easy as possible The software conception is based on this document Software conception from the structured mathematical description it is then easier to choose the objects that are implemented It highlights the services attached to the objects the dependencies with other objects and or the possibility to use existing objects Development when the conception is done the development starts It consists in the implementation of the objects and algorithms Opus has a set of development rules that should be followed in all cases but must be followed if the contribution is to be integrated at the Opus Lib level See the Programming Rules guide and following articles for more detail Test cases and unitary validation this step is required in order to demonstrate that the development is correct Each object and methods should be tested and validated with comparisons with analytical methods or reference methods Documentation of the development a documentation of the development is required in order to secure the development and its maintainability There are several types of documentation Reference documentation it contains the mathematical basis of the method developed It is based on the structured mathematical description Architecture documentation it describes the architecture of the different objects developed and their link with the existing

    Original URL path: http://www.opus-project.fr/index.php/contributionmain/levels?el_mcal_month=12&el_mcal_year=2015 (2016-01-11)
    Open archived version from archive