Technology File Modification Issues / Encounter Prevent ViaCell Generation

We are using the IBM cmrf8sf PDK. We have designed a standard cell library, but we were not able to import this into Abstract Generator because it lacked required metal spacing. To remedy this, we dumped the cmrf8sf techfile, added the required spacings, compiled it and attached to a library copy, and were able to generate abstracts. However, after the modifications, DRC will not pass on any of our previously DRC-clean standard cells. By attaching the original techfile, DRC was fine. Investigating this further, we dumped the original techfile and tried to create a library based on it (only dumped, no modifications). The compile was fine, but any libraries attached to it would exhibit the same DRC errors that our modified library would. From this, it seems that there is either an issue occuring when dumping techfiles or compiling ASCII techfiles so modifying techfiles and still passing DRC is not possible. Why is this happening?

Since we can't modify the techfile, we are also having to do some time-extensive workarounds to use Encounter. During the power planning step of Encounter, array of vias (viacells) will be created for the design. When the design is exported using the oaOut command, these viacells will be added to the technology library. However, we are not able to modify our original techfile, as previously mentioned, so we use the -copyTechFromRefLib command so the viacells are added to a modified techfile in the specified library. We then have to flatten all of the viacells and copy the layout to a library with the original cmrf8sf techfile attached, which is quite annoying. Is there a way to force Encounter to use individual power planning vias instead of cells?

Thanks,

Brett