You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(15) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(1) |
Feb
(11) |
Mar
(18) |
Apr
(1) |
May
(10) |
Jun
(5) |
Jul
(7) |
Aug
(5) |
Sep
(12) |
Oct
(2) |
Nov
|
Dec
(13) |
| 2004 |
Jan
(13) |
Feb
(46) |
Mar
(20) |
Apr
(10) |
May
(13) |
Jun
(8) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(47) |
Aug
(14) |
Sep
(7) |
Oct
(1) |
Nov
|
Dec
|
| 2006 |
Jan
(11) |
Feb
(17) |
Mar
(5) |
Apr
(9) |
May
(1) |
Jun
|
Jul
(5) |
Aug
(4) |
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2007 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
(3) |
Mar
(8) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(6) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(4) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Nivaldo H. B. <hi...@gm...> - 2011-10-22 02:24:08
|
For the functions color_classify<http://dl.dropbox.com/u/24233046/color_classify.xml> , color_classify_single<http://dl.dropbox.com/u/24233046/color_classify_single.xml> and color_segmentation<http://dl.dropbox.com/u/24233046/color_segmentation.xml>. |
|
From: Nivaldo H. B. <hi...@gm...> - 2011-10-18 23:01:27
|
Welcome, Andrei! Just like you, I've just started to study the SIP code and I'm also new at the open source community. Hope you enjoy the being a SIP developer (I know I do!). Best, Nivaldo 2011/10/17 Andrei Krishkevich <kol...@gm...> > Hello all, > > My name is Andrei, I'm a DSP engineer working at Clair Global, but looking > for other fun projects to do on the side. I'm new to open source community > development, so I'll learn as I go, but I do have a good amount of knowledge > in areas of signal and image processing as well as extensive Matlab > experience. I've come across Scilab while looking for free Matlab > alternatives other than Octave, which wouldn't for some reason run properly > on my Mint machine, and then I found out that it's still very much in > process of development, so I decided join the team and work on a few things. > I mainly do audio one-dimensional signal processing at work, if any, but I > had a strong emphasis on image processing in grad school, so this is a good > way to keep it fresh in my memory and also do some good. I'm just starting > to look through the current code and projects, but I hope I'll be up to > speed soon. > > I'm sure that this will be a very enjoyable collaboration. > > Cheers! = ] > > -- > I know not with what weapons World War III will be fought, but World War IV > will be fought with sticks and stones. > > - Albert Einstein > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > SIPtoolbox-devel mailing list > SIP...@li... > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > > |
|
From: Andrei K. <kol...@gm...> - 2011-10-18 01:23:31
|
Hello all, My name is Andrei, I'm a DSP engineer working at Clair Global, but looking for other fun projects to do on the side. I'm new to open source community development, so I'll learn as I go, but I do have a good amount of knowledge in areas of signal and image processing as well as extensive Matlab experience. I've come across Scilab while looking for free Matlab alternatives other than Octave, which wouldn't for some reason run properly on my Mint machine, and then I found out that it's still very much in process of development, so I decided join the team and work on a few things. I mainly do audio one-dimensional signal processing at work, if any, but I had a strong emphasis on image processing in grad school, so this is a good way to keep it fresh in my memory and also do some good. I'm just starting to look through the current code and projects, but I hope I'll be up to speed soon. I'm sure that this will be a very enjoyable collaboration. Cheers! = ] -- I know not with what weapons World War III will be fought, but World War IV will be fought with sticks and stones. - Albert Einstein |
|
From: Ricardo F. <ric...@us...> - 2011-09-25 21:25:41
|
Hi, I'd like to give some instructions on how to navigate the SIP code base, how to add a new function, and how the build system is organized. Please look into: http://wiki.nosdigitais.teia.org.br/SIP#Hacking Our goal with this build system is to support many libraries with a lot of flexibility, without worrying too much about Scilab's atoms packaging system. Best, Ricardo -- Linux registered user #175401 www.lems.brown.edu/~rfabbri |
|
From: Ricardo F. <ric...@us...> - 2011-09-19 22:03:18
|
Hello, all, Sourceforge revived our extensive to-do list of old: http://sourceforge.net/apps/taskfreak/siptoolbox/public.php Devs: take a look and send me suggestions while I clean it up and update it. We will be developing SIP heavily in the next days, and this will be essential. Best, Ricardo |
|
From: Ricardo F. <ric...@us...> - 2011-08-09 06:12:03
|
Hi, The SIP repositories were converted to Git. We will no longer support CVS. Please read the instructions on how to download and contribute using Git here: http://siptoolbox.sourceforge.net/devel/ We have already included a number of changes in the Git version, mainly to get SIP to compile in Ubuntu 11.04 and other environments. The Git version of SIP is where you can get the latest working SIP code. I would also like to welcome our new developers: hick209, wakkuu, and penalv. Hope you can enjoy their upcoming contributions. Cheers, Ricardo |
|
From: <so...@ei...> - 2010-10-22 18:48:28
|
Is there a fast way to convert sivp matrix format to the sip format. I think the sip format is more versatile. Thanks ------Original Message------ From: Ricardo Fabbri To: SIP Development and advanced discussion ReplyTo: Development and advanced discussion Subject: [SIP-devel] SIP and SIVP Sent: Oct 14, 2010 00:48 Hi, First of all I'd like to share with you that SIP CVS version compiles with latest Linux distros and latest Scilab, and a SIP Ubuntu package is under development. Also, new functions related to photogrammetry and rotations/quaternions have been added. Download and install the CVS by following the step-by-step instructions in http://siptoolbox.sf.net/devel . Now, as you know, SIVP is a fork of SIP that uses OpenCV as a library and which has been more suitable for video processing than the current version of SIP. However, SIVP doesn't have as many functions as SIP, and SIP can read/write much more image formats than SIVP. I have always tried to merge back as much functionality as possible from SIVP into SIP. Here's the current situation: Functionality in SIVP that is OpenCV-based: - Tracking (camshift) and video I/O - Canny - detectobjects/detecteyes - Image pyramids - Meanshift SIVP Scilab Scripts not currently in SIP: - conversion functions to/from ints - conversion from to/from ycbcr - improved convolution/correlation operators Other Todo's for SIP related to SIVP - use integers for matrices where appropriate - bring some of the cool demos over The idea is to merge back functionality from SIVP and I will try to be using OpenCV as an optional parameter to ./configure, as I stated in a previous email. Ricardo ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ SIPtoolbox-devel mailing list SIP...@li... https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel Let your email find you with BlackBerry® from Vodafone |
|
From: ZHANG, C. <zha...@gm...> - 2010-10-14 00:43:41
|
Hi, Ricardo, I noticed that there is another Image Processing Toolbox project http://forge.scilab.org/index.php/p/IPD/ It seems to me that SIVP and IPD are gaining more popularizes than SIP. And people are reinvesting the wheels over and over again. Motivated by your previous email I made an attempt to build SIP for Window last month. I added some CMakeLists.txt into CVS to make the build more easier. But I noticed that the C code in CVS was heavily dependent on GNU build toolchain. The config.h generated by running ./configure played a irreplaceable role for a successful build under Linux. That is hard for code to be build with CMake. By the way I also noticed that C99 syntax features seemed to be used in the CVS code which were also badly supported by Visual Studio. I've been doing all my research under Linux these years. So porting to Windows doesn't appear to be interesting to me even though I did it several years ago. Regards, Cheng On Wed, Oct 13, 2010 at 6:48 PM, Ricardo Fabbri < ric...@us...> wrote: > Hi, > > First of all I'd like to share with you that SIP CVS version compiles > with latest Linux distros and latest Scilab, and a SIP Ubuntu package > is under development. Also, new functions related to photogrammetry > and rotations/quaternions have been added. Download and install the > CVS by following the step-by-step instructions in > http://siptoolbox.sf.net/devel . > > Now, as you know, SIVP is a fork of SIP that uses OpenCV as a library > and which has been more suitable for video processing than the current > version of SIP. > However, SIVP doesn't have as many functions as SIP, and SIP can > read/write much more image formats than SIVP. > > I have always tried to merge back as much functionality as possible > from SIVP into SIP. Here's the current situation: > > Functionality in SIVP that is OpenCV-based: > - Tracking (camshift) and video I/O > - Canny > - detectobjects/detecteyes > - Image pyramids > - Meanshift > > SIVP Scilab Scripts not currently in SIP: > - conversion functions to/from ints > - conversion from to/from ycbcr > - improved convolution/correlation operators > > Other Todo's for SIP related to SIVP > - use integers for matrices where appropriate > - bring some of the cool demos over > > The idea is to merge back functionality from SIVP and I will try to be > using OpenCV as an optional parameter to ./configure, as I stated in a > previous email. > > Ricardo > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > SIPtoolbox-devel mailing list > SIP...@li... > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > -- Cheng Zhang PhD Candidate The Department of Electrical and Computer Engineering The University of Iowa, USA |
|
From: Ricardo F. <ric...@us...> - 2010-10-13 23:49:10
|
Hi, First of all I'd like to share with you that SIP CVS version compiles with latest Linux distros and latest Scilab, and a SIP Ubuntu package is under development. Also, new functions related to photogrammetry and rotations/quaternions have been added. Download and install the CVS by following the step-by-step instructions in http://siptoolbox.sf.net/devel . Now, as you know, SIVP is a fork of SIP that uses OpenCV as a library and which has been more suitable for video processing than the current version of SIP. However, SIVP doesn't have as many functions as SIP, and SIP can read/write much more image formats than SIVP. I have always tried to merge back as much functionality as possible from SIVP into SIP. Here's the current situation: Functionality in SIVP that is OpenCV-based: - Tracking (camshift) and video I/O - Canny - detectobjects/detecteyes - Image pyramids - Meanshift SIVP Scilab Scripts not currently in SIP: - conversion functions to/from ints - conversion from to/from ycbcr - improved convolution/correlation operators Other Todo's for SIP related to SIVP - use integers for matrices where appropriate - bring some of the cool demos over The idea is to merge back functionality from SIVP and I will try to be using OpenCV as an optional parameter to ./configure, as I stated in a previous email. Ricardo |
|
From: Ricardo F. <ric...@us...> - 2010-10-10 10:23:29
|
Hi Vitor, Zhang Cheng seems to have started some CMake scripts. You can find them in CVS. I agree that this would make cross-platform compilation much easier, esp. under windows. Thanks for your participation, Ricardo On Sat, Oct 9, 2010 at 11:24 PM, vitors <vi...@cn...> wrote: > Hello Ricardo and all SIP developers, > > I have some experience using CMake to perform multi platarfom > compilation. Unfortunately I'm too busy now doing a post grad course, but I > would be glad to help (if I can...) with CMake scripts. > > Vitor > >> Hi, >> >> I dont have much time to maintain a windows version of SIP. However, >> there seems to be recent development activity in switching to the >> CMake build system. This should make compiling SIP for windows a lot >> simpler. >> >> > > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > SIPtoolbox-devel mailing list > SIP...@li... > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > |
|
From: vitors <vi...@cn...> - 2010-10-10 03:49:00
|
Hello Ricardo and all SIP developers, I have some experience using CMake to perform multi platarfom compilation. Unfortunately I'm too busy now doing a post grad course, but I would be glad to help (if I can...) with CMake scripts. Vitor > Hi, > > I dont have much time to maintain a windows version of SIP. However, > there seems to be recent development activity in switching to the > CMake build system. This should make compiling SIP for windows a lot > simpler. > > |
|
From: Ricardo F. <ric...@us...> - 2010-10-09 23:44:02
|
Hi, I dont have much time to maintain a windows version of SIP. However, there seems to be recent development activity in switching to the CMake build system. This should make compiling SIP for windows a lot simpler. Best, On Monday, September 20, 2010, Christophe <so...@ei...> wrote: > Hi Ricardo, > > Interesting email. > > I have switched away from SIP to SIVP, since the SIP toolbox hasn't been > ported to Windows and scilab 5.0. Do you kow if SIP will be available > under windows anytime soon. I love the toolbox. > > Cheers > > On 19/09/2010 13:05, Ricardo Fabbri wrote: >> Hi all, >> >> It has been a while, but I've always kept SIP in mind. I'd like to >> share with you some ideas motivating me towards this project. They >> should also be useful for SIP forks and other similar software: >> >> Developing SIP is not only towards generating a final useful toolbox; >> this development activity can fundamentally be seen as a *fun* way of >> playing with image processing and computer vision algorithms. I can >> argue that this Fun is so deep and far-reaching that it has power to >> revolutionize computer vision as a field - and to make it >> understandable, to make it more applicable, to popularize it, to teach >> it, and to develop new methods for it. Ok, that is all beautiful and >> good and abstract, and so here are some pragmatic ideas from this >> "Just for Fun"/Torvaldian way of thinking: >> >> It would be cool to have SIP be explicitly divided into two: >> 1) a core SIP which is built by default and should be as stable >> as possible. This has the universally useful image I/O functionality >> (imread, imwrite, imshow, imfinfo, ...), and perhaps other >> easy-to-support stuff. >> 2) an experimental SIP, which is all the rest of functionality. >> This should only be enabled by passing an explicit configure flag e.g. >> : >> ./configure --all_fancy_features >> >> >> The experimental component would take the Just for Fun philosophy to >> an extreme. More specifically, it would ruthlessly interface to as >> many external libs as desired (VXL, OpenCV, Leptonica, LTILib, >> AnImaL, and so on), without much concern about portability or ease of >> installation at first. >> >> As a developer, it is fun to write Scilab/scripted interfaces to >> these external libs as it helps you learn the algorithms and >> functionalities of these libs, and also helps you have this >> functionality easily available in a nice easy-to-use environment. You >> then see your work being used by those power users like adventure and >> use the "--fancy_features" functionality, and with time these can >> even make into 'core'. Note that even if Scilab itself has its own >> "quirks", that itself actually adds to the fun and can actually lead >> to different and innovative ways of exploring image processing. >> >> Writing Scilab interfaces to these libs or even scilab scripts for the >> SIP toolbox is also an awesome way not only to explore these >> algorithms, but also to document them. Each function you write for SIP >> is documented with a nice interactive example, and can also be part of >> a demo. That's the other thing, producing demos in Scilab are >> extremely easy and fun to do once the scripting interface has been >> built. And having demos just makes computer vision more fun. >> >> So out of these purely "just for fun" activities, I believe other good >> things come as a natural consequence. Naturally, a community starts >> being built around SIP due to the social culture of free software >> based on sharing. The computer vision field moves forward. Scilab >> itself gets better. >> Image processing courses get more fun to teach and participate. It all >> works well, as long as we don't start "pretending" SIP is a finished >> product to be pristinely packaged& delivered& supported, but just >> accepting that above this it is just another way of having fun with >> algorithms, computers, and vision. >> >> PS: This is not just talk.. I hope. I'm installing Scilab + SIP on >> Ubuntu Lucid& Mac OS X right now. Join the fun! >> Ricardo >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> SIPtoolbox-devel mailing list >> SIP...@li... >> https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel >> > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > SIPtoolbox-devel mailing list > SIP...@li... > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > -- Ricardo |
|
From: Christophe <so...@ei...> - 2010-09-20 14:13:05
|
Hi Ricardo, Interesting email. I have switched away from SIP to SIVP, since the SIP toolbox hasn't been ported to Windows and scilab 5.0. Do you kow if SIP will be available under windows anytime soon. I love the toolbox. Cheers On 19/09/2010 13:05, Ricardo Fabbri wrote: > Hi all, > > It has been a while, but I've always kept SIP in mind. I'd like to > share with you some ideas motivating me towards this project. They > should also be useful for SIP forks and other similar software: > > Developing SIP is not only towards generating a final useful toolbox; > this development activity can fundamentally be seen as a *fun* way of > playing with image processing and computer vision algorithms. I can > argue that this Fun is so deep and far-reaching that it has power to > revolutionize computer vision as a field - and to make it > understandable, to make it more applicable, to popularize it, to teach > it, and to develop new methods for it. Ok, that is all beautiful and > good and abstract, and so here are some pragmatic ideas from this > "Just for Fun"/Torvaldian way of thinking: > > It would be cool to have SIP be explicitly divided into two: > 1) a core SIP which is built by default and should be as stable > as possible. This has the universally useful image I/O functionality > (imread, imwrite, imshow, imfinfo, ...), and perhaps other > easy-to-support stuff. > 2) an experimental SIP, which is all the rest of functionality. > This should only be enabled by passing an explicit configure flag e.g. > : > ./configure --all_fancy_features > > > The experimental component would take the Just for Fun philosophy to > an extreme. More specifically, it would ruthlessly interface to as > many external libs as desired (VXL, OpenCV, Leptonica, LTILib, > AnImaL, and so on), without much concern about portability or ease of > installation at first. > > As a developer, it is fun to write Scilab/scripted interfaces to > these external libs as it helps you learn the algorithms and > functionalities of these libs, and also helps you have this > functionality easily available in a nice easy-to-use environment. You > then see your work being used by those power users like adventure and > use the "--fancy_features" functionality, and with time these can > even make into 'core'. Note that even if Scilab itself has its own > "quirks", that itself actually adds to the fun and can actually lead > to different and innovative ways of exploring image processing. > > Writing Scilab interfaces to these libs or even scilab scripts for the > SIP toolbox is also an awesome way not only to explore these > algorithms, but also to document them. Each function you write for SIP > is documented with a nice interactive example, and can also be part of > a demo. That's the other thing, producing demos in Scilab are > extremely easy and fun to do once the scripting interface has been > built. And having demos just makes computer vision more fun. > > So out of these purely "just for fun" activities, I believe other good > things come as a natural consequence. Naturally, a community starts > being built around SIP due to the social culture of free software > based on sharing. The computer vision field moves forward. Scilab > itself gets better. > Image processing courses get more fun to teach and participate. It all > works well, as long as we don't start "pretending" SIP is a finished > product to be pristinely packaged& delivered& supported, but just > accepting that above this it is just another way of having fun with > algorithms, computers, and vision. > > PS: This is not just talk.. I hope. I'm installing Scilab + SIP on > Ubuntu Lucid& Mac OS X right now. Join the fun! > Ricardo > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > SIPtoolbox-devel mailing list > SIP...@li... > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > |
|
From: Ricardo F. <ric...@us...> - 2010-09-19 12:05:59
|
Hi all,
It has been a while, but I've always kept SIP in mind. I'd like to
share with you some ideas motivating me towards this project. They
should also be useful for SIP forks and other similar software:
Developing SIP is not only towards generating a final useful toolbox;
this development activity can fundamentally be seen as a *fun* way of
playing with image processing and computer vision algorithms. I can
argue that this Fun is so deep and far-reaching that it has power to
revolutionize computer vision as a field - and to make it
understandable, to make it more applicable, to popularize it, to teach
it, and to develop new methods for it. Ok, that is all beautiful and
good and abstract, and so here are some pragmatic ideas from this
"Just for Fun"/Torvaldian way of thinking:
It would be cool to have SIP be explicitly divided into two:
1) a core SIP which is built by default and should be as stable
as possible. This has the universally useful image I/O functionality
(imread, imwrite, imshow, imfinfo, ...), and perhaps other
easy-to-support stuff.
2) an experimental SIP, which is all the rest of functionality.
This should only be enabled by passing an explicit configure flag e.g.
:
./configure --all_fancy_features
The experimental component would take the Just for Fun philosophy to
an extreme. More specifically, it would ruthlessly interface to as
many external libs as desired (VXL, OpenCV, Leptonica, LTILib,
AnImaL, and so on), without much concern about portability or ease of
installation at first.
As a developer, it is fun to write Scilab/scripted interfaces to
these external libs as it helps you learn the algorithms and
functionalities of these libs, and also helps you have this
functionality easily available in a nice easy-to-use environment. You
then see your work being used by those power users like adventure and
use the "--fancy_features" functionality, and with time these can
even make into 'core'. Note that even if Scilab itself has its own
"quirks", that itself actually adds to the fun and can actually lead
to different and innovative ways of exploring image processing.
Writing Scilab interfaces to these libs or even scilab scripts for the
SIP toolbox is also an awesome way not only to explore these
algorithms, but also to document them. Each function you write for SIP
is documented with a nice interactive example, and can also be part of
a demo. That's the other thing, producing demos in Scilab are
extremely easy and fun to do once the scripting interface has been
built. And having demos just makes computer vision more fun.
So out of these purely "just for fun" activities, I believe other good
things come as a natural consequence. Naturally, a community starts
being built around SIP due to the social culture of free software
based on sharing. The computer vision field moves forward. Scilab
itself gets better.
Image processing courses get more fun to teach and participate. It all
works well, as long as we don't start "pretending" SIP is a finished
product to be pristinely packaged & delivered & supported, but just
accepting that above this it is just another way of having fun with
algorithms, computers, and vision.
PS: This is not just talk.. I hope. I'm installing Scilab + SIP on
Ubuntu Lucid & Mac OS X right now. Join the fun!
Ricardo
|
|
From: Ricardo F. <ric...@us...> - 2010-05-05 01:14:56
|
Hi, all, the CVS version of SIP and its core library AnImaL have improved build systems allowing for greater portability across recent Linux systems. SIP also compiles with the new Scilab 5.2.2. As I am finishing my PhD thesis, I don't have the time to make new packaged releases. Please download the new versions from CVS using the following instructions: First, issue the following command: cvs -d:pserver:ano...@si...:/cvsroot/siptoolbox login To download SIP, do: cvs -z3 -d:pserver:ano...@si...:/cvsroot/siptoolbox co -P siptoolbox To download AnImaL, do: cvs -z3 -d:pserver:ano...@si...:/cvsroot/siptoolbox co -P animal Thanks for using the SIP toolbox. Ricardo Fabbri |
|
From: Ricardo F. <ric...@us...> - 2009-10-21 00:51:39
|
This is just a good paper to read about when dealing with shared objects http://people.redhat.com/drepper/dsohowto.pdf Ricardo |
|
From: Ricardo F. <ric...@us...> - 2009-04-17 00:39:48
|
Hi, the Scilab Image Processing toolbox version 0.4.1 has been released. This new minor version works for Scilab 5.1.1, has an improved build system for newer ImageMagick, and has all 64 documentation files updated to the new DocBook format. Check out the documentation on the web: http://siptoolbox.sourceforge.net/doc/sip-0.4.1-reference/ Currently only a source code release is available, which readily installs under Linux. An experimental windows version is available only for Scilab 4 at this point. If you wish to contribute with a windows port, you will be greatly praised by the community. SIP has over 60 downloads/day and about 2000 page views/day! The demand for a windows port is huge. Please report any problems to our bug tracker: https://sourceforge.net/tracker/?group_id=68055&atid=519890 About: SIP provides image processing, pattern recognition, and computer vision routines for SciLab, a Matlab-like matrix-oriented programming environment. SIP is able to read/write images in almost 90 major formats, including JPEG, PNG, BMP, GIF, FITS, and TIFF. It includes routines for filtering, segmentation, edge detection, morphology, curvature, fractal dimension, distance transforms, multiscale skeletons, and more. http://siptoolbox.sourceforge.net Enjoy, Ricardo Fabbri |
|
From: Ricardo F. <ric...@us...> - 2009-04-16 23:42:00
|
Hi, all, the help pages were completely translated into the Scilab 5 DocBook format. Thanks to bugfixes to Scilab 5.1.1. the xmltodocbook toolbox now worked just fine in converting the old Scilab 4 xml files to the new ones. It seems the Scilab team has been pretty active, they respond to my bug reports sooner or later. SIP 0.4.1 should be out soon with these improvements and other minor fixes. Ricardo |
|
From: Ricardo F. <ric...@us...> - 2009-04-10 14:21:12
|
Hi, the Scilab Image Processing toolbox version 0.4.0 has been released. This new major version works for Scilab 5.1, and brings new functions such as a new fast Euclidean distance map algorithm, phase unwrapping, Radon transform, HSV color space transformations, and more. Many other bugfixes and minor improvements were added, and recent versions of ImageMagick are now supported to read and write over 90 image formats. Currently only a source code release is available, which readily installs under Linux. An experimental windows version is available only for Scilab 4 at this point. If you wish to contribute with a windows port, you will be greatly praised by the community. SIP has over 60 downloads/day and about 2000 page views/day! The demand for a windows port is huge. We are in the process of migrating help files to the new DocBook format for Scilab 5. The SIP 0.4.0 release contains DocBook help pages for most of the core functions, but we still have about 40 more function documentations to convert. Please report any problems to our bug tracker: https://sourceforge.net/tracker/?group_id=68055&atid=519890 About: SIP provides image processing, pattern recognition, and computer vision routines for SciLab, a Matlab-like matrix-oriented programming environment. SIP is able to read/write images in almost 90 major formats, including JPEG, PNG, BMP, GIF, FITS, and TIFF. It includes routines for filtering, segmentation, edge detection, morphology, curvature, fractal dimension, distance transforms, multiscale skeletons, and more. http://siptoolbox.sourceforge.net Cheers, Ricardo Fabbri |
|
From: <ric...@us...> - 2009-04-04 22:08:32
|
Hi, all, I got a system to build help files for Scilab 5.1 going, it should work in the CVS version. Having a friendly fork of SIP around that already does this (SIVP) definitely helped a lot, but we still need volunteers to translate remaining help files to the new format. That's all that remains for us to have a completely working SIP for Scilab 5.1. We have 65 help files in SIP! I already translated all the docs of functions that have some overlap with SIVP (10 files), as well as other important ones from SIP, such as mogrify. It was an interesting idea to do it by hand, since it taught me the differences between the two toolboxes and got me started in merging the two. I tried to translate the remaining help files using an automated tool provided by the Scilab team - the xmltodocbook toolbox: http://www.scilab.org/contrib/index_contrib.php?page=displayContribution&fileID=1163 but it didn't work on my computer - Java crashes (gentoo Linux with sun-jdk-1.6). We had a custom DTD for the 4.x help pages which might complicate the use of such an automated tool, so I think doing it by hand is the most likely solution. We can take the opportunity to fix any typos and learn the new help style. Last time we moved from the old Scilab 2.x to 4.x help styles, Vitor admirably did most of the work. Here are my guidelines for doing this. The new help files are in the help/en_US directory (as opposed to 'man'), and you can start from a copy of the existing ones to use as a template. My only requirement is that you try to keep the XML tags in the file well-indented as much as you can, but we should not enforce a strict style. It is up to you, just keep it fairly clean. Once you translated a new help file, say man/bwdist.xml to help/en_US/bwdist.xml, then add the file to the list in help/Makefile.am, and type "make" inside the help directory. That should rebuild the help files. Instead of opening scilab all over again to check if the help file formatting looks good, you can just point your browser to help/en_US/scilab_en_US_help/index.html and navigate to your function. Keeping the browser open, all you have to do is refresh it after you make a change to your xml file and type "make" inside the help folder. Once all the files are done, I will immediately make a new SIP release, with plenty of thank you notes to the volunteer(s). So your help would be appreciated since a new release of SIP is more than needed! Thanks! Ricardo |
|
From: Liberio <lib...@gm...> - 2009-04-03 06:33:21
|
Hi, all, we have updated SIP CVS to compile with Scilab 5 and 4 at the same time. Please give it a try and let us know how it works for you. The help pages still don't build in Scilab 5, but that should be fixed in the next couple of days. The merge with SIVP is ongoing and we added a dummy test for opencv. |
|
From: <ric...@us...> - 2009-03-31 22:32:48
|
Actually, I realized that my sip tree was pointing to some old Scilab 4.x sources, so that's why it compiled normally. The strange thing is that it used Scilab 4.x to compile, while it loaded _and_ ran just fine in Scilab 5.x We will need some time to port SIP to Scilab 5 and that is a process that also involves merging-in some changes from SIVP. Although this process has started, it is not so simple and will take some days to finish. Sorry for the inconvenience, On Sun, Mar 29, 2009 at 9:03 PM, Dean S. Messing <de...@sh...> wrote: > >> just letting you know that I've compiled the SIP CVS version and it >> compiles and works with Scilab 5.1 under linux. > > Wow! Good news. I will proceed to spend the time to build > 5.1 and SIP on my system (Fedora 10) system in the next > few days. > > Thanks > > Dean > |
|
From: <ric...@us...> - 2009-03-30 20:01:38
|
Hi Vitor & Cheng, CMake is great, there are many reasons I'd like to see it used: - I also have been using it extensively with the VXL computer vision libraries, which could very well be used as one of the basis for new SIP functions in the future. I actually already build some interface functions between vxl and matlab using CMake, and that should give a good idea on how to do the same for SIP/Scilab. - KDE migrated to use CMake, and so many other huge libraries use it, so it is a ubiquitous and standard tool. - My lab has connections with people in Kitware - Most importantly, we want to be able to support many OS. Right now the Autoconf/Automake tools work very well only for Linux. So I hope this idea can be pushed forward with concrete and realistic results. While the CMake port is being done, nothing prevents us from trying to start merging SIP and SIVP with the current build system and get it to work well in Linux first. That will get most conflicts and merges between the two out of the way. 2009/3/30 Cheng Zhang <che...@en...>: > Hi Vitor, > > FYI. I had already used CMake in SIP Windows port in 2005. I definitely > support your idea of adopting CMake in SIP's build process. It's a great > tool. > > Cheng > > On Mon, Mar 30, 2009 at 9:51 AM, <vi...@cn...> wrote: >> >> Hello Fabbri and all SIP and SIVP developers, >> >> I was wondering if could help you with the transition step you >> mentioned. When you said about "configure", which tool where you >> talking about? Let me explain: I joined for two years a software >> project and one of my tasks was to move from GNU autotools to CMake. >> The idea was to use the same set of scripts to be able to build our >> software (library, unit tests, documentation, GUI, etc.) on both Linux >> and Windows environments. >> My experience says that CMake is simply excellent doing this job. >> >> The biggest problem now is to manage my time because I just moved from >> team (and city) and I'll be quite busy for the next two months. >> However, once things get more organized and clear at the office, I can >> say how much time I would have to work on SIP install scripting. >> >> Please, let me know what you think about this idea. >> >> Vitor >> >> p.s.: For those who don't know CMake: http://www.cmake.org >> > Hi Shiqi, >> > >> > long time no see! >> > >> > As a follow-up to our usual idea of merging SIP and SIVP, I had an >> > idea about supporting both OpenCV and ImageMagick. Here is a plan of >> > how this can be feasible: >> > >> > The end-goal would be a toolbox that optionally compiles the functions >> > that use >> > opencv, or the functions that use imagemagick, or both, depending on >> > flags passed to the >> > configure script. For the functions that overlap, we can start by >> > providing both >> > implementations, the configure script will default to the best >> > option. For example, imread can be implemented by ImageMagick by >> > default, but if we choose not to use >> > imagemagick, then an imread by opencv would be used. Of course, if it >> > turns out that there is no advantage in keeping two implementations >> > around, in the future we can >> > remove one of them. >> > >> > We can start with a transition plan. The short term goal would be to >> > start >> > providing such a "configure" script in SIP, which can take both opencv >> > and >> > imagemagick, or just one of them. By default, for now, SIP would compile >> > to the >> > normal SIP without opencv, but if you pass a flag such as "--full-build" >> > then it >> > would try to compile all possible functions (the union of SIP and SIVP). >> > >> > Once that is done, SIVP could also have a transitional version that >> > would >> > be >> > identical to the above package, but whose configure script would default >> > to >> > build the usual OpenCV-based SIVP, without imagemagick. >> > >> > That is a lot of work, but all the effort would be towards trying to >> > bring >> > SIP and SIVP into agreement where they overlap, and complementing each >> > other >> > where they don't overlap. For instance, the transitional "SIP" would >> > have >> > to >> > move towards supporting integer formats. >> > >> > I think I can try to start the transitional merge by incorporating SIVP >> > features >> > back into SIP and activating opencv as an optional step. >> > >> > We can always keep it simple by providing the SIP and SIVP-style >> > packages >> > around. >> > >> > Let me know what you think. >> > >> > Thanks. >> > >> > >> > >> >> Hi Shiqi, >> >> >> >> I am sorry I didn't reply to your email before, I have been extremely >> >> busy with my PhD load, but hopefully I will gradually get back to SIP >> >> and Scilab. >> >> It is a really good idea to merge SIP and SIVP. The main difference >> >> right now seems to be that SIP uses ImageMagick. I think OpenCV cannot >> >> handle as many image formats, right? Imagemagick handles virtually 100 >> >> formats. It would be nice to support both, but maybe it would be to >> >> hard to maintain everything into a single toolbox. If we work >> >> together, it might be feasible, though. I was also thinking about >> >> interfacing http://vxl.sourceforge.net >> >> but that is more for a long-term project. >> >> >> >> Anyways, great job with SIVP. You can continue to use SIP code as you >> >> wish. >> >> >> >> Let me know what are your ideas, >> >> >> >> >> >>> >> >>> >> >>> I noticed you have put a notice on SIP homepage. It's a googd news >> >>> for >> >>> all SIP users. ^-^ >> >> >> >>> Now SIVP is still in developing. I have ported some macros such as >> >>> imnoise, edge, etc from SIP to SIVP. Compared with SIP, the >> >>> advantages >> >>> of SIVP are integer image support(UINT8, INT8, ..., INT32) and some >> >>> fast >> >>> functions which using OpenCV (such as canny in SIVP edge function). >> >>> The >> >>> disadvantage is that the functions are still not enough. The SIVP >> >>> function prototypes is the same as Matlab Image Processing toolbox. >> >>> >> >>> You will be back to SIP next month. I wonder if it's a chance to >> >>> merge >> >>> SIP and SIVP to one toolbox. >> >>> >> >>> Shiqi >> >>> >> >>> >> > >> > >> > ------------------------------------------------------------------------------ >> > _______________________________________________ >> > SIPtoolbox-devel mailing list >> > SIP...@li... >> > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel >> > >> >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> SIPtoolbox-devel mailing list >> SIP...@li... >> https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > > > > -- > Cheng Zhang > > PhD Candidate > The Department of Electrical and Computer Engineering > The University of Iowa, USA > > ------------------------------------------------------------------------------ > > _______________________________________________ > SIPtoolbox-devel mailing list > SIP...@li... > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > > |
|
From: Cheng Z. <che...@en...> - 2009-03-30 17:47:42
|
Hi Vitor, FYI. I had already used CMake in SIP Windows port in 2005. I definitely support your idea of adopting CMake in SIP's build process. It's a great tool. Cheng On Mon, Mar 30, 2009 at 9:51 AM, <vi...@cn...> wrote: > Hello Fabbri and all SIP and SIVP developers, > > I was wondering if could help you with the transition step you > mentioned. When you said about "configure", which tool where you > talking about? Let me explain: I joined for two years a software > project and one of my tasks was to move from GNU autotools to CMake. > The idea was to use the same set of scripts to be able to build our > software (library, unit tests, documentation, GUI, etc.) on both Linux > and Windows environments. > My experience says that CMake is simply excellent doing this job. > > The biggest problem now is to manage my time because I just moved from > team (and city) and I'll be quite busy for the next two months. > However, once things get more organized and clear at the office, I can > say how much time I would have to work on SIP install scripting. > > Please, let me know what you think about this idea. > > Vitor > > p.s.: For those who don't know CMake: http://www.cmake.org > > Hi Shiqi, > > > > long time no see! > > > > As a follow-up to our usual idea of merging SIP and SIVP, I had an > > idea about supporting both OpenCV and ImageMagick. Here is a plan of > > how this can be feasible: > > > > The end-goal would be a toolbox that optionally compiles the functions > > that use > > opencv, or the functions that use imagemagick, or both, depending on > > flags passed to the > > configure script. For the functions that overlap, we can start by > > providing both > > implementations, the configure script will default to the best > > option. For example, imread can be implemented by ImageMagick by > > default, but if we choose not to use > > imagemagick, then an imread by opencv would be used. Of course, if it > > turns out that there is no advantage in keeping two implementations > > around, in the future we can > > remove one of them. > > > > We can start with a transition plan. The short term goal would be to > > start > > providing such a "configure" script in SIP, which can take both opencv > and > > imagemagick, or just one of them. By default, for now, SIP would compile > > to the > > normal SIP without opencv, but if you pass a flag such as "--full-build" > > then it > > would try to compile all possible functions (the union of SIP and SIVP). > > > > Once that is done, SIVP could also have a transitional version that would > > be > > identical to the above package, but whose configure script would default > > to > > build the usual OpenCV-based SIVP, without imagemagick. > > > > That is a lot of work, but all the effort would be towards trying to > bring > > SIP and SIVP into agreement where they overlap, and complementing each > > other > > where they don't overlap. For instance, the transitional "SIP" would have > > to > > move towards supporting integer formats. > > > > I think I can try to start the transitional merge by incorporating SIVP > > features > > back into SIP and activating opencv as an optional step. > > > > We can always keep it simple by providing the SIP and SIVP-style packages > > around. > > > > Let me know what you think. > > > > Thanks. > > > > > > > >> Hi Shiqi, > >> > >> I am sorry I didn't reply to your email before, I have been extremely > >> busy with my PhD load, but hopefully I will gradually get back to SIP > >> and Scilab. > >> It is a really good idea to merge SIP and SIVP. The main difference > >> right now seems to be that SIP uses ImageMagick. I think OpenCV cannot > >> handle as many image formats, right? Imagemagick handles virtually 100 > >> formats. It would be nice to support both, but maybe it would be to > >> hard to maintain everything into a single toolbox. If we work > >> together, it might be feasible, though. I was also thinking about > >> interfacing http://vxl.sourceforge.net > >> but that is more for a long-term project. > >> > >> Anyways, great job with SIVP. You can continue to use SIP code as you > >> wish. > >> > >> Let me know what are your ideas, > >> > >> > >>> > >>> > >>> I noticed you have put a notice on SIP homepage. It's a googd news for > >>> all SIP users. ^-^ > >> > >>> Now SIVP is still in developing. I have ported some macros such as > >>> imnoise, edge, etc from SIP to SIVP. Compared with SIP, the advantages > >>> of SIVP are integer image support(UINT8, INT8, ..., INT32) and some > >>> fast > >>> functions which using OpenCV (such as canny in SIVP edge function). > >>> The > >>> disadvantage is that the functions are still not enough. The SIVP > >>> function prototypes is the same as Matlab Image Processing toolbox. > >>> > >>> You will be back to SIP next month. I wonder if it's a chance to merge > >>> SIP and SIVP to one toolbox. > >>> > >>> Shiqi > >>> > >>> > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > SIPtoolbox-devel mailing list > > SIP...@li... > > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > SIPtoolbox-devel mailing list > SIP...@li... > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel > -- Cheng Zhang PhD Candidate The Department of Electrical and Computer Engineering The University of Iowa, USA |
|
From: <vi...@cn...> - 2009-03-30 15:17:01
|
Hello Fabbri and all SIP and SIVP developers,
I was wondering if could help you with the transition step you
mentioned. When you said about "configure", which tool where you
talking about? Let me explain: I joined for two years a software
project and one of my tasks was to move from GNU autotools to CMake.
The idea was to use the same set of scripts to be able to build our
software (library, unit tests, documentation, GUI, etc.) on both Linux
and Windows environments.
My experience says that CMake is simply excellent doing this job.
The biggest problem now is to manage my time because I just moved from
team (and city) and I'll be quite busy for the next two months.
However, once things get more organized and clear at the office, I can
say how much time I would have to work on SIP install scripting.
Please, let me know what you think about this idea.
Vitor
p.s.: For those who don't know CMake: http://www.cmake.org
> Hi Shiqi,
>
> long time no see!
>
> As a follow-up to our usual idea of merging SIP and SIVP, I had an
> idea about supporting both OpenCV and ImageMagick. Here is a plan of
> how this can be feasible:
>
> The end-goal would be a toolbox that optionally compiles the functions
> that use
> opencv, or the functions that use imagemagick, or both, depending on
> flags passed to the
> configure script. For the functions that overlap, we can start by
> providing both
> implementations, the configure script will default to the best
> option. For example, imread can be implemented by ImageMagick by
> default, but if we choose not to use
> imagemagick, then an imread by opencv would be used. Of course, if it
> turns out that there is no advantage in keeping two implementations
> around, in the future we can
> remove one of them.
>
> We can start with a transition plan. The short term goal would be to
> start
> providing such a "configure" script in SIP, which can take both opencv and
> imagemagick, or just one of them. By default, for now, SIP would compile
> to the
> normal SIP without opencv, but if you pass a flag such as "--full-build"
> then it
> would try to compile all possible functions (the union of SIP and SIVP).
>
> Once that is done, SIVP could also have a transitional version that would
> be
> identical to the above package, but whose configure script would default
> to
> build the usual OpenCV-based SIVP, without imagemagick.
>
> That is a lot of work, but all the effort would be towards trying to bring
> SIP and SIVP into agreement where they overlap, and complementing each
> other
> where they don't overlap. For instance, the transitional "SIP" would have
> to
> move towards supporting integer formats.
>
> I think I can try to start the transitional merge by incorporating SIVP
> features
> back into SIP and activating opencv as an optional step.
>
> We can always keep it simple by providing the SIP and SIVP-style packages
> around.
>
> Let me know what you think.
>
> Thanks.
>
>
>
>> Hi Shiqi,
>>
>> I am sorry I didn't reply to your email before, I have been extremely
>> busy with my PhD load, but hopefully I will gradually get back to SIP
>> and Scilab.
>> It is a really good idea to merge SIP and SIVP. The main difference
>> right now seems to be that SIP uses ImageMagick. I think OpenCV cannot
>> handle as many image formats, right? Imagemagick handles virtually 100
>> formats. It would be nice to support both, but maybe it would be to
>> hard to maintain everything into a single toolbox. If we work
>> together, it might be feasible, though. I was also thinking about
>> interfacing http://vxl.sourceforge.net
>> but that is more for a long-term project.
>>
>> Anyways, great job with SIVP. You can continue to use SIP code as you
>> wish.
>>
>> Let me know what are your ideas,
>>
>>
>>>
>>>
>>> I noticed you have put a notice on SIP homepage. It's a googd news for
>>> all SIP users. ^-^
>>
>>> Now SIVP is still in developing. I have ported some macros such as
>>> imnoise, edge, etc from SIP to SIVP. Compared with SIP, the advantages
>>> of SIVP are integer image support(UINT8, INT8, ..., INT32) and some
>>> fast
>>> functions which using OpenCV (such as canny in SIVP edge function).
>>> The
>>> disadvantage is that the functions are still not enough. The SIVP
>>> function prototypes is the same as Matlab Image Processing toolbox.
>>>
>>> You will be back to SIP next month. I wonder if it's a chance to merge
>>> SIP and SIVP to one toolbox.
>>>
>>> Shiqi
>>>
>>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> SIPtoolbox-devel mailing list
> SIP...@li...
> https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel
>
|
