We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does SCRAM support referencing other XMLs in the input file? I tried to put the probabilities of basic events in a separate params.xml as follows:
params.xml
<?xml version="1.0"?> <define-basic-event name="BatteryFault"> <float value="0.0001"/> </define-basic-event>
In input.xml (at the same directory as params.xml), I tried to reference the params file as follows:
input.xml
<?xml version="1.0"?> <!DOCTYPE opsa-mef [ <!ENTITY params SYSTEM "params.xml"> ]> <opsa-mef> <define-fault-tree name="DroneFaultTree"> <define-gate name="..."> ... </define-gate> ¶ms; </define-fault-tree> </opsa-mef>
The error message that I got was:
scram::mef::ValidityError File: /home/.../input.xml Line: 106 Undefined event BatteryFault with base path DroneFaultTree
If it helps, my current SCRAM version is
SCRAM 0.16.2 () Dependencies: Boost 1_65_1 libxml2 2.9.4
Line 106 is the event BatteryFault (one of the <or> arguments within <define-gate>). The "..." are in place for brevity.
BatteryFault
<or>
<define-gate>
@rakhimov Please let me know, thank you for your time!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Does SCRAM support referencing other XMLs in the input file? I tried to put the probabilities of basic events in a separate
params.xml
as follows:In
input.xml
(at the same directory asparams.xml
), I tried to reference the params file as follows:The error message that I got was:
If it helps, my current SCRAM version is
Line 106 is the event
BatteryFault
(one of the<or>
arguments within<define-gate>
). The "..." are in place for brevity.@rakhimov Please let me know, thank you for your time!
The text was updated successfully, but these errors were encountered: