Bug 824147 - asimut: structural model simulation gives incorrect results (i.e. undefined outputs)
asimut: structural model simulation gives incorrect results (i.e. undefined o...
Product: Fedora
Classification: Fedora
Component: alliance (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Chitlesh GOORAH
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-05-22 16:09 EDT by Ashwith Rego
Modified: 2014-02-05 06:58 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-02-05 06:58:21 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Source files required for reproducing the bug. (10.00 KB, application/x-tar)
2012-05-22 16:09 EDT, Ashwith Rego
no flags Details

  None (edit)
Description Ashwith Rego 2012-05-22 16:09:59 EDT
Created attachment 586156 [details]
Source files required for reproducing the bug.

Description of problem:

I'm getting "?u" in the output pattern file when I use asimut to run a schematic model based simulation.

I first wrote a behavioral vbe file to describe an inverter. I next used boog to convert this to it's vst equivalent.

Next I ran a simulation with an input pattern. I saw ?u at the output.



How reproducible:

Happens every time

Steps to Reproduce:

1. Untar the attachment invg.tar
2. Run 
      boog invg invg -x 1 -m 2
3. Next, run
      asimut invg invg_in invg_out

Actual results:

Here is the output pattern (input is a, output is x):

--                                 vva x 
--                                 ds    
--                                 ds    

                                 : 100?u;
                                 : 101?u;

Expected results:

--                                 vva x 
--                                 ds    
--                                 ds    

                                 : 100?1;
                                 : 101?0;

Additional info:

I checked that this issue occurs with an AND gate and OR gate description as well. This is my first time with alliance so I'm sorry if I've done something wrong in the procedure itself.

The attachment contains 

invg.vbe - the behavioral description of the inverter
invg_in.pat - the input pattern
Comment 1 Ashwith Rego 2012-05-22 16:32:02 EDT
The Description section of the report has a typo. 
I ran a simulation of a structural description (not schematic).
Comment 2 Ashwith Rego 2012-06-28 13:41:41 EDT
Changed version to 17 as the issue is present on Fedora 17 as well. Package installed is: alliance-5.0-34.20090901snap.fc17.x86_64
Comment 3 Ashwith Rego 2013-02-26 14:03:35 EST
Updating version to Fedora 18.
Comment 4 Fedora End Of Life 2013-12-21 03:36:33 EST
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2014-02-05 06:58:24 EST
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.