some questions after using abConvertComponentParams.il to do schematic porting

That's a pretty old version - not sure where you got it from (can you let me know, so I can update the reference if that makes sense)? The version in this post is pretty much the latest (there's a slightly newer version, but it only fixes a minor issue; I may update that post at some point). That's version 1.13 from 2019 rather than 1.7 from 2005.

Some answers for your questions:

1. Either use %N (rather than %n) in the sprintf: sprintf(nil "%N" evalstring(val)*2) (which gives you exponential format if that makes more sense) or use something like aelSuffixNotation(evalstring(val)*2) or maybe aelSuffixNotation(cdfParseFloatString(val)*2) .
2. This is supported in a newer version than that which you're using - you'll see from the comments at the top that you can now specify the new parameter name in the params map as nil and that causes the property to be deleted
3. There's nothing in the code to do this - you'd have to write some code to search for any instances of noConn and delete them - but it's slightly tricky because it would need a check to see if the noConn is on top of a wire or a pin. I don't have code to do this right now
4. The newer version has a postProcess option that could be used to write code to add a wire stub and label. Again, hard to write something without details on precisely what is needed (I have some other code for wiring up when symbols have changed, but it very much needs tuning to a particular need). 

Perhaps you could contact customer support? You can ask the AE to contact me and I can certainly look at this with some real examples and make abConvertComponentParams better at handling this? That said, it's unlikely to be in the next couple of weeks as I'm busy this week and on vacation next week...

Andrew

That's a pretty old version - not sure where you got it from (can you let me know, so I can update the reference if that makes sense)? The version in this post is pretty much the latest (there's a slightly newer version, but it only fixes a minor issue; I may update that post at some point). That's version 1.13 from 2019 rather than 1.7 from 2005.

Some answers for your questions:

1. Either use %N (rather than %n) in the sprintf: sprintf(nil "%N" evalstring(val)*2) (which gives you exponential format if that makes more sense) or use something like aelSuffixNotation(evalstring(val)*2) or maybe aelSuffixNotation(cdfParseFloatString(val)*2) .
2. This is supported in a newer version than that which you're using - you'll see from the comments at the top that you can now specify the new parameter name in the params map as nil and that causes the property to be deleted
3. There's nothing in the code to do this - you'd have to write some code to search for any instances of noConn and delete them - but it's slightly tricky because it would need a check to see if the noConn is on top of a wire or a pin. I don't have code to do this right now
4. The newer version has a postProcess option that could be used to write code to add a wire stub and label. Again, hard to write something without details on precisely what is needed (I have some other code for wiring up when symbols have changed, but it very much needs tuning to a particular need). 

Perhaps you could contact customer support? You can ask the AE to contact me and I can certainly look at this with some real examples and make abConvertComponentParams better at handling this? That said, it's unlikely to be in the next couple of weeks as I'm busy this week and on vacation next week...

Andrew

Hi Andrew,

I found the old version  here.

1. works well if I changed to %N.

2. newer version I can delete the user property. one thing after I tried is: in PDK_A, "m" is a string but in PDK_B "m" is int type. can you give an example how to do the mapping in this situation ? I wrote ("m“ ”m“ int) in the Params section. It didn't work.

3. I just want to know is it the script support that poring A device in PDK_A to nil in PDK_B, if so, I think it might be use to delete something.

4.  you mean using something like "schHiCreateWire" in the postProcess ?

I will talk with AE if he come next-time. thanks for your help!

Answering your questions:

2. You'd need to create a function to convert the string parameter to an integer, and also specify the type as the fourth entry in the params element (see the comments at the top). So for example:

procedure(RINGAMPstringToInt(inst paramName val)
    atoi(val)
)

and then in the params section, you'd have:

   ("m" "m" RINGAMPstringToInt "int") ; fourth element is the type of the new property - the default is the same as the old property.

3. No, there's nothing in the code to delete an instance right now. Mapping to nil just wouldn't work.

4. Yes - something like that.

Andrew

add one questions:

if the device W & L parameter is something like "Ppar("nw")" "Ppar("nl")", how to write the mapping function ?

What needs mapping here? Use of pPar() is a design decision - it's unclear what you're expecting to be mapped.

Andrew