Issue: Negative Binomial Models with Offsets.

Welcome to the forum for MLwiN users. Feel free to post your question about MLwiN software here. The Centre for Multilevel Modelling take no responsibility for the accuracy of these posts, we are unable to monitor them closely. Do go ahead and post your question and thank you in advance if you find the time to post any answers!

Remember to check out our extensive software FAQs which may answer your question: http://www.bristol.ac.uk/cmm/software/s ... port-faqs/
Post Reply
dianecrowe
Posts: 1
Joined: Fri Jun 19, 2020 2:09 pm

Issue: Negative Binomial Models with Offsets.

Post by dianecrowe »

Hi all, im a new. Nice to meet u.

And second,

I'm trying to run two-level negative binomial models. While there is no problem without offsets, when I include offsets MLwiN falls over immediately with the following error message:

“error while obeying batch file C:\Program Files (x86)\MLwiNv2.22\discrete\pre at line number 65:
calc ‘F~(H)’=expo(‘H’)
23171 numeric errors in calculate command, first 20 affected entries listed.
Affected entries replaced with system missing."

I'm working in a secure data lab and was running negative binomial models with offsets there two weeks ago without any problem.
This makes me think the issue could be the environment and the owners of the lab, who contract their secure service from someone else, are checking with their supplier if there have been any hardware/software changes.
In the meantime, I thought I would just check with yourselves in case you can think of anything obvious, though please don't spend too long on it at this stage as it could be the environment.

Tks in advance./

ChrisCharlton
Posts: 1174
Joined: Mon Oct 19, 2009 10:34 am

Re: Issue: Negative Binomial Models with Offsets.

Post by ChrisCharlton »

MLwiN v2.22 is a rather old version (December 2010), so we would need to know that the same problem happens for you in the most recent version before we can look into this. If the same model was working before however then it's likely that something external has changed. Are you using the same data as the previously working version?

Post Reply