Activity for QSoas
-
Anonymous posted a comment on discussion General Discussion
That works. You can also use the latest github version of QSoas that fixes this: https://github.com/fourmond/QSoas However, be aware that there are some subtle changes in mruby 2.0 with respect to 1.4.1 that make QSoas crash if you're using apply-formula from inside a Ruby code (but I guess this will only affect a very very small minority of users).
-
Anonymous posted a comment on discussion General Discussion
Same here. Solved it by cloning the mruby project and rolling back to an old version (1.4.1) : git clone https://github.com/mruby/mruby.git cd mruby git checkout 023070a6396233974785a8fd5735b9380a884f27 make Then, in the qsoas-2.2.0 source directory, I indicated the mruby source location, in my case in ~/mruby : qmake MRUBY_DIR=~/mruby Then I succesfully recompiled QSoas : make clean && make
-
Anonymous posted a comment on discussion General Discussion
This appears to be due to some preprocessor macros that have been removed in mruby: src/mruby.cc:224:8: error: use of undeclared identifier 'GET_OPCODE' if(GET_OPCODE(c) == OP_SEND) { ^ src/mruby.cc:225:10: error: use of undeclared identifier 'GETARG_A' if(GETARG_A(c) == cur_top_self && GETARG_C(c) == 0) ^ src/mruby.cc:225:41: error: use of undeclared identifier 'GETARG_C' if(GETARG_A(c) == cur_top_self && GETARG_C(c) == 0) ^ src/mruby.cc:226:48: error: use of undeclared identifier 'GETARG_B' rv.insert(mrb_sym2name(mrb,...
-
Vincent Fourmond modified a comment on discussion General Discussion
You need to compile mruby from source. From compilation.txt: The mruby interpreter, from https://mruby.org/. The problem with mruby is QSoas will compile fine with version 1.3.0, but a bug in the mruby interpreter will cause a crash. You need a version between commits 7450a774 and afa5380, or posterior to 55431b4. Grab them from https://github.com/mruby/mruby Then use # MRUBY_DIR=/home/mine/mruby ./configure That should get you going.
-
You need to compile mruby from source. From compilation.txt: The mruby interpreter, from https://mruby.org/. The problem with mruby is QSoas will compile fine with version 1.3.0, but a bug inthe mruby interpreter will cause a crash. You need a versionbetween commits 7450a774 and afa5380, or posterior to 55431b4. Grab them from https://github.com/mruby/mruby Then use # MRUBY_DIR=/home/mine/mruby ./configure That should get you going.
-
You need to compile mruby from source. From compilation.txt: The mruby interpreter, from https://mruby.org/. The problem with mruby is QSoas will compile fine with version 1.3.0, but a bug inthe mruby interpreter will cause a crash. You need a versionbetween commits 7450a774 and afa5380, or posterior to 55431b4. Grab them from https://github.com/mruby/mruby Then use # MRUBY_DIR=/home/mine/mruby ./configure That should get you going.
-
You need to compile mruby from source. From compilation.txt: * The mruby interpreter, from https://mruby.org/. The problem with mruby is QSoas will compile fine with version 1.3.0, but a bug inthe mruby interpreter will cause a crash. You need a versionbetween commits 7450a774 and afa5380, or posterior to 55431b4. Grab them from https://github.com/mruby/mruby ``` Then use MRUBY_DIR=/home/mine/mruby ./configure ``` That should get you going.
-
Anonymous posted a comment on discussion General Discussion
so far the 2.2.0 source doesnt compile properly, I suspect because the qmake or configuration procedure doesnt find the right ruby library. BUT the 2.1 runs fine, except for the two last prompt lines that I understand as compilation errors: /bin/sh: 1: gdb: not found /bin/sh: 1: test: -gt: unexpected operator
-
Anonymous posted a comment on discussion General Discussion
that one weent away after install g++ there is another one which seems to originate from mruby not being found. I installed it, as well, but it seems that it wants something else (log off/in, may be). i'll try later...
-
Anonymous posted a comment on discussion General Discussion
Hiii! new install, new error ;) now it seems to stop right a way: g++ -m64 -pipe -O2 -Werror=return-type -Winit-self -Werror=init-self -Werror=misleading-indentation -std=c++11 -DMRB_ENABLE_DEBUG_HOOK -g -D_REENTRANT -Wall -W -DSOAS_VERSION='"2.2"' -DHAS_EXECINFO -DQT_SVG_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtSvg...
-
Barre d’échelle
-
The problem in this file comes from the fact that QSoas interprets the comma (used as decimal separator here) as column separators. The right way to load the file is: QSoas> load-as-text 10_MLE171106_2uL_seche4H30_TpTrisHCl50mM_NaCl150mM_degaze_Ph74_PGE3mm_3mVs_C01.txt /decimal=, Hope it helps
-
Anonymous created ticket #2
Barre d’échelle
-
Anonymous posted a comment on discussion General Discussion
quick follow-up, despite a number of error messages at the prompt upon running 'make', the 'run-all-tests' landed nicely (quite impressed by the running time w/o graphics, 10vs30sec)
-
Anonymous posted a comment on discussion General Discussion
Hi! that (almost) did the trick, thanks! I eventualy got some success (it launches, will see later about stability and possible bugs), but only with the mruby-1.4.1 build, the one referred to on qsoas.org seemed bot satisfactory. Pierre Cecc.
-
Hmmm... You need to have mruby installed and pass its install location to qmake using, for instance: ~ qmake MRUBY_DIR=/opt/mruby I guess a step-by-step tutorial may come in useful...
-
Anonymous posted a comment on discussion General Discussion
Still have installation error. ~/Apps/qsoas-2.2.0 $ make g++ -m64 -pipe -O2 -Werror=return-type -std=c++11 -DMRB_ENABLE_DEBUG_HOOK -g -D_REENTRANT -Wall -W -DSOAS_VERSION='"2.2"' -DHAS_EXECINFO -DQT_SVG_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtSvg -I/usr/include/qt4 -I. -Isrc -I/usr/X11R6/include...
-
Ah, this means that you are somehow missing the libqt4-opengl-dev package. Running ~ sudo apt-get install libqt4-opengl-dev should fix the problem.
-
Anonymous posted a comment on discussion General Discussion
Thanks for the answer. Have got new problem: ~/Apps/qsoas-2.2.0 $ qmake Project MESSAGE: Found /usr/include/execinfo.h, so we should have stack traces Project MESSAGE: Using odrpack ~/Apps/qsoas-2.2.0 $ make g++ -m64 -pipe -O2 -Werror=return-type -std=c++11 -DMRB_ENABLE_DEBUG_HOOK -g -D_REENTRANT -Wall -W -DSOAS_VERSION='"2.2"' -DHAS_EXECINFO -DQT_SVG_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork...
-
Hi ! You just need to remove the following lines from QSoas.pro: unix { QMAKE_CXXFLAGS += -Winit-self -Werror=init-self -Werror=misleading-indentation } Then, run qmake and make again. I will remove the problematic flag from the release branch, it does only make sense to keep it in the development branch. Kind regards, Vincent
-
Anonymous posted a comment on discussion General Discussion
Hi! How to fix this? cc1plus: error: -Werror=misleading-indentation: no option -Wmisleading-indentation Makefile:527: recipe for target 'build/QSoas.gch/c++' failed make: * [build/QSoas.gch/c++] Error 1 ~/Apps/qsoas-2.2.0 $ qmake Project MESSAGE: Found /usr/include/execinfo.h, so we should have stack traces Project MESSAGE: Using odrpack boris@Encelados ~/Apps/qsoas-2.2.0 $ make g++ -m64 -pipe -O2 -Werror=return-type -Winit-self -Werror=init-self -Werror=misleading-indentation -std=c++11 -DMRB_ENABLE_DEBUG_HOOK...
-
Version 2.2 failed to build with libgsl > 2
-
I've just released the source code of version 2.2.0, which fixes this problem.
-
Thanks for spotting this issue. Indeed, that is the only thing that need to be modified. I'm releasing an updated tarball as soon as the overnight build is over. Kind regards, Vincent
-
Anonymous created ticket #1
Version 2.2 failed to build with libgsl > 2
-
This just means you need a script ! I'm unsure what you want exactly, but try making a load-data.cmds containing this: l ${1} /columns=1,4 auto-filter-fft apply-formula x-=0.1 s ${1}.cleaned.dat /overwrite=true (just loading, filtering, subtracting 100 mV, and saving again) And run on your file using the following command: QSoas> @ load-data.cmds SWV_filename.csv If that does what you want,yYou can run that on all your data files at once using: QSoas> run-for-each load-data.cmds *.csv QSoas was built...
-
Anonymous posted a comment on discussion General Discussion
Thanks! l SWV_filename.csv /columns=1,2 l SWV_filename.csv /columns=1,3 l SWV_filename.csv /columns=1,4 Loading separately forward, backward and net data => then overlay... Unfortunately this way is unconvinient/long for fft filtering, potential correction of SWV data and saving data again in a file...
-
Hi ! In principle, yes. Have you had a look at the FAQ -- http://bip.cnrs-mrs.fr/bip06/qsoas/faq.html ? Could you post the data here, that we can help you ? BTW, don't use SOAS's doc for QSoas, the new documentation is found there: http://bip.cnrs-mrs.fr/bip06/qsoas/manual.html Best, Vincent
-
Anonymous posted a comment on discussion General Discussion
Hi, Does QSoas has possibility to load and process SWV data from csv four column text file? Commands from SOAS help doesn't work. http://bip.cnrs-mrs.fr/bip06/soas/node5.html
-
Hi. For fits, the potential should be in volts (SI unit), but this is not the main problem. QSoas just does not provide models for diffusive cyclic voltammetry, so you can't fit that (besides, there's nothing catalytic in the data you sent). However, you still can efficiently extract the peak information by running the command echem-peaks, see attached image.
-
Anonymous posted a comment on discussion General Discussion
Hi. I can't do fit CV (datafile attached) – I’ve got two vertical lines at 232 and 360 mV (Menu Fits→Fit of EC reversible catalytic wave. Fit resutls - are NAN. What are dimensions of variables before fitting CV (electrode potential – V/mV; current( or current density) – A/mA/uA? Where I can read about it? Do you have “standard/template” CV curve datafile or/and step-by-step instruction to start with? Thank you.
-
Mmmmm... As far as I understand, the error message can safely be ignored, and you should get a working QSoas package even in the absence of the gdb package. Do you still have around the (long) command-line that leads to this error message ? Have you checked the presence of the QSoas executable ? Cheers !
-
Anonymous posted a comment on discussion General Discussion
Sorry for polluting, installing gdb (GNU debug database, I assume) did the trick. the make ends smoothly. ./QSoas (mind the CAse) works fine ! PC
-
Anonymous posted a comment on discussion General Discussion
On debian Gnome 3.22.2, the 'make' command leads to this (after a relatively long thread, seemingly ok unitl...) /bin/sh: 1: gdb: not found /bin/sh: 1: test: -gt: unexpected operator I tried reinstalling ruby, with the -dev extension you mentioned, made sure gsl is present... What should I do next? Thanks Pierre C
-
Same problem as original post: you are using custom built Ruby. Drop it, and use the ruby2.1-dev or ruby2.3-dev package.
-
Anonymous posted a comment on discussion General Discussion
Why install the GSL manually (in /usr/local) ? Because it was mentioned at Download page in Compilation notes in order: the first - packages and then console command... Done on Debian 8. Thank you! Still have dozen warnings and final error message on run make on ubuntu. A few final lines from console: /usr/bin/ld: /usr/local/lib/libruby-static.a(dln.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libdl.so.2: error adding symbols: DSO missing from command line collect2:...
-
Why install the GSL manually (in /usr/local) ? Drop your manual install of the GSL and use the libgsl-dev package provided by Ubuntu, that is likely to work better.
-
Anonymous posted a comment on discussion General Discussion
on ubuntu 16.04 /Apps/qsoas-2.1$ make g++ -c -m64 -pipe -O2 -Werror=return-type -Winit-self -Werror=init-self -std=c++11 -g -D_REENTRANT -Wall -W -DSOAS_VERSION='"2.1"' -DHAS_EXECINFO -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4 -I. -Isrc -I/usr/local/include/ruby-2.1.0 -I/usr/local/include/ruby-2.1.0/x86_64-linux -I/usr/X11R6/include -Ibuild -o build/qmain.o...
-
This looks pretty OK, these are the messages expected when running ./configure. What happens when you run make ?
-
Anonymous posted a comment on discussion General Discussion
QSoas 2.1 on Debian 8 (Gnome) and Ubuntu 16.04. ruby 2.1/ 2.3 (compiled); gsi... (compiled). And have got this or similar messages: ~~~stable@debian:~/Apps/qsoas-2.1$ ./configure Project MESSAGE: Found /usr/include/execinfo.h, so we should have stack traces Project MESSAGE: Ruby: using /usr/bin/ruby2.1, found library: -lruby-2.1 and includes at /usr/include/ruby-2.1.0 /usr/include/x86_64-linux-gnu/ruby-2.1.0 Project MESSAGE: Using odrpack ~~~ How to fix it?
-
A simple way to obtain both the usual peak data and the area is to run the following commands: stats /output=false /set-meta=y_int 1 /meta=y_int This first stores the integral of the curve as the meta-data y_int and then writes the peak data together with the y_int meta to the output file. You could just save this two commands as a peak.cmds text file and run it from QSoas using QSoas> @ peak.cmds Next version will have a standard way to do that.
-
The fit-eecro-wave fit is a remnant of the old parametrization of the fit-*-wave...
-
Anonymous posted a comment on discussion General Discussion
I was wondering what is fit-eecro-wave doing. It's not defined on the help file and...
-
Fitting with derivatives doesn't work when X values are not strictly monotonous....
-
When you have a nice fit, use the "Data..."/"Push all subfunctions", this will create...
-
Anonymous posted a comment on discussion General Discussion
While running filter-fft /derive=1 I get the following message; "Mixed-radix: 1265...
-
The "surface under the peak" from 1 isn't so easy to do reliably. I have to check...
-
Best is to install the ruby2.1-dev package and not rely on manual install, or, even...
-
Sorry for missing your post earlier. You should have had a download link once you...
-
Anonymous posted a comment on discussion General Discussion
I am trying to install QSoas 2.1 on Xubuntu 16.04.2 LTS (Xenial). I have removed...
-
Anonymous posted a comment on discussion General Discussion
Hi I was wondering how you calculate the peak area in QSoas. I have done a baseline...
-
Anonymous posted a comment on discussion General Discussion
I was wondering if this is a way to export the subfunctions of a fitting so they...
-
Anonymous posted a comment on discussion General Discussion
I am also interested in having a function to integrate peak area in the "Peak find...
-
Anonymous posted a comment on discussion General Discussion
I bought a copy of QSoas (Windows binary) on evalorix.com on Wednesday. How will...
-
QSoas works seamlessly on 64 bit installations of windows, via the so-called WOW64...
-
Anonymous posted a comment on discussion General Discussion
The site says that it works for 32bit windows. Is there a problem in running on 64bit...
1
