isis-group / vast Goto Github PK
View Code? Open in Web Editor NEWisis based medical image viewer
License: GNU General Public License v3.0
vast's People
Contributors
Stargazers
Watchers
vast's Issues
Core dump when upper threshold slider on minimum
When I open an image as "zmap" and I pull down the "upper threshold" slider to the very end of the scale vast core dumps with this message:
michael@meiner ~ % vast -zmap analysis/MNI_3mm_brain_mask.nii.gz
ASSERT failure in QVector<T>::operator[]: "index out of range", file /usr/include/qt4/QtCore/qvector.h, line 347
Correct offset implementation
When changing brightness and contrast of the image the offset value is not treated as it should be.
Wishlist: stats image handling/naming
Statistics images are currently referred to as 'zmap'. It might be more appropriate to call them 'stats' or something similar as they seem to be the only non-structural overlay category (e.g. when visualizing classification accurracy, or other error maps). Moreover, it would be nice if it would be possible to change the type of an image (structural vs. stats) after it has been loaded.
Can't build vast with BOOST 1.46
I just built isis with BOOST 1.46 and now tried to built vast on the same system. It fails like this:
[ 26%] Building CXX object CMakeFiles/vast.dir/viewer/qviewercore.cpp.o
/usr/lib/ccache/c++ -D_VAST_VERSION_MAJOR=0 -D_VAST_VERSION_MINOR=4 -D_VAST_VERSION_PATCH=0 -D_ENABLE_LOG=1 -D_ENABLE_DEBUG=0 -D_ENABLE_DEV=1 -DQT_UITOOLS_LIB -DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DVAST_RCS_REVISION="Debian-0.4.0~beta-1" -ftemplate-depth-100 -Wextra -Wall -Wfatal-errors -fopenmp -I/home/michael/debian/lipsia/vast/widgets -I/home/michael/debian/lipsia/vast/obj-i486-linux-gnu -I/usr/include/isis -I/usr/include/qt4 -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtWebKit -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/home/michael/debian/lipsia/vast/QImageWidget -I/home/michael/debian/lipsia/vast/viewer -o CMakeFiles/vast.dir/viewer/qviewercore.cpp.o -c /home/michael/debian/lipsia/vast/viewer/qviewercore.cpp
In file included from /usr/include/isis/DataStorage/../CoreUtils/log.hpp:18:0,
from /usr/include/isis/DataStorage/../CoreUtils/common.hpp:30,
from /usr/include/isis/DataStorage/../CoreUtils/vector.hpp:20,
from /usr/include/isis/DataStorage/../CoreUtils/types.hpp:17,
from /usr/include/isis/DataStorage/../CoreUtils/value_base.hpp:20,
from /usr/include/isis/DataStorage/valuearray_base.hpp:22,
from /usr/include/isis/DataStorage/valuearray.hpp:25,
from /usr/include/isis/DataStorage/chunk.hpp:16,
from /home/michael/debian/lipsia/vast/viewer/common.hpp:32,
from /home/michael/debian/lipsia/vast/viewer/widgetinterface.h:32,
from /home/michael/debian/lipsia/vast/viewer/widgetloader.hpp:32,
from /home/michael/debian/lipsia/vast/viewer/viewercorebase.hpp:32,
from /home/michael/debian/lipsia/vast/viewer/qviewercore.hpp:32,
from /home/michael/debian/lipsia/vast/viewer/qviewercore.cpp:28:
/usr/include/isis/DataStorage/../CoreUtils/message.hpp:21:0: warning: "BOOST_FILESYSTEM_VERSION" redefined [enabled by default]
/usr/include/boost/filesystem.hpp:24:0: note: this is the location of the previous definition
In file included from /usr/include/boost/filesystem/path.hpp:28:0,
from /usr/include/isis/DataStorage/../CoreUtils/message.hpp:22,
from /usr/include/isis/DataStorage/../CoreUtils/log.hpp:18,
from /usr/include/isis/DataStorage/../CoreUtils/common.hpp:30,
from /usr/include/isis/DataStorage/../CoreUtils/vector.hpp:20,
from /usr/include/isis/DataStorage/../CoreUtils/types.hpp:17,
from /usr/include/isis/DataStorage/../CoreUtils/value_base.hpp:20,
from /usr/include/isis/DataStorage/valuearray_base.hpp:22,
from /usr/include/isis/DataStorage/valuearray.hpp:25,
from /usr/include/isis/DataStorage/chunk.hpp:16,
from /home/michael/debian/lipsia/vast/viewer/common.hpp:32,
from /home/michael/debian/lipsia/vast/viewer/widgetinterface.h:32,
from /home/michael/debian/lipsia/vast/viewer/widgetloader.hpp:32,
from /home/michael/debian/lipsia/vast/viewer/viewercorebase.hpp:32,
from /home/michael/debian/lipsia/vast/viewer/qviewercore.hpp:32,
from /home/michael/debian/lipsia/vast/viewer/qviewercore.cpp:28:
/usr/include/boost/filesystem/v2/path.hpp:1542:24: error: ‘wpath’ is already declared in this scope
compilation terminated due to -Wfatal-errors.
This seems to be related to #define BOOST_FILESYSTEM_VERSION 2 in ISIS (see http://markmail.org/message/q7f3qdozp5cekjd7#query:+page:1+mid:q7f3qdozp5cekjd7+state:results for a similar problem). How can I build VAST so it would work with ISIS? Does it need a more recent BOOST version. If so, cmake should probably mention this.
Please push consistent tags for all versions
Hi,
The last tag in the repo is for version 0.2.5, but it seems that 0.2.6 followed it and now 0.3 is current. Please push the remaining tags.
Moreover, until 0.1.7-0 tag were prefixed with 'v', all following tags didn't have this prefix. It would be nice to have on consistent prefix for all release tags, e.g. 'release/0.3.0' so they can be easily identified among all other possibly existing tags.
Thanks
Contact address field in about dialog is empty
As of current master.
Please support lazy data loading
When I open a 4D fMRI image (gzipped nifti) all data seems to be loaded into memory before anything is displayed. Even if I never intent to look at anything but a few volumes, or a single voxel's timeseries. This causes significant startup delays even for modestly sized dataset, and make it a challenge to open large highres dataset at all (e.g. 2-3GB timeseries).
It would be great if data is only loaded when it is needed. For example, only the first volume at startup, or a column/row for profile plotting.
Core dump when "show spectrum" in profile plotter
Load any image, open profile plotter, click "show spectrum" -> core dump
michael@meiner ~/analysis % vast -in raiders_epi_template.nii.gz
vast: /usr/include/isis/DataStorage/../CoreUtils/generic_type.hpp:43: T& isis::util::_internal::GenericValue::m_cast_to() [with T = isis::data::ValuePtr<short int>]: Assertion `getTypeID() == T::staticID' failed.
Do not set -Wfatal-errors unconditionally
This causes the build to break unconditionally whenever a newer compiler with more fancy warning is used. To avoid this breakage everybody has to patch the code now.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.