Analytica 5 Video Short: Operator + used to concatenate text

Share Now

This is the second installment in the Analytica 5 Video shorts series — short (under 5 minutes) videos showcasing an individual topic or feature in Analytica. The series primarily focuses on features that are New in Analytica 5.0

Since I'm putting this one out there a few hours before the 5.0 release is official, I thought it fitting to cover an error message that you might encounter right away, when you load your legacy model you created in 4.6 into 5.0. As the video shows, it is easy to deal with, so this is a “don't panic” message. Overall, you should be pretty confident in 5.0's backward compatibility (the ability of 5.0 to run 4.6 models), which is extremely high. In a survey of 5.0 users (look for that blog post within a few days), 100% of the responders stated that they encountered no problems running their 4.6 models in Analytica 5.0. Nevertheless, I have seen this particular error appear in several cases, and hence decided to show you what to do in a quick 5 minute video. 


Share Now

Leave a Comment

avatar
  Subscribe  
Notify of
Lonnie Chrisman
Guest
lchrisman

When I made the video, I made a comment “in the several models I studied, that didn’t actually happen” — where “that” referred to the model relying on the result of text+ text. I encountered one where it did matter — the PO5 benchmark model in the “Faster evaluation in Analytica 5.0” blog posting. That model dates back to Analytica 3.1, and used + for text concatenation in many places for real. I ended up having to go through that model and change those in about a dozen places. However, because the error pointed me directly to the rogue Definition,… Read more »

Lonnie Chrisman
Guest
lchrisman

Once other thing to be aware of is that after you set the “x+y returns NAN for Text” preference, you don’t want to load the model into 4.6 and then save it from 4.6, since that would reset the preference for you. Analytica 4.6 doesn’t know about this preference, plus Analytica 5.0 sets it by default for a legacy model that had been last saved from 4.6.