I've been using MOFA2 on a couple of Ubuntu machines. One of them is Ubuntu 20, the other was Ubuntu 18.
Other than the Ubuntu version, their setup was identical:
R: 4.2.2
MOFA2: 1.8.0
mofapy2: 0.6.7
Running MOFA (with basilisk) on the Ubuntu 18 machine would result in an object has no attribute run.entry_point error. In contrast, the Ubuntu 20 machine ran MOFA without any problems.
Furthermore: I upgraded the Ubuntu 18 machine to Ubuntu 20 and the error disappeared!
I was surprised to see Basilisk/MOFA2 interact with the OS version in this way. This may be a Basilisk issue, rather than a MOFA2 issue. In any case, I didn't see this issue mentioned anywhere online, so I thought I would post something here.
This is more like a PSA than a bug.
I've been using MOFA2 on a couple of Ubuntu machines. One of them is Ubuntu 20, the other was Ubuntu 18.
Other than the Ubuntu version, their setup was identical:
Running MOFA (with basilisk) on the Ubuntu 18 machine would result in an
object has no attribute run.entry_pointerror. In contrast, the Ubuntu 20 machine ran MOFA without any problems.Furthermore: I upgraded the Ubuntu 18 machine to Ubuntu 20 and the error disappeared!
I was surprised to see Basilisk/MOFA2 interact with the OS version in this way. This may be a Basilisk issue, rather than a MOFA2 issue. In any case, I didn't see this issue mentioned anywhere online, so I thought I would post something here.