Fangyi, The standard says that Use_Init_Output is of Usage "Info". Info means that is not an input to the DLL, but is information on how a DLL operates, and what is can do, and how it expects the EDA tool to use it. I understand why this is not clear in the current 5.0 document. It is my intent that the modification to the 5.0 documentation that I am working on will significantly clarify how all this is supposed to work. My team is thoroughly reviewing my changes. I plan to incorporate a new section on the "Reference Flows" that Arpad has been working so diligently on. I believe that next week Vladimir is going to give an "Admittance" presentation. I will plan on introducing the updated spec at the meeting after. Walter Walter Katz 303.449-2308 Mobile 720.333-1107 wkatz@xxxxxxxxxx www.sisoft.com -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]On Behalf Of fangyi_rao@xxxxxxxxxxx Sent: Wednesday, October 07, 2009 7:42 PM To: ibis-macro@xxxxxxxxxxxxx Subject: [ibis-macro] modifiability of AMI parameters Hi, All; If a parameter is of Value format and its value is specified in the .ami file by model vendor, can EDA tools or model user modify this value? For example, does the standard intend to let model implement two behaviors for Use_Init_Output=true and false, and allow EDA tools to get different output from AMI_Init by passing Use_Init_Output=true or Use_Init_Output=false in the argument? Does a model have to support both scenarios? I think the standard is not clear about whether the parameters are used by models to instruct EDA tools how to call the model, or used by EDA tools to instruct the models how to function. Thanks, Fangyi