Back to the main page.
Bug 1457 - OpenMEEG should come packaged with FieldTrip
| Status | CLOSED WORKSFORME |
| Reported | 2012-05-07 11:53:00 +0200 |
| Modified | 2019-08-10 12:30:55 +0200 |
| Product: | FieldTrip |
| Component: | forward |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | All |
| Importance: | P3 normal |
| Assigned to: | |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | 1441 |
| See also: |
Boris Reuderink - 2012-05-07 11:53:07 +0200
In the context of bug1441, Robert and I discussed the installation of OpenMEEG. We were both expecting that $FT/external/openmeeg would contain all the files needed to use OpenMEEG, but it appears that a separate install of OpenMEEG is necessary. Is there a good reason not to? I checked the file sizes, and the current release is well below 10 MB (compressed) @Robert, could you indicate which project in $FT/external we could use as an example for wrapping binary executables on different platforms?
Cristiano Micheli - 2012-08-21 16:23:31 +0200
(In reply to comment #0) Hi, I checked the forge site of OpenMEEG: https://gforge.inria.fr/frs/?group_id=435 and it looks like the whole set of executables is now well above 10MB. Are we really sure we want to have it packaged in the FT release? I would say that it makes more sense to add a warning in ft_hastoolbox('openmeeg') which points out to the user which wiki page to look at, in order to proceed to the manual installation. What do you think? Best, Cristiano
Boris Reuderink - 2012-08-22 16:50:18 +0200
Sounds like a valid option to me as well. But I got the feeling that it is more in the philosophy of FieldTrip to provide the user the service of the availability of a comprehensive set of tools; so perhaps it should be included after all. What do you think Robert?
Robert Oostenveld - 2012-08-22 22:47:18 +0200
Ideally we would indeed package it in the lease zit, but 10 mb or more per platform (there are three) gets quite heavy. Idem for simbio and fns. But I think we should, besides pointing to the official release site, provide our own tested version, e.g. as zip from our own FTP. The zip content should be checked and should be known to work. Ideally it is the same as the official release, but if needed we can repackage for easier deployment. E.g. ftp.fcdonders.nl/pub/fieldtrip/external/openmeeg/windows.zip ftp.fcdonders.nl/pub/fieldtrip/external/openmeeg/linux.zip ftp.fcdonders.nl/pub/fieldtrip/external/openmeeg/osx.zip And idem for fns, simbio and even perhaps for dipoli. If thre is a consistent check on the binary executable being present at the expected locatio, there can also be a consistent information message to the users with download and install instructions for the executables. The wrapper/glue code should remain in the regular fieldtrip.zip release.
Boris Reuderink - 2012-08-23 10:36:40 +0200
Ok, that sounds like a nice compromise. I wonder though where these wrappers should be maintained? If it is in the main SVN, it should be excluded from the daily FieldTrip release.
Boris Reuderink - 2012-10-10 14:15:25 +0200
Moved bugs from Christiano Michelli to joint development user.
Robert Oostenveld - 2013-01-24 12:29:06 +0100
I changed a bunch of bugs that were assigned to fieldtrip-bugs from ASSIGNED into NEW, since nobody is now explicitly working on them.
Robert Oostenveld - 2015-02-11 09:48:49 +0100
installation instructions are provided at http://fieldtrip.fcdonders.nl/faq/how_can_i_use_openmeeg_for_forward_modelling which is the first hit in google if I search for "fieldtrip openmeeg". I don't think we can make it much easier. Providing binaries for all platform inside the fieldtrip zip file does not sound like a good plan to me.