Forum Replies Created
-
AuthorPosts
-
rswatyParticipant
Thanks tons Katie! I appreciate it.
rswatyParticipantThanks Leonardo! Exactly what I needed to know.
Randy
rswatyParticipantThanks for this discussion. I had several students run into this error. Glad to have a solution posted here.
rswatyParticipantHi folks,
I am running Ubuntu on a machine and wondered how the ST-Sim development for Linux is going.Thanks,
RandyrswatyParticipantFirst where is Path? It’s required to do the transfer from VDDT to ST-Sim but I can’t find it on your web site. For now Jim Smith is doing the VDDT-Path step.
Second, I cannot get the “State Class” import to work. I am sure it has to do with how I am typing in the formula that is on the tutorial. Exactly what should it look like in Excel? I get a “#value” error in Excel when I use anything like what is in the tutorial (without the “”).
Thanks!
RandyrswatyParticipantThanks Colin-can tell you’ve been doing this for a while. Very helpful!
Randy
rswatyParticipantHi Megan,
Those boxes just change the display so you are safe to check or un-check at will.Randy
July 15, 2010 at 3:05 pm in reply to: making transition groups same between VDDT models before import to Path #1736rswatyParticipantHi Leonardo and Colin,
Thanks for the help with the transition groups and types. I used the process that Colin described and got a successful import into Path with the “Use VDDT definitions…” unchecked. If I try to import with the box checked I get errors which I suspect are due to the fact that there are different codes for the same transition type from model to model.Is it OK to have different codes in different models for the same transition if I plan to move the VDDT models to Telsa? If that is the case it sounds like I’ll be sending you a database Leonardo!
Randy
-
AuthorPosts