[ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded

  • From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
  • To: "ibis-macro@xxxxxxxxxxxxx" <ibis-macro@xxxxxxxxxxxxx>
  • Date: Wed, 4 Sep 2013 04:04:20 +0000

Bob,

I got it now, you are basically "factoring out" the
rules which are the same, and dwell on the different
stuff on a case-by-case basis.  We can do it that way
too.  Let me spend a little time to see how that should
go then.

Thanks,

Arpad
=========================================================

From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] 
On Behalf Of Bob Ross
Sent: Tuesday, September 03, 2013 6:26 PM
To: Muranyi, Arpad; ibis-macro@xxxxxxxxxxxxx
Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded

Arpad:

My comments were with respect to your wording, which I wanted to
simplify or modify.

For both [External Model] and [External Circuit], the wording should
be nearly identical and simple for a).   While it is expected that a
.ami file exists as a result of an [Algorithmic Model] somewhere,
for the purposes of passing Usage Info or Usage In parameters,
even a floating, unattached .ami file would syntactically work as well,
as long as it is in the same directory.

Item b) for [External Model] is a revision of your item b) to be
precise and to give all conditions testable by the parser (reason for
adding the AMI_Resolve_Exits True)  The parser does not check
the AMI_Resolve flow.  So I think your b) needs to be rewritten.

Bob

From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx> 
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Tuesday, September 03, 2013 3:39 PM
To: Bob Ross; ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded

Bob,

I don't think we are in disagreement, it is just the wording.
Part of the problem is that in this email you are not referring
to my latest proposed text, so I would like you to comment with
respect to that text.

But when I refer to .ami files, I mean "any .ami file", even though
I didn't use the "any" word.  I just called them "a .ami file"
which in my mind is the same as "any .amy file", but I don't
mind making that change.

Please comment on the latest proposed text I sent out after
the meeting.

Thanks,

Arpad
=====================================================================

From: Bob Ross [mailto:bob@xxxxxxxxxxxxx]
Sent: Tuesday, September 03, 2013 5:20 PM
To: Muranyi, Arpad; ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx>
Subject: RE: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded

Arpad:

We have a misunderstanding and disagreement for pg. 99 and 100 because in a) 
the parameter
may reference Usage In and Usage Info parameters in ANY .ami file - just like 
[External Circuit].
The intended revision should state:

a) An [External Mode] parameter may reference Usage In, Usage Info parameters 
in any .ami file.

b) An [External Model parameter may also reference Usage Dep parameters under 
the following
conditions: the top-level [Model] keyword must contain [Algorithmic Model], its 
Executable
calls the same .ami file and its corresponding executable model, the .ami file 
must contain
the parameter AMI_Resolve_Exists set to True, and the parameter value shall be 
resolved
by calling the AMI_Resolve Function (see section 10.2.3).

In pages 119 and 120:

Insert "any

a) An [External Circuit] parameter may only reference Usage In, Usage Info 
parameters in any .ami file.





From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx> 
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Tuesday, September 03, 2013 1:57 PM
To: ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded

Radek,

In light of the discussion in the ATM meeting today I revised
the words to go along with the second option's rules you
proposed.  How does this sound to you:

For pg. 99 and 100:
===================

When the extension of the external parameter's file name ends with .ami:

a) If an [External Model] keyword is located under a [Model] keyword which also 
contains an [Algorithmic Model] keyword, and the [External Model]'s parameter 
and the [Algorithmic Model] keyword point to the same .ami file, the [External 
Model] parameter may reference Usage In, Usage Info, or Usage Dep parameters.  
Otherwise only references to Usage In or Usage Info parameters are allowed.

b) Before Usage Dep parameters are passed to [External Model]s, their value 
must be resolved by calling the AMI_Resolve function of the executable model 
pointed to by the [Algorithmic Model] keyword (see Section 10.2.3).

When the extension of the external parameter's file name does not end with 
".ami":

a) The parameter tree must not contain the Reserved_Parameters branch but must 
contain the Model_Specific branch.

b) Only Usage Info parameters are allowed in the parameter file.


For pg. 119 and 120:
====================

When the extension of the external parameter's file name ends with .ami:

a) An [External Circuit] parameter may only reference Usage In, Usage Info 
parameters in .ami file.

When the extension of the external parameter's file name does not end with 
".ami":

a) The parameter tree must not contain the Reserved_Parameters branch but must 
contain the Model_Specific branch.

b) Only Usage Info parameters are allowed in the parameter file.


Thanks,

Arpad
================================================================

Other related posts:

  1. Home
  2. ibis-macro
  3. Archive
  4. 09-2013