How about this: For (pg. 99 and 100): ===================== When the extension of the external parameter's file name ends with .ami: a) an [External Model] parameter may only reference an .ami file if the [Model] which contains the [External Model] keyword also contains an [Algorithmic Model] keyword pointing to the same .ami file b) only Usage In, Usage Info or Usage Dep parameters are allowed, c) if a parameter is of Usage Dep then its value, prior passing it into the external model, must be resolved by calling the AMI_Resolve function (see Section 10.2.3) of the DLL pointed by the [Algorithmic Model] keyword. 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 is allowed For (pg. 119 and 120): ===================== When the extension of the external parameter's file name ends with .ami: a) only Usage In, Usage Info parameters are allowed, 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 is allowed Thanks, Arpad ============================= From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Tuesday, September 03, 2013 1:00 PM To: ibis-macro@xxxxxxxxxxxxx Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded Yes, I was referring to the third option. I agree that [External Circuit] still needs to be fixed. I am working on that. But I have a question. Should we just disallow .ami file extensions for [External Circuit] completely, or should we allow .ami file extensions, but forbid using the Usage Dep parameters in it? Thanks, Arpad =============================================================== From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx> [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of radek_biernacki@xxxxxxxxxxx<mailto:radek_biernacki@xxxxxxxxxxx> Sent: Tuesday, September 03, 2013 12:57 PM To: Muranyi, Arpad; ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx> Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded Hi Arpad, I suppose you refer to the third option. Combining a) and b) is fine, yet a reference to an .ami within [External Circuit] still needs to be clearly disallowed. Radek 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 10:49 AM To: ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx> Subject: [ibis-macro] Re: revision of BIRD155.1 - draft 6 uploaded Radek, I like the second option in red at the end. However, I think the a) and b) could be combined. What do you think about doing this: a) an [External Model] parameter may only reference an .ami file if the [Model] which contains the [External Model] keyword also contains an [Algorithmic Model] keyword pointing to the same .ami file b) only Usage In, Usage Info or Usage Dep parameters are allowed, c) if a parameter is of Usage Dep then its value, prior passing it into the external model, must be resolved by calling the AMI_Resolve function (see Section 10.2.3) of the DLL pointed by the [Algorithmic Model] keyword. Thanks, Arpad ==========