Comments (5)
</define-basic-event>
<define-basic-event name='Line2.VO.fRightFlow_false'>
</define-basic-event>
<define-gate name='Reacto.vfInFlow_false'>
<and>
<basic-event name='Line1.VO.fRightFlow_false'/>
<basic-event name='Line2.VO.fRightFlow_false'/>
</and>
</define-gate>
from mef.
Use for "or" logic. You should create intermediate gate for Line1.P (you should not use inside ) .
If you want to find a software that is compatible with this Open-PSA (for export en import), you can try the free demo version of GRIF (Fault-Tree module). It is perfect to test small files. But you will need the full version is you have more than 5 basic events.
from mef.
</define-basic-event> <define-basic-event name='Line2.VO.fRightFlow_false'> </define-basic-event> <define-gate name='Reacto.vfInFlow_false'> <and> <basic-event name='Line1.VO.fRightFlow_false'/> <basic-event name='Line2.VO.fRightFlow_false'/> </and> </define-gate>
Where did this snippet come from? The xml file I uploaded should be:
<define-gate name="Line2.VO.vfRightFlow_false" >
<gate name="Line2.P.vfOutFlow_false" />
</define-gate>
<define-gate name="Reactor.vfInFlow_false" >
<and >
<gate name="Line1.VO.vfRightFlow_false" />
<gate name="Line2.VO.vfRightFlow_false" />
</and>
</define-gate>
The differences between the above two paragraphs:
Reacto.vfInFlow_false vs Reactor.vfInFlow_false
Line1.VO.fRightFlow_false vs Line1.VO.vfRightFlow_false
Line2.VO.fRightFlow_false vs Line2.VO.vfRightFlow_false
But I think these differences are not the key to the problem.
from mef.
Use for "or" logic. You should create intermediate gate for Line1.P (you should not use inside ) .
If you want to find a software that is compatible with this Open-PSA (for export en import), you can try the free demo version of GRIF (Fault-Tree module). It is perfect to test small files. But you will need the full version is you have more than 5 basic events.
Use for "or" logic: What is the basis for this conclusion?
Now that we know the fault trees of each component on the two lines and the fault tree of the Reactor, we can connect these scattered fault trees to construct a complete fault tree. My problem is that it seems that the information like Use for "or" logic
is missing in the xml file.
from mef.
Use for "or" logic. You should create intermediate gate for Line1.P (you should not use inside ) .
If you want to find a software that is compatible with this Open-PSA (for export en import), you can try the free demo version of GRIF (Fault-Tree module). It is perfect to test small files. But you will need the full version is you have more than 5 basic events.Use for "or" logic: What is the basis for this conclusion? Now that we know the fault trees of each component on the two lines and the fault tree of the Reactor, we can connect these scattered fault trees to construct a complete fault tree. My problem is that it seems that the information like
Use for "or" logic
is missing in the xml file.
Sorry, I misunderstood, I thought you tried to write an Open-PSA file manually for an "and" gate, based on the topic : "How to connect Reactor Fault Tree to Line1 and Line2's Fault Tree". The file I attached was generated "manually" (with typo errors ;-) ) based on your "reactor fault-tree" table. I didn't read the tutorial.
Maybe you should try to as people who did the tutorial.
from mef.
Related Issues (20)
- Boolean operator symbols instead of 'words' in formulas HOT 1
- Transition to RELAX NG Compact schema language
- pdf: Missing section numbers in titles HOT 1
- pdf: Table head highlighting
- html: Search feature doesn't work HOT 1
- Unspecified, ambiguous location of "model-data" declaration HOT 1
- "include" specification clarification HOT 1
- Log-Normal distribution Error Factor general formula/explanation HOT 2
- Precisely specify Minimal Cut Set (MCS) and Prime Implicant (PI)
- Incorrect formula for Histogram distribution expected value HOT 1
- Discrete Distribution
- Piecewise Linear Distribution HOT 1
- Random Random Deviates? HOT 1
- Does "Extern function" imply dynamic loading?
- Typing of Expression
- Parameter "units" are underspecified HOT 1
- Fault tree variable redefinition allowance breaks the declarative language HOT 1
- Uniqueness of attributes
- Redundant mix of 'etc./...' with 'for example/like/such as/(examples)'
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mef.