I wish I could make all my software work just by wanting it to fail! :) Cheers, Dave
> On Feb 2, 2021, at 12:27, Guillermo Gancio <[email protected]> wrote: > > Hi Adam, > > Thanks for you answer, and as Murphy said, if it can fail, it > will....but in this case it didn't fail... > I was preparing the files from scratch to attach them correctly and to > copy the error, but in the process it worked ok, I mean, I open the > m2016a version in the m2018a, updated with "update_casper_blocks", > save the m2018a model, close everything, reopen the recently updated > and saved m2018a model, and it compiled ok... > I guess that with the several tests that I did I have some mix of versions.... > > If I find what the actual problem was I'll let you know. > > Thanks! > > > > El mar, 2 feb 2021 a las 3:05, Adam Isaacson (<[email protected]>) escribió: >> >> Hi Guillermo, >> >> Interesting. Please send me the following: >> >> 1) screen capture of the errors you get before you do "update_casper_blocks". >> 2) please attach your R2016a slx file >> 3) please attach your new saved R2018a slx file. >> >> I will then investigate and get back to you. >> >> Kind regards, >> >> Adam >> >> >> On Tue, 02 Feb 2021, 2:59 AM Guillermo Gancio, <[email protected]> wrote: >>> >>> Dearest CasperAmigos, >>> >>> I'm having the following issue, I'm trying to compile a simulink >>> design from m2016a into a m2018a, if I try to compile it directly I >>> got several errors, but if I do "update_casper_blocks(bdroot)" the >>> model compiles ok.. >>> >>> Now if I save the updated model and reopen it again, I have to do >>> "update_casper_blocks(bdroot)" again, what I mean is that every time >>> that the model is opened, I have to update it with >>> update_casper.--.... >>> >>> I'm not sure if this is the normal procedure, or if there is a way to >>> save the model in order to avoid the "update....." every time. >>> >>> Cheers. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "[email protected]" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CA%2BEePfQc_e33QqiK2MZvLV_wjYaRGCNkOioN%3DJAnKJKgXBH3xw%40mail.gmail.com. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "[email protected]" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnHQU_CE%3D0qRgs7vQwEBKbLqWCQdDfyje149C1zK0cVptQ%40mail.gmail.com. > > > > -- > Instituto Argentino de Radioastronomia > [Argentine Institute of Radioastronomy] > > Guillermo M. Gancio > Responsable Área Observatorio > [Head of Observatory] > > Tel: (0054-0221) 482-4903 Int: 106 > Mail laboral [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "[email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CA%2BEePfSPOvCEF9sbKpk66%3DUKwmeBYnApSOtp-UVHBpCvzzhMrA%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/BFDD1A90-18F8-410A-BF43-0E46EA8571A8%40berkeley.edu.
