Hi All, Thanks to all who contributed their thoughts to best describe the agreed details. Once the discussion is finished I will make the changes to the draft and have it ready for the ATM meeting next Tuesday. Thanks, Radek From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Thursday, September 05, 2013 10:45 AM To: ibis-macro@xxxxxxxxxxxxx Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded Bob, Thanks for your comments and suggestions. I like your corrections, and either option at the end is fine with me. Radek, Could you incorporate these words with Bob's changes into BIRD 155? Let me know if you need help with it. Thanks, Arpad ========================================================== From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx> [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross Sent: Thursday, September 05, 2013 11:51 AM To: Muranyi, Arpad; ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx> Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded Arpad: I see what you are trying to do: 1. Define parameter tree file rules for files without the .ami extension (however the same rules are given four times), 2. Then define rules inclusive of all parameter files with or WITHOUT the .ami extension (only item a) supports both cases, items b) and c) are for .ami files only). I would make the following change: Change The following rules apply to parameter trees located in parameter files whose file name doesn't end with .ami: To The following rules apply to parameter trees located in parameter files whose file name extension is not .ami: Since the file format is <flile_name>.<extension> according to section 10.1 where a .ami file extension is defined under "Parameter_File". The second rules items a) and b) should be made clearer concerning extensions: Change a) Usage Info parameters may be referenced in any external parameter file. b) Usage In parameters may be referenced in any parameter file whose file name ends with .ami. To a) Usage Info parameters may be referenced in any external parameter file with or without the .ami extension b) Usage In parameters may be referenced in any parameter file whose file name extension is .ami. The Usage Dep rule needs to have the singular/plural tenses corrected from If all of these conditions are satisfied, the EDA tool must execute the AMI_Resolve function in the executable model defined by the [Algorithmic Model] keyword to resolve the value of any Usage Dep parameters before passing the value of such parameters to the [External Model] (see Section 10.2.3). To If all of these conditions are satisfied, the EDA tool must execute the AMI_Resolve function in the executable model defined by the [Algorithmic Model] keyword to resolve the value of any Usage Dep parameter before passing its value to the [External Model] (see Section 10.2.3). Or: If all of these conditions are satisfied, the EDA tool must execute the AMI_Resolve function in the executable model defined by the [Algorithmic Model] keyword to resolve the values of all Usage Dep parameters before passing their values to the [External Model] (see Section 10.2.3). Bob From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx> [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Wednesday, September 04, 2013 10:53 PM To: ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx> Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded Bob, I rewrote these rules according to Bob's suggestions. There is still some duplication which could be removed, but then the question becomes where these rules would be best located in the spec. I think for now we should just put these in the same four locations where the corresponding rules are currently. We can deal with making the spec more concise later... For pg. 99 and 100: =================== The following rules apply to parameter trees located in parameter files whose file name doesn't end with .ami: a) The parameter tree must not contain the Reserved_Parameters branch. b) The parameter tree must contain the Model_Specific branch. c) The parameter tree may only contain Usage Info parameters. The following rules must be observed when [External Model] parameters reference parameters located in external parameter files: a) Usage Info parameters may be referenced in any external parameter file. b) Usage In parameters may be referenced in any parameter file whose file name ends with .ami. c) Usage Dep parameters may also be referenced in a .ami parameter file under the following conditions: - the [External Model] keyword is located under a [Model] keyword which also contains an [Algorithmic Model] keyword, - the [External Model]'s parameter and the [Algorithmic Model] keyword point to the same .ami file, - the .ami parameter file contains the parameter AMI_Resolve_Exists with a value of True. If all of these conditions are satisfied, the EDA tool must execute the AMI_Resolve function in the executable model defined by the [Algorithmic Model] keyword to resolve the value of any Usage Dep parameters before passing the value of such parameters to the [External Model] (see Section 10.2.3). For pg. 119 and 120: ==================== The following rules apply to parameter trees located in parameter files whose file name doesn't end with .ami: a) The parameter tree must not contain the Reserved_Parameters branch. b) The parameter tree must contain the Model_Specific branch. c) The parameter tree may only contain Usage Info parameters. The following rules must be observed when [External Circuit] parameters reference parameters located in external parameter files: a) Usage Info parameters may be referenced in any external parameter file. b) Usage In parameters may be referenced in any parameter file whose file name ends with .ami. Questions, comments are welcome from anyone... Thanks, Arpad ==============================================================================