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".
  • WikiPageNames (diff) – Opus Project
    names must follow these rules 7 8 1 The name must consist of alphabetic characters only No digits spaces punctuation or underscores are allowed 9 2 A name must have at least two capital letters 10 3 The first character must be capitalized 11 4 Every capital letter must be followed by one or more lower case letters 12 5 The use of slash is permitted in page names possibly representing a hierarchy 13 14 If you want to create a wiki page that doesn t follow CamelCase rules you can use the following syntax 15 16 wiki Wiki page wiki ISO9000 17 wiki Space Matters that page name embeds space characters 18 or simply WikiPageName s MoinMoin s internal free links style 19 20 21 This will be rendered as 22 wiki Wiki page wiki ISO9000 23 wiki Space Matters that page name embeds space characters 24 or simply WikiPageName s MoinMoin s internal free links style 25 26 Starting with Trac 0 11 it s also possible to link to a specific version of a Wiki page as you would do for a specific version of a file for example WikiStart 1 27 28 See also TracLinks QuotingspaceinTracLinks

    Original URL path: http://www.opus-project.fr/trac/wiki/WikiPageNames?action=diff&version=1 (2016-01-11)
    Open archived version from archive


  • WikiProcessors (diff) – Opus Project
    such blocks of HTML have to be self contained i e you can t start an HTML element in one block and close it later in a second block Use div or span processors for achieving similar effect see WikiHtml 29 30 31 32 Example 2 inserting Restructured Text in wiki text 33 34 35 html 36 pre class wiki 37 rst 38 A header 39 40 This is some text with a footnote 41 42 This is the footnote 43 pre 44 45 46 Results in 47 48 rst 49 A header 50 51 This is some text with a footnote 52 53 This is the footnote 54 55 56 Example 3 inserting a block of C source code in wiki text 57 58 59 html 60 pre class wiki 61 c 62 int main int argc char argv 63 64 printf Hello World n 65 return 0 66 67 pre 68 69 70 Results in 71 72 c 73 int main int argc char argv 74 75 printf Hello World n 76 return 0 77 78 79 80 81 82 Available Processors 83 The following processors are included in the Trac distribution 84 html Insert custom HTML in a wiki page See WikiHtml 85 div Wrap an arbitrary Wiki content in a div element since 0 11 See WikiHtml 86 span Wrap an arbitrary Wiki content in a span element since 0 11 See also WikiHtml 87 rst Trac support for Restructured Text See WikiRestructuredText 88 textile Supported if http cheeseshop python org pypi textile Textile is installed See http www textism com tools textile a Textile reference 89 comment Do not process the text in this section i e contents exist only in the plain text not in the rendered page 90 91 Code Highlighting Support 92

    Original URL path: http://www.opus-project.fr/trac/wiki/WikiProcessors?action=diff&version=1 (2016-01-11)
    Open archived version from archive

  • WikiRestructuredText (diff) – Opus Project
    sourceforge net rst html 17 RST Quick Reference http docutils sourceforge net docs rst quickref html 18 19 20 21 Using RST in Trac 22 To specify that a block of text should be parsed using RST use the rst processor 23 24 TracLinks in reStructuredText 25 26 Trac provides a custom RST directive trac to allow TracLinks from within RST text 27 28 Example 29 30 31 rst 32 This is a reference to a ticket 33 34 a ticket trac 42 35 36 37 38 Trac allows an even easier way of creating TracLinks in RST using the custom trac role 39 40 Example 41 42 43 rst 44 This is a reference to ticket 12 trac 45 46 To learn how to use Trac see TracGuide trac 47 48 49 50 For a complete example of all uses of the trac role please see WikiRestructuredTextLinks 51 52 53 Syntax highlighting in reStructuredText 54 55 There is a directive for doing TracSyntaxColoring in RST as well The directive is called 56 code block 57 58 Example 59 60 61 62 rst 63 64 code block python 65 66 class Test 67 68 def TestFunction self 69 pass 70 71 72 73 74 Will result in the below 75 76 77 rst 78 79 code block python 80 81 class Test 82 83 def TestFunction self 84 pass 85 86 87 88 Wiki Macros in reStructuredText 89 90 For doing WikiMacros Wiki Macros in RST you use the same directive as for syntax highlighting i e 91 code block To work you must use a version of trac that has trac ticket 801 801 applied 92 93 Wiki Macro Example 94 95 96 97 rst 98 99 code block RecentChanges 100 101 Trac 3 102 103 104 105 106

    Original URL path: http://www.opus-project.fr/trac/wiki/WikiRestructuredText?action=diff&version=1 (2016-01-11)
    Open archived version from archive

  • WikiRestructuredTextLinks (diff) – Opus Project
    1 or trac changeset 1 14 Revision log trac r1 3 trac 1 3 or trac log 1 3 trac log trunk 1 3 15 Diffs since version 0 10 trac diff 20 30 trac diff tags trac 0 9 2 wiki default tags trac 0 9 3 wiki default or trac diff trunk trac 3538 sandbox vc refactoring trac 3539 16 Wiki pages trac CamelCase or trac wiki CamelCase 17 Milestones trac milestone 1 0 18 Attachment trac attachment ticket 944 attachment 1073 diff 19 Files trac source trunk COPYING 20 A specific file revision trac source trunk COPYING 200 21 A particular line of a specific file revision trac source trunk COPYING 200 L25 22 23 An explicit label can be specified separated from the link by a space 24 25 See trac 1 ticket 1 and the trac source trunk COPYING license 26 27 28 29 Provided you have docutils installed the above block will render as 30 31 32 rst 33 Examples 34 35 Tickets trac 1 or trac ticket 1 36 Ticket comments trac comment ticket 1 2 37 Reports trac 1 or trac report 1 38 Changesets trac r1 trac 1 or trac changeset 1 39 Revision log trac r1 3 trac 1 3 or trac log 1 3 trac log trunk 1 3 40 Diffs since version 0 10 trac diff 20 30 trac diff tags trac 0 9 2 wiki default tags trac 0 9 3 wiki default or trac diff trunk trac 3538 sandbox vc refactoring trac 3539 41 Wiki pages trac CamelCase or trac wiki CamelCase 42 Milestones trac milestone 1 0 43 Attachment trac attachment ticket 944 attachment 1073 diff 44 Files trac source trunk COPYING 45 A specific file revision trac source trunk COPYING 200 46 A particular

    Original URL path: http://www.opus-project.fr/trac/wiki/WikiRestructuredTextLinks?action=diff&version=1 (2016-01-11)
    Open archived version from archive

  • Wp0 (diff) – Opus Project
    beginning the collaborative web internet extranet allows researchers industrials and developers to keep connected during the project life time 18 19 Moreover during the project the web resource plays an important role in disseminating the results it centralises the documents scientific papers data and reports produced during the project The OPUS platform Open Source release is a start for the improvements and extensions a suitable infrastructure should be ready on therefore completing the mission of this tool 20 21 WP0 3 Dissemination 22 23 Researches used to say that good research project never ends as it keeps discovering the issues to tackle as the next stage It is not the aim of this project however OPUS project targets a completed and sustainable platform that is poised to succeed thanks to its deep foundations on industrial needs and its cutting edge contain and sensible business model Meanwhile it is not supposed to sustain on 24 this basis only The Complex System Design Software inspires many people in France Europe and worldwide Indeed by building and maintaining close links with existing and emerging communities the Uncertainty Treatment platform may reach many more end users contributors and business peoples 25 26 Considering the importance of this task for the overall prospects of the project product it was decided to design a specific work package on purpose It implements the internal and external communication policy agreed with WP0 1 and WP0 management and expert college respectively 27 28 The Communication Dissemination working package coordination responsibility is confided to ECP as it is already present in many stakeholders meeting places and relevant projects in France and abroad 29 30 This WP s actions include the contribution to the creation and regular update of the internet and extranet sites It is in charge of organisation of transitional thematic workshops aimed at results dissemination and endorsement by the scientific community 31 32 Moreover WP0 3 is responsible for coordination of activities aimed at promotion of the Generic Uncertainty Management mindset practices and platform to the relevant communities and encouraging the use of it including in the projects to emerge The main communication axes includes 33 34 SCILAB community 35 R community 36 High Performance Modelling community particularly via TERATEC 37 Complex System Design Community 38 Superior and Professional education community 39 The ImdR national group Incertitudes et Industrie gathering large French industrial companies and research units 40 41 Such actions include 42 Links and advertising from relevant project Home Pages Scilab R to OPUS web site 43 OPUS toolboxes references by original software Scialb R contribution pages 44 Promoting OPUS through relevant conferences and events 45 Design a modules for Engineering Schools and on the methods dealing with uncertainties in numerical modelling 46 Promoting generic uncertainty treatment foundations of OPUS in various stakeholder communities 47 48 WP0 Expert College 49 50 The rich experience of various co funded projects where OPUS members were involved as collaborators or coordinators shows how hard it may be to keep an

    Original URL path: http://www.opus-project.fr/trac/wiki/Wp0?action=diff&version=1 (2016-01-11)
    Open archived version from archive

  • Wp1 (diff) – Opus Project
    indicates the need for the interfaces to be designed to communicate easily with the most recent developments in the connecting fields high performance Simulation platform SALOME complex system design platform SCOS scientific computing language SCILAB statistical programming software R many domain specific uncertainty libraries and computer codes 11 High performing means that the coding practices and core data models specifications must be on the cutting edge of the resources management 12 Gatherer puts an accent on the requirement to communicate with home made sometimes commercial software and computer models 13 Open highlights that the product codes and documentation must be comprehensive enough to be developer friendly let alone the user friendliness the must 14 Supported Sustained underlines the need to have an evolving structure enabling it to accommodate to any particular development environment and potentially to modern concepts still to emerge 15 16 Based on the renowned partners know how in Open Source Platform design and Uncertainty Management Methodology EDF and DA two industrial partners lead the cornerstone specification task 17 18 This work is evenly split between the specifications of scientific research to be carried by the WP2 and the Software specifications for the building blocks and the whole platform that results from the WP3 actions 19 20 The former mostly features the scope definition for every methodological innovation That includes providing the scientists with a sufficiently wide spectrum of industrial cases both by problem set ups and application fields 21 22 The Software specifications are based on the cutting edge current development practices and latest available platforms Given the recent progress in the software development it is needless to build the Generic Open Source Uncertainty Management Platform from scratch based on the benchmark of these developments it is sensible to inherit the core data model specifications as well

    Original URL path: http://www.opus-project.fr/trac/wiki/Wp1?action=diff&version=1 (2016-01-11)
    Open archived version from archive

  • Wp3 (diff) – Opus Project
    16 21 29 6 years ago Author pmpair Comment Legend Unmodified Added Removed Modified Wp3 v1 v1 1 WP3 Validation Demonstration 2 3 It is unconceivable nowadays to start a research project without a clear specification of expected results Nevertheless the validation remains as unavoidable as ever not least because an industrial success story worth to some stakeholders many more than dozens of scientific reviews 4 5 EADS an industrial partner is designated to coordinate the validations demonstration activity as the variety of its business areas the study cases can challenge any would be generic product 6 7 The actions of this working package are run by four industrial partners CEA DA EADS and EDF on the industrial cases representatives for each groups business areas 8 9 This WP is an essential step for the project It completes the two stage validation path to be run through by scientific advance prior to the industrialisation investment First Expert College endorsement and then industrial relevancy assessment drastically reduces the likelihood for an industrialised version of methodology and platform to miss its target or upset it users 10 11 Each methodology will be challenged by a handpicked industrial cases from 12 Mechanical and

    Original URL path: http://www.opus-project.fr/trac/wiki/Wp3?action=diff&version=1 (2016-01-11)
    Open archived version from archive

  • Wp4 (diff) – Opus Project
    Added Removed Modified Wp4 v1 v1 1 WP4 Industrialisation Output durability 2 3 Softia a French start up committed at providing industrial players with services for Open Source software leads this working package 4 This Working package is split in two major activities 5 6 Detailed specification for Industrialisation 7 Industrialisation Development 8 9 Detailed industrialisation specifications are the basic development document to be provided with a platform Its quality and thoroughness are essential for the development and the product future as well 10 11 Industrialisation stage steps in when the method prototypes are both scientifically endorsed and industrially validated It aims to produce a user friendly fully documented and easily maintainable and evolving ready toolboxes for the OPUS platform 12 13 Besides the software deliveries this package address the issues like Infrastructure specifications and Open Source business model It aims at casting some light on what are the service offer expectations of large companies in the uncertainty treatment field or what is the infrastructure that gets the best from the OPUS platform current industrial practice and available technology networks 14 15 These deliverables although not straightforwardly connected to the scientific aims of the OPUS project are essential for its

    Original URL path: http://www.opus-project.fr/trac/wiki/Wp4?action=diff&version=1 (2016-01-11)
    Open archived version from archive