how to re-evaluate the pcell submaster

Why would you want the Python code to run again? If you are placing the exact same parameters of another instance, Virtuoso runs much faster because it does not have to re-evaluate the pcell. In this case it uses a common "sub-master" for that pcell. Say for example you have a complex inverter pcell that takes 1 second to evaluate the Python code that constructs it. If you place the same inverter size 100 times on your design, re-running your Python code every time will take 100 seconds. If the code is only evaluated once and the sub-master is rereferenced for sub-sequent placments, your total evaluation time is only 1 second.

Even if the Express Pcell caching worked with your pcells, this would only make your problem worse. The way the Express Pcell feature works for Skill pcells is that it saves your evaluated sub-master to disk, so the next time you open your design the code isn't run at all. The saved pcell that was evaluated in the last session is read in from disk. In this case, once the cache was built, assuming no new pcells are added, there would be no Skill code run at all. It sounds like your goal is to run the code more than necessary.

Derek

Why would you want the Python code to run again? If you are placing the exact same parameters of another instance, Virtuoso runs much faster because it does not have to re-evaluate the pcell. In this case it uses a common "sub-master" for that pcell. Say for example you have a complex inverter pcell that takes 1 second to evaluate the Python code that constructs it. If you place the same inverter size 100 times on your design, re-running your Python code every time will take 100 seconds. If the code is only evaluated once and the sub-master is rereferenced for sub-sequent placments, your total evaluation time is only 1 second.

Even if the Express Pcell caching worked with your pcells, this would only make your problem worse. The way the Express Pcell feature works for Skill pcells is that it saves your evaluated sub-master to disk, so the next time you open your design the code isn't run at all. The saved pcell that was evaluated in the last session is read in from disk. In this case, once the cache was built, assuming no new pcells are added, there would be no Skill code run at all. It sounds like your goal is to run the code more than necessary.

Derek