This is related with #74.
While INLA is only a package suggested for testing and simulation of spatial fields for the metagene class and it is not typically installed by most users, it is necessary for Travis CI to fully test every release (every commit, really). It complicates the Travis configuration enormously, it extends significantly the set-up time, needs to compile in advance several heavy packages (Matrix, shiny) and needs to install INLA itself, which is quite heavy.
Furthermore, dependencies change regularly with every new version of any of the involved packages, and they break the Travis CI testing process. Takes a lot of time to debug, and all that has nothing to do with breedR.
I really need to test in alternative ways and simulate fields with package fields, or whatever.
This is related with #74. While INLA is only a package suggested for testing and simulation of spatial fields for the metagene class and it is not typically installed by most users, it is necessary for Travis CI to fully test every release (every commit, really). It complicates the Travis configuration enormously, it extends significantly the set-up time, needs to compile in advance several heavy packages (Matrix, shiny) and needs to install INLA itself, which is quite heavy. Furthermore, dependencies change regularly with every new version of any of the involved packages, and they break the Travis CI testing process. Takes a lot of time to debug, and all that has nothing to do with breedR.
I really need to test in alternative ways and simulate fields with package
fields, or whatever.