siptoolbox-devel — Development and advanced discussion

Re: [SIP-devel] I just join the SIP mailing list

[Ricardo F. <rf...@gm...>]

>     I'm so glad to join the SIP mailing list. I want to do something for
> SIP. I'm reading the SIP source code recently, and have had a basic
> understanding of the structure of SIP. Now I'm doing some small changes
> of source code in order to have a better understanding of the interfaces
> among SIP, Animal and Scilab.

Excellent. there is a very simple toolbox having the same build
structure as SIP,
maybe you would like to take a look at that too:
http://sourceforge.net/project/showfiles.php?group_id=3D68055&package_id=3D=
83851

>     Thanks for Ricardo's enthusiastic reply, if you need me to do some
> work for Windows port, just let me know. What I want to do is to involve
> SIP development as soon as possible.

Sure. Try to compile the simple toolbox first. I did it already and it work=
s.
The whole instrunctions are at:
http://siptoolbox.sourceforge.net/devel/windows-port.php

>     After a rough reading of source code, I have some immature ideas
> about SIP as follows:
> 1) Should we adopt MagickWand API instead of the MagickCore API? Since
> MagickWand API is easier to use.

Sure. I did not use it because this API was unstable back then (it had
just been created). Nowadays it surely can be used.

> 2) Should we divide mogrify() into small independent functions? Because
> I think the functions of mogrify() is too many. The source code of
> mogrify is too long (more than 1000 lines).

You mean to modularize the C code? Yes, that should be done.

> 3) Should we integrate Animal library into SIP? The independence of
> Animal may add extra difficulty to port to other platforms.

Actually it simplifies the port process because you can just port
Animal without needing to compile any Scilab module. And, after that,
you port SIP.


Other things that could be done are:

- Put SIP into CVS (another developer should be doing that but I have
not heard from him in a week or so). For this, first we have to put
the simple toolbox into CVS (just to get some practice). After all
developers approve the simple toolbox CVS repository, then we move on
to SIP and Animal.

- Release a new Unix source and binary (version 0.4.0). The current
version is a release candidate. This would give you experience in
making releases.

Of course, you could do more fun activities such as programming algorithms,
that is totally up to you. But the above tasks are the most important
for us currently.

thanks for your disposition,
and always feel free to ask any questions to the list.
--=20
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA

[SIP-devel] I just join the SIP mailing list

[Zhang C. <ch...@ma...>]

Hi, SIP developers!

    I'm so glad to join the SIP mailing list. I want to do something for 
SIP. I'm reading the SIP source code recently, and have had a basic 
understanding of the structure of SIP. Now I'm doing some small changes 
of source code in order to have a better understanding of the interfaces 
among SIP, Animal and Scilab.
    Thanks for Ricardo's enthusiastic reply, if you need me to do some 
work for Windows port, just let me know. What I want to do is to involve 
SIP development as soon as possible.
    After a rough reading of source code, I have some immature ideas 
about SIP as follows:
1) Should we adopt MagickWand API instead of the MagickCore API? Since 
MagickWand API is easier to use.
2) Should we divide mogrify() into small independent functions? Because 
I think the functions of mogrify() is too many. The source code of 
mogrify is too long (more than 1000 lines).
3) Should we integrate Animal library into SIP? The independence of 
Animal may add extra difficulty to port to other platforms.

    Looking forward to anyone's reponse:-)

[SIP-devel] CVS

[Ricardo F. <rf...@gm...>]

Hi,

The latest sip-dev release is at:
https://sourceforge.net/project/showfiles.php?group_id=3D68055&package_id=
=3D67061&release_id=3D340126

Are you familiar with how automake/autoconf works?
Do not forget that in the CVS there is no configure script; only
configure.ac goes,
and you need a script to "bootstrap" (i.e. generate the configure
script). This script
is named "bootstrap" in the sip-dev source code, but I suggest you
rename it to autogen.sh, which is more standard among open source
software.

The way this works is that, when you checkout code from CVS, you must
run autogen.sh, and only then run ./configure.

Oh, and have your linux box updated with the latest autotools.

thanks again
--
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA

Re: [SIP-devel] CVS

[Ricardo F. <rf...@gm...>]

Hi Angus,

Here are the steps to f follow:



- yes, read the CVS doc in sourceforge

- first import the simple toolbox into CVS and lets test it=20
 ('Simple' is a dummy scilab toolbox whose file
      structure is similar to SIP)

http://sourceforge.net/project/showfiles.php?group_id=3D68055&package_id=3D=
83851

- after we approve that, you can move on put the code from the
following sip-devel release into CVS (sip-dev-0.4.0-rc2-alpha3):


I guess you already have access permission to everything. If not, let me kn=
ow.
thank you very much,
Ricardo.

On 7/5/05, Angus Errington <aer...@vi...> wrote:
> Hi Ricardo,
>=20
> What release would you like imported to CVS? Do you have the latest
> version which is not posted yet?
>=20
> Let me know. It looks like a simple matter to get CVS up and working.
>=20
> cheers,
>=20
> Angus
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic=
k
> _______________________________________________
> SIPtoolbox-devel mailing list
> SIP...@li...
> https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel
>=20


--=20
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA

[SIP-devel] CVS

[Angus E. <aer...@vi...>]

Hi Ricardo,

What release would you like imported to CVS? Do you have the latest
version which is not posted yet?

Let me know. It looks like a simple matter to get CVS up and working.

cheers,

Angus

Re: [SIP-devel] Developers needed

[Angus E. <aer...@vi...>]

Hi Ricardo,

I can look into getting CVS working, as it sounds like a good place to
start.  I assume reading the sourceforge documentation is the first thing
to do?

Thanks,

Angus

On Mon, 4 Jul 2005, Ricardo Fabbri wrote:

> Hi Angus,
>
> I will update the TODO list very shortly.
>
> I would suggest the following steps before any actual coding of new features:
>
> - put SIP sourcecode under CVS
> - make a new sourcecode + Linux release (the current one is a release candidate)
> - finally, build the code under Windows and find a good way to install it
>     - I have detailed instructions on this; will post it shortly.
>
>
> Of course, if you are not willing to undertake any of these tasks, you
> can still do anything in the todo lists or anything you want yourself,
> although the priorities are listed above and the project will not
> evolve considerably without having them done.
>
> Please tell me if you have interest in any of the tasks above, or if
> you'd rather do something else, which might be more fun but less
> important.
>
>
> On 7/1/05, Angus Errington <aer...@vi...> wrote:
> > Hello,
> >
> > I am interested in helping out with this project to a greater extent and
> > would welcome the opportunity to become more involved.
> >
> > My research (my Master's) does not currently deal with image processing,
> > but I am still actively exploring and learning more about the subject.
> > Also, I am doing more C programming and Scilab than I have done before and
> > have learned a great deal.
> >
> > It might be a good idea for us to discuss exactly what are the priorities
> > and goals we wish to accomplish in the next few months/year.  I have gone
> > over the tasks section on sourceforge and currently, it is quite out of
> > date; it might be a good idea to re-evaluate where this project is
> > going. Just a thought.
> >
> > I would like to help out in a more concrete role. Questions or comments
> > about my background and anything else are most welcome.
> >
> > Hope all are doing well.
> >
> > cheers,
> >
> >
> > Angus Errington
> >
> >
> >
> >
> >
> > On Tue, 7 Jun 2005, Ricardo Fabbri wrote:
> >
> > > Hi, all,
> > >
> > > I know it has been quite a long time without any news, sorry.
> > > We are in need of an new active developer/administrator for SIP. If
> > > you are interested please sign up to the developers mailing list and
> > > present yourself.  I am not leaving SIP development, but will help
> > > manage it and participate.
> > >
> > > Unfortunately, since I moved to the USA I could not find any time to
> > > significantly work on SIP. The main reason is that I have not been
> > > using Scilab for my own research, so there is no way I could spare
> > > time for it. I like my new research group very much, but they don't
> > > rely on Scilab as much as my old group.  So it is a very slow process
> > > to get them to know it and eventually use it.
> > >
> > > We currently work with C++ using http://vxl.sf.net for image
> > > processing. Since C++ is way more time-consuming to program than
> > > Scilab for most numerical computing, I am trying to convince people
> > > (specially my advisor) to take a glance at Scilab.  And in the process
> > > I have to tell them why Scilab and not Matlab, the advantages of open
> > > source, etc. It would be nice to gather stories of Matlab to Scilab
> > > migration around the world, and how to convince people to do it. One
> > > thing people always complain is that Scilab is not GPL. People are
> > > very paranoid about this. I was informed that Scilab 4.0 is planned to
> > > have a new license, GPL or LGPL. That is very good news. (it is taking
> > > long because some code is having to be rewritten to be
> > > GPL-compatible).
> > >
> > > Anyway, I am currently only passively supporting the SIP Unix SOURCE
> > > version.  The rest I simply cannot touch for now. I've been extremely
> > > busy, and finally realized I am going to be like this at least for the
> > > near future.  I just cannot do everything (home page, binary packages,
> > > documentation, review contributions, give support, etc).
> > >
> > > Frankly it is quite hard to achieve the same level of quality and
> > > productivity we used to have in SIP a year ago. We need a careful
> > > solution that guarantees no loss of quality. On the other hand the
> > > project cannot be stalled forever.
> > >
> > > Recently, I was asked:
> > >
> > > > We really need to have a Windows version of SIP for Scilab 3.0 and
> > > > more. Do you plan to have one?
> > >
> > > I started one but cannot finalize it myself, at least for the next few
> > > months. Whenever I work on SIP it is either for support (of the unix
> > > version) or for actual coding of image processing and writing
> > > documentation. I was able to port SIP for windows using MinGW
> > > (www.mingw.org). It actually works, but requires so many tricks and
> > > hacks, that I did not have time to find a way to actually make a
> > > windows install executable that would smoothly install on all windows
> > > versions (from 95 to XP). Each windows version needs its own tweaks
> > > for e.g.  locating DLLs and imagemagick configuration files. As I
> > > don't program nor use windows, it is hard to find time for this.
> > >
> > > Anyway, I have detailed documentation on my (hacky) windows port and
> > > can provide it for anybody upon request. I might soon provide a
> > > webpage on this.
> > >
> > > best regards,
> > > --
> > > Ricardo Fabbri
> > >
> > > PhD Student in Computer Engineering / Computer Vision
> > > LEMS - Laboratory for Engineering Man-Machine Systems
> > > Brown University, USA
> > >
> > >
> > > --
> > > Ricardo Fabbri
> > >
> > > PhD Student in Computer Engineering / Computer Vision
> > > LEMS - Laboratory for Engineering Man-Machine Systems
> > > Brown University, USA
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
> > > a projector? How fast can you ride your desk chair down the office luge track?
> > > If you want to score the big prize, get to know the little guy.
> > > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
> > > _______________________________________________
> > > SIPtoolbox-devel mailing list
> > > SIP...@li...
> > > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel
> > >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > SIPtoolbox-devel mailing list
> > SIP...@li...
> > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel
> >
>
>
> --
> Ricardo Fabbri
>
> PhD Student in Computer Engineering / Computer Vision
> LEMS - Laboratory for Engineering Man-Machine Systems
> Brown University, USA
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Fi

[SIP-devel] windows port

[Ricardo F. <rf...@gm...>]

Hi all,

I wrote a  webpage for the SIP windows port:
http://siptoolbox.sourceforge.net/devel/windows-port.php

I was able to compile and install SIP under windows, but I didn't have
time to pack everything into an installable package that would work
under all windows versions.

Happy 4th of July :-P
cheers,
--=20
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA

[SIP-devel] Fwd: Compiling SIP on Mac

[Ricardo F. <rf...@gm...>]

Hi, all,

Pierre Mathieu had managed to compile SIP under Macintosh.
He said he had to change a linker flag in Makefile.am
In the future we must automate this based on results of
the configure script.
--
Ricardo.


---------- Forwarded message ----------
From: Pierre Mathieu <ma...@i3...>
Date: Jun 21, 2005 4:47 AM
Subject: Re: Compiling SIP



Le 1 juin 05, =E0 07:02, Ricardo Fabbri a =E9crit :

> Hi Pierre,
>
> Did you use the configure script?
> if affirmative, send me the file config.log
>
>
> It could be, also, that your system deals differently than linux
> regarding shared libraries containing undefined symbols. The SIP
> library is made to load into scilab. So there are symbols that are
> _not_ defined in SIP but which will be defined when you load the lib
> into Scilab. These are exactly the symbols your linker is complaining
> about. So what you need is a flag to let undefined symbols exist,
> somehow. I don't know how to do this in MacOS. Maybe -no-undefined
> flag, I'm not sure.
>

Thank you for your response.
I didn't know the meaning of the  "-no-undefined  " modifier of the ld
command in the Makefile.am .

Although the compiler is gcc  on the Mac, ld is not the same as on
Linux.

To let undefined symbols at the link time, the option is then
"-undefined warning "  which transforms errors in warnings. On 10.3 it
can be used "-undefined dynamic_lookup ".

In any case it is working very well now.
I thank you again for your help and for you great work in SIP.

best regards

Pierre Mathieu

Re: [SIP-devel] Developers needed

[Ricardo F. <rf...@gm...>]

Hi Angus,

I will update the TODO list very shortly.

I would suggest the following steps before any actual coding of new feature=
s:

- put SIP sourcecode under CVS
- make a new sourcecode + Linux release (the current one is a release candi=
date)
- finally, build the code under Windows and find a good way to install it
    - I have detailed instructions on this; will post it shortly.=20


Of course, if you are not willing to undertake any of these tasks, you
can still do anything in the todo lists or anything you want yourself,
although the priorities are listed above and the project will not
evolve considerably without having them done.

Please tell me if you have interest in any of the tasks above, or if
you'd rather do something else, which might be more fun but less
important.


On 7/1/05, Angus Errington <aer...@vi...> wrote:
> Hello,
>=20
> I am interested in helping out with this project to a greater extent and
> would welcome the opportunity to become more involved.
>=20
> My research (my Master's) does not currently deal with image processing,
> but I am still actively exploring and learning more about the subject.
> Also, I am doing more C programming and Scilab than I have done before an=
d
> have learned a great deal.
>=20
> It might be a good idea for us to discuss exactly what are the priorities
> and goals we wish to accomplish in the next few months/year.  I have gone
> over the tasks section on sourceforge and currently, it is quite out of
> date; it might be a good idea to re-evaluate where this project is
> going. Just a thought.
>=20
> I would like to help out in a more concrete role. Questions or comments
> about my background and anything else are most welcome.
>=20
> Hope all are doing well.
>=20
> cheers,
>=20
>=20
> Angus Errington
>=20
>=20
>=20
>=20
>=20
> On Tue, 7 Jun 2005, Ricardo Fabbri wrote:
>=20
> > Hi, all,
> >
> > I know it has been quite a long time without any news, sorry.
> > We are in need of an new active developer/administrator for SIP. If
> > you are interested please sign up to the developers mailing list and
> > present yourself.  I am not leaving SIP development, but will help
> > manage it and participate.
> >
> > Unfortunately, since I moved to the USA I could not find any time to
> > significantly work on SIP. The main reason is that I have not been
> > using Scilab for my own research, so there is no way I could spare
> > time for it. I like my new research group very much, but they don't
> > rely on Scilab as much as my old group.  So it is a very slow process
> > to get them to know it and eventually use it.
> >
> > We currently work with C++ using http://vxl.sf.net for image
> > processing. Since C++ is way more time-consuming to program than
> > Scilab for most numerical computing, I am trying to convince people
> > (specially my advisor) to take a glance at Scilab.  And in the process
> > I have to tell them why Scilab and not Matlab, the advantages of open
> > source, etc. It would be nice to gather stories of Matlab to Scilab
> > migration around the world, and how to convince people to do it. One
> > thing people always complain is that Scilab is not GPL. People are
> > very paranoid about this. I was informed that Scilab 4.0 is planned to
> > have a new license, GPL or LGPL. That is very good news. (it is taking
> > long because some code is having to be rewritten to be
> > GPL-compatible).
> >
> > Anyway, I am currently only passively supporting the SIP Unix SOURCE
> > version.  The rest I simply cannot touch for now. I've been extremely
> > busy, and finally realized I am going to be like this at least for the
> > near future.  I just cannot do everything (home page, binary packages,
> > documentation, review contributions, give support, etc).
> >
> > Frankly it is quite hard to achieve the same level of quality and
> > productivity we used to have in SIP a year ago. We need a careful
> > solution that guarantees no loss of quality. On the other hand the
> > project cannot be stalled forever.
> >
> > Recently, I was asked:
> >
> > > We really need to have a Windows version of SIP for Scilab 3.0 and
> > > more. Do you plan to have one?
> >
> > I started one but cannot finalize it myself, at least for the next few
> > months. Whenever I work on SIP it is either for support (of the unix
> > version) or for actual coding of image processing and writing
> > documentation. I was able to port SIP for windows using MinGW
> > (www.mingw.org). It actually works, but requires so many tricks and
> > hacks, that I did not have time to find a way to actually make a
> > windows install executable that would smoothly install on all windows
> > versions (from 95 to XP). Each windows version needs its own tweaks
> > for e.g.  locating DLLs and imagemagick configuration files. As I
> > don't program nor use windows, it is hard to find time for this.
> >
> > Anyway, I have detailed documentation on my (hacky) windows port and
> > can provide it for anybody upon request. I might soon provide a
> > webpage on this.
> >
> > best regards,
> > --
> > Ricardo Fabbri
> >
> > PhD Student in Computer Engineering / Computer Vision
> > LEMS - Laboratory for Engineering Man-Machine Systems
> > Brown University, USA
> >
> >
> > --
> > Ricardo Fabbri
> >
> > PhD Student in Computer Engineering / Computer Vision
> > LEMS - Laboratory for Engineering Man-Machine Systems
> > Brown University, USA
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you s=
hotput
> > a projector? How fast can you ride your desk chair down the office luge=
 track?
> > If you want to score the big prize, get to know the little guy.
> > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
> > _______________________________________________
> > SIPtoolbox-devel mailing list
> > SIP...@li...
> > https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel
> >
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic=
k
> _______________________________________________
> SIPtoolbox-devel mailing list
> SIP...@li...
> https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel
>=20


--=20
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA

[SIP-devel] test 1

[Ricardo F. <rf...@gm...>]

this is just a test,=20
I appologize for the inconvenience.

--=20
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA

[SIP-devel] test A

[Ricardo F. <rf...@gm...>]

this is a test, sorry for the inconvenience.
--=20
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA

Re: [SIP-devel] Developers needed

[Angus E. <aer...@vi...>]

Hello,

I am interested in helping out with this project to a greater extent and
would welcome the opportunity to become more involved.

My research (my Master's) does not currently deal with image processing,
but I am still actively exploring and learning more about the subject.
Also, I am doing more C programming and Scilab than I have done before and
have learned a great deal.

It might be a good idea for us to discuss exactly what are the priorities
and goals we wish to accomplish in the next few months/year.  I have gone
over the tasks section on sourceforge and currently, it is quite out of
date; it might be a good idea to re-evaluate where this project is
going. Just a thought.

I would like to help out in a more concrete role. Questions or comments
about my background and anything else are most welcome.

Hope all are doing well.

cheers,


Angus Errington





On Tue, 7 Jun 2005, Ricardo Fabbri wrote:

> Hi, all,
>
> I know it has been quite a long time without any news, sorry.
> We are in need of an new active developer/administrator for SIP. If
> you are interested please sign up to the developers mailing list and
> present yourself.  I am not leaving SIP development, but will help
> manage it and participate.
>
> Unfortunately, since I moved to the USA I could not find any time to
> significantly work on SIP. The main reason is that I have not been
> using Scilab for my own research, so there is no way I could spare
> time for it. I like my new research group very much, but they don't
> rely on Scilab as much as my old group.  So it is a very slow process
> to get them to know it and eventually use it.
>
> We currently work with C++ using http://vxl.sf.net for image
> processing. Since C++ is way more time-consuming to program than
> Scilab for most numerical computing, I am trying to convince people
> (specially my advisor) to take a glance at Scilab.  And in the process
> I have to tell them why Scilab and not Matlab, the advantages of open
> source, etc. It would be nice to gather stories of Matlab to Scilab
> migration around the world, and how to convince people to do it. One
> thing people always complain is that Scilab is not GPL. People are
> very paranoid about this. I was informed that Scilab 4.0 is planned to
> have a new license, GPL or LGPL. That is very good news. (it is taking
> long because some code is having to be rewritten to be
> GPL-compatible).
>
> Anyway, I am currently only passively supporting the SIP Unix SOURCE
> version.  The rest I simply cannot touch for now. I've been extremely
> busy, and finally realized I am going to be like this at least for the
> near future.  I just cannot do everything (home page, binary packages,
> documentation, review contributions, give support, etc).
>
> Frankly it is quite hard to achieve the same level of quality and
> productivity we used to have in SIP a year ago. We need a careful
> solution that guarantees no loss of quality. On the other hand the
> project cannot be stalled forever.
>
> Recently, I was asked:
>
> > We really need to have a Windows version of SIP for Scilab 3.0 and
> > more. Do you plan to have one?
>
> I started one but cannot finalize it myself, at least for the next few
> months. Whenever I work on SIP it is either for support (of the unix
> version) or for actual coding of image processing and writing
> documentation. I was able to port SIP for windows using MinGW
> (www.mingw.org). It actually works, but requires so many tricks and
> hacks, that I did not have time to find a way to actually make a
> windows install executable that would smoothly install on all windows
> versions (from 95 to XP). Each windows version needs its own tweaks
> for e.g.  locating DLLs and imagemagick configuration files. As I
> don't program nor use windows, it is hard to find time for this.
>
> Anyway, I have detailed documentation on my (hacky) windows port and
> can provide it for anybody upon request. I might soon provide a
> webpage on this.
>
> best regards,
> --
> Ricardo Fabbri
>
> PhD Student in Computer Engineering / Computer Vision
> LEMS - Laboratory for Engineering Man-Machine Systems
> Brown University, USA
>
>
> --
> Ricardo Fabbri
>
> PhD Student in Computer Engineering / Computer Vision
> LEMS - Laboratory for Engineering Man-Machine Systems
> Brown University, USA
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
> a projector? How fast can you ride your desk chair down the office luge track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
> _______________________________________________
> SIPtoolbox-devel mailing list
> SIP...@li...
> https://lists.sourceforge.net/lists/listinfo/siptoolbox-devel
>

[SIP-devel] Developers needed

[Ricardo F. <rf...@gm...>]

Hi, all,

I know it has been quite a long time without any news, sorry.
We are in need of an new active developer/administrator for SIP. If
you are interested please sign up to the developers mailing list and
present yourself.  I am not leaving SIP development, but will help
manage it and participate.

Unfortunately, since I moved to the USA I could not find any time to
significantly work on SIP. The main reason is that I have not been
using Scilab for my own research, so there is no way I could spare
time for it. I like my new research group very much, but they don't
rely on Scilab as much as my old group.  So it is a very slow process
to get them to know it and eventually use it.

We currently work with C++ using http://vxl.sf.net for image
processing. Since C++ is way more time-consuming to program than
Scilab for most numerical computing, I am trying to convince people
(specially my advisor) to take a glance at Scilab.  And in the process
I have to tell them why Scilab and not Matlab, the advantages of open
source, etc. It would be nice to gather stories of Matlab to Scilab
migration around the world, and how to convince people to do it. One
thing people always complain is that Scilab is not GPL. People are
very paranoid about this. I was informed that Scilab 4.0 is planned to
have a new license, GPL or LGPL. That is very good news. (it is taking
long because some code is having to be rewritten to be
GPL-compatible).

Anyway, I am currently only passively supporting the SIP Unix SOURCE
version.  The rest I simply cannot touch for now. I've been extremely
busy, and finally realized I am going to be like this at least for the
near future.  I just cannot do everything (home page, binary packages,
documentation, review contributions, give support, etc).

Frankly it is quite hard to achieve the same level of quality and
productivity we used to have in SIP a year ago. We need a careful
solution that guarantees no loss of quality. On the other hand the
project cannot be stalled forever.

Recently, I was asked:

> We really need to have a Windows version of SIP for Scilab 3.0 and
> more. Do you plan to have one?

I started one but cannot finalize it myself, at least for the next few
months. Whenever I work on SIP it is either for support (of the unix
version) or for actual coding of image processing and writing
documentation. I was able to port SIP for windows using MinGW
(www.mingw.org). It actually works, but requires so many tricks and
hacks, that I did not have time to find a way to actually make a
windows install executable that would smoothly install on all windows
versions (from 95 to XP). Each windows version needs its own tweaks
for e.g.  locating DLLs and imagemagick configuration files. As I
don't program nor use windows, it is hard to find time for this.

Anyway, I have detailed documentation on my (hacky) windows port and
can provide it for anybody upon request. I might soon provide a
webpage on this.

best regards,
--
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA


--=20
Ricardo Fabbri

PhD Student in Computer Engineering / Computer Vision
LEMS - Laboratory for Engineering Man-Machine Systems
Brown University, USA

[SIP-devel] new function mkgaussfilter

[jocelyn.druel <joc...@li...>]

Hi everybody,
I'm still alive but I had many other things to do other than SIP.

I hope the SIP project is still alive with Ricardo's move to the US.

Well, here, as student projects are going on, I come back to SIP to easily 
prototype some vision operations.

In order to ease the "blurr mask treatement" (I don't know if it's the correct 
translation for "traitement par masque flou"), I coded a simple function to 
create gaussian kernels which are used in the blurring process (with imconv).

Here's the function, manpage and a photo from jupiter to test.

Best regards to all 
Jocelyn

-- 
Powered by Linux

Re: [SIP-devel] build trouble, MacOS 10.3

[Scott D. <sd...@sc...>]

Hi --

I'm trying to resume my efforts to port SIP to MacOS 10.3 (I'm cautiously
optimistic...).  But I must confess I've run into a problem (I think just
a small one) just in compilation; here's the most immediately relevant
portion of gcc output:

if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.
-I/sw/lib/scilab-2.7/routines  -g -O2 -W -Wall -Wno-implicit-int
-I/usr/local/include -I/usr/local/include -I/usr/local/include/freetype2
-D_REENTRANT -I/usr/local/include/libxml2  -I/usr/local/include
-I/usr/local/include/freetype2 -D_REENTRANT -I/usr/local/include/libxml2
-MT mogrify_int.lo -MD -MP -MF ".deps/mogrify_int.Tpo" -c -o
mogrify_int.lo mogrify_int.c; \
then mv -f ".deps/mogrify_int.Tpo" ".deps/mogrify_int.Plo"; else rm -f
".deps/mogrify_int.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I. -I/sw/lib/scilab-2.7/routines -g -O2 -W
-Wall -Wno-implicit-int -I/usr/local/include -I/usr/local/include
-I/usr/local/include/freetype2 -D_REENTRANT -I/usr/local/include/libxml2
-I/usr/local/include -I/usr/local/include/freetype2 -D_REENTRANT
-I/usr/local/include/libxml2 -MT mogrify_int.lo -MD -MP -MF
.deps/mogrify_int.Tpo -c mogrify_int.c  -fno-common -DPIC -o
.libs/mogrify_int.o
mogrify_int.c: In function `check_argv_validity':
mogrify_int.c:1299: error: `UndefinedCompressionQuality' undeclared (first
use in this function)

Indeed, I can find no evidence of UndefinedCompressionQuality being
defined in SIP or ImageMagick, but I'm not exactly sure where to be
looking for it.  Can you give me a hint about where it's supposed to be
defined?

Thanks
Scott Dexter


On Tue, 17 Feb 2004, Ricardo Fabbri wrote:

> On Mon, 16 Feb 2004, Scott Dexter wrote:
> 
> > ld: Undefined symbols:
> > _com_
> > _sci_gateway
> > _Scierror
> > _checklhs_
> > _checkrhs_
> > _createvarfromptr_
> > (..)
> 
> Hi,
> I can't see how to solve the problem for you, but here's some
> information:
> 
> SIP generates a dynamic library called libsip.so, and this library has
> some undefined symbols ON PURPOSE, since these symbols are to be
> defined by Scilab when SIP is loaded into it.
> 
> Your problem is very similar to what I find on Windows: I don't know
> how to build shared libraries with undefined symbols under MacOSX or
> Windows.
> 
> This is, most certainly, a libtool issue. The flag '-no-undefined'
> is used to do exactly this: tell the system that *all* symbols will be
> defined at link time (that is, when scilab loads the library).
> 
> My guess is that -no-undefined is not working under MacOSX for some
> reason I don't understand. My second guess is that libtool is working
> fine but I don't know enough about it.
> 
> Unfortunately, I really don't have much experience/knowledge about
> shared libraries nor MacOSX to be able to help you further, but I am
> really interested in your problem.
> 
> best,
> Ricardo.
> 
> --
>   Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil.
>   WEB: cyvision.if.sc.usp.br/~rfabbri   ICQ: 208974212
> 
>   "With pain and suddeness is how Real Offsprings are born. But they
>   must result from intense pleasure and a long period of development."
> 

[SIP-devel] a corrected help page

[DRUEL J. <joc...@li...>]

Hi,
There were words missing in this help page.
It's now corrected.
Best
Jocelyn
-- 
Powered by Linux

[SIP-devel] interferometry_gui

[DRUEL J. <joc...@li...>]

Hi,
Having a look at the new SIP version (which seems to work very fine), I made 
some improvements on my interferometry_gui demo.
The problem was mainly with imxprofile: it's necessary to switch to scilab 
old_graphic style (set("old_style","on")) to have a normal behaviour.
Now, the demo switches automatically to this mode.

Something else (if someone can test on his hardware to tell if it works):
in the section "Screen" of XF86Config, I added 2 lines:

    Option      "backing_store"
    Option      "save_unders"

(I found this tip on the Scilab web site).
If it works, we should had a remark in the imxprofile help page.

Something else: the original laser1.jpg is awful (too small). Here is a new 
one to use with the laser beam menu.

Best
Jocelyn

PS: the anouncement of a window version of SIP is a great news: the number of 
people using SIP will probably greatly grow. Congratulations to Ricardo.

-- 
Powered by Linux

[SIP-devel] SIP 0.4.0 Candidate 1

[Ricardo F. <rf...@if...>]

SIP 0.4.0 release candidate 1 is out for public testing. It brings
major new features, read on! Generic sourcecode is available, as well
as an EASY-TO-INSTALL BINARY for GNU/Linux systems. Windows binaries
will be released soon. Grab the new version in the Download section at
http://siptoolbox.sf.net

This list highlights the main changes from 0.3.1 to 0.4.0. Read the
previous changelogs for minor improvements and details.

   + Help files moved to XML/HTML format and were totally revised;
   + NEW hsv2rgb and rgb2hsv functions to convert between RGB images
     and HSV (Hue Saturation Intensity) images.
   + NEW radon and iradon functions
   + NEW sip_set_verbose, sip_quiet and sip_wordy functions to adjust
     the messaging level issued by sip routines. For instance, this
     may be used to stop imread and mogrify from issuing verbose
     messages.
   + NEW sip_setenv to set environment variables.
   + imvariance is now coded in C for efficiency
   + unwrapl and unwrapp functions are now coded in C. unwrapl now
     returns the unwrapped_phase and the phase_jumps.
   + NEW rgbplot function to plot the RGB components of a colormap
   + NEW sip_colormap function
   + FIX to imread: when you read a non-indexed image (such as
     truecolor or binary) with two output parameters, imread crashed
     scilab in some cases. This is now fixed. (thx to )
   + FIX regarding truecolor images in imwrite, imread and mogrify
     functions, by using scilab's new hypermatrix structure.
   + imwrite now supports the "depth" optional argument to set image
     depth. It defaults to 16bpp, but one can now set it to 8bpp.
   + GANDALF is NOT needed anymore for the a source build
   + Animal 0.14.0 or later is required for a source build
   + Virtually any version of ImageMagick is now supported for
     compiling from source (all  versions down to 5.4.2)
   + Both sabcmd and xsltproc are supported to build the help pages;
     SIP will use whichever is available.
   + NEW preliminary imxprofile, wich has some improvements to
     improfile but is not fully functional.
   + INCOMPATIBLE: function angle changed to "getangle"
   + Many other bugfixes and minor improvements

   Main Developers: Ricardo Fabbri and Jocelyn Druel.
   Special Thanks to: Sandro da Silva, Leandro Estrozi, Edson
   Nakamura, Dean Messing, Enrico Segre, Torsten Werner


0.4.0 RC1 (changes from the latest sip-dev)
   + FIXED small syntax error in imroi.sci
   + Binaries are available


Compilation and installation is suited for Linux, but should
workcorrectly in other unix systems. I use Slackware Linux 9.1.
Please report to the list any problems that you see with SIP in other
distros.

You shall install the new SIP version over the older ones
without problems, but if you want, you can remove the old version
like this: in the unix shell, change dir to the old SIP-dev then type
the following:

prompt# make uninstall

Also please comment out any "exec ...loader.sce" instructions from
your ".scilab" startup file before installing a new version.

Enjoy!

Ricardo.

--
  Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil.
  TEL: +55 016 273.9882  CEL: +55 016 9121.9046  ICQ: 208974212

Re: [SIP-devel] sip-dev-20040527-2 and imagemagick

[Ricardo F. <rf...@if...>]

Hi, Jocelyn,

remember that nasty problem about ImageMagick and the latest
SIP-devel?

The reason is that you have two conflicting ImageMagick installations.
Check your include directories for conflicting "includes".

I ran into the same problem. I had wrong magick/*.h files in /usr/local/include
Perhaps you have wrong magick/*.h in /usr/include or in some other
place.

hope you can now compile the new SIP.

PS: new Linux binaries should be under way. I succeeded building windows
toolboxes. The SIP windows version is now under way, if nothing too
much hairy gets on the way.

Ricardo.

On Fri, 11 Jun 2004, DRUEL Jocelyn wrote:

> After problems compiling the development version, I investigated to find that
> ImageMagick-5.5.7 is not enough for it:
> I have the following error:
>
> mogrify_int.c: In function `check_argv_validity':
> mogrify_int.c:1302: `UndefinedCompressionQuality' undeclared (first use in
> this
> function)
> mogrify_int.c:1302: (Each undeclared identifier is reported only once
> mogrify_int.c:1302: for each function it appears in.)
>

[SIP-devel] New devel release

[Ricardo F. <rf...@if...>]

In this release, there are new functions to convert RGB to/from HSV
images and colormaps. The Radon transform is now available. We also
fixed C functions with respect of truecolor images, by using Scilab's
new hypermatrix structure. Therefore this version now works with
Scilab 3.0. There are many other changes, making this a strong
candidate for the next SIP stable version. Download the new version at
http://siptoolbox.sf.net/devel

CHANGES
   + NEW hsv2rgb and rgb2hsv functions to convert between RGB images
     to HSV colorspace images. It also works for colormaps.  (thx.
     Sandro da Silva)
   + NEW radon and iradon functions (by Leandro Estrozi)
   + FIX regarding truecolor images in imwrite, imread and mogrify
     functions, by using scilab's new hypermatrix structure.
   + NEW sip_set_verbose, sip_quiet and sip_wordy functions to adjust
     the messaging level issued by sip routines. For instance, this
     may be used to stop imread and mogrify from issuing verbose
     messages, which are very annoying when these functions are used
     inside loops.
   + NEW sip_setenv to set environment variables.
   + unwrapl and unwrapp functions are now coded in C (by Jocelyn
     Druel). unwrapl now returns the unwrapped_phase and the
     phase_jumps to be consistent with the unwrapp function.
   + INCOMPATIBLE: improvements to imxprofile, new parameters
   + NEW threshold parameter for unwrapp
   + improvements to the interferometry GUI - Gamma correction on
     colormaps, use of imxprofile instead of improfile, and more.
   + INCOMPATIBLE: function angle changed to "getangle" because
     "angle" is too simple and often conflicts with user variables.
   + dummy builder.sce file so that Scilab includes SIP in the
     toolboxes menu (thx. Enrico Segre).
   + many fixes and improvements to help pages

Compilation and installation is suited for Linux, but should
workcorrectly in other unix systems. I use Slackware Linux 9.1.
Please report to the list any problems that you see with SIP in other
distros.

You shall install the new SIP version over the older ones
without problems, but if you want, you can remove the old version
like this: in the unix shell, change dir to the old SIP-dev then type
the following:

prompt# make uninstall

Also please comment out any "exec ...loader.sce" instructions from
your ".scilab" startup file before installing a new version.

Enjoy!
Ricardo.

--
  Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil.
  TEL: +55 016 273.9882  CEL: +55 016 9121.9046  ICQ: 208974212

Re: [SIP-devel] SIP windows version and other stuff

[Vitor V. A. S. <vi...@cn...>]

	Congratulations!
	Energy to work hard and hardest. :-)
	Greetings,

-- Vitor Vasconcelos Araujo Silva

   Tecnologista
   .Comissao Nacional de Energia Nuclear - CNEN
   Mestrando
   .Laboratorio de Computacao Grafica - LCG/COPPE/UFRJ

   vi...@cn...

"The difficult in life is the choice."
		- George Moore (1900)

Re: [SIP-devel] sip-dev-20040527-2 and imagemagick

[Ricardo F. <rf...@if...>]

Hi, Jocelyn,

your problem with ImageMagick 5.5.7 seems very strange. I checked you
log files and the tests on your system went correctly, except that the
configure script didn't do what it was programmed to.

I'm a bit clueless. Lets track down the problem by steps.
First, tell me your system specs:
Whats your Linux distro? You are using the ImageMagick 5.5.7 that came with it?

Second, try to download SIP again, maybe you have a slightly older
version that I had uploaded by mistake at release time. Please send me
the file "configure".

Anyway, the problem is still very strange, I just can't figure out why
the configure script (which is exactly the same as mine) didn't work.

BTW, did the manpage build with the workaround I proposed in the last email?

kind regards,
Ricardo.

[SIP-devel] SIP windows version and other stuff

[Ricardo F. <rf...@if...>]

Hello, all,

I know I have been taking a long time to answer emails, requests,
contributions, and to update the windows version of SIP (Scilab
Image processing Toolbox).

But I am glad to give you a good excuse. This August I am going to
start PhD at Brown University, USA, on digital image analysis!  I was
awarded financial support from the Brazilian govenment to
work with Drs. Benjamin Kimia and F. Leymarie, at the Computer
Engineering department. In the meantime, I will be very busy (and
happy) finishing my MSc dissertation and packing things up.

Therefore, I've only been able to maintain the Unix version of SIP; the
windows version will have to wait a bit, although I will be trying to do
something in every tiny stretch of time that I can get. We need
contributors if SIP is to be ported to Windows sooner than I can.
My intensive activity on SIP shall return by September and hopefully
continue for a long time. In the meantime, I will be trying to
answer emails and requests as possible.

Another good news is that I am a contribution memeber of the new
Scilab consortium. This means that the voice of the SIP community is
now stronger to decide Scilab issues. Something I will be striving
for is that Scilab moves to GPL or LGPL (keeping the INRIA/ENPC copyright).

cheers,
Ricardo.

--
  Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil.
  TEL: +55 016 273.9882  CEL: +55 016 9121.9046  ICQ: 208974212

Re: [SIP-devel] sip-dev-20040527-2 and imagemagick

[DRUEL J. <joc...@li...>]

Le Lundi 14 Juin 2004 17:02, vous avez écrit :
> Hi, Jocelyn,
>
> > After problems compiling the development version, I investigated to find
> > that ImageMagick-5.5.7 is not enough for it:
>
> On the contrary.. it had been written so that it will now work with
> virtually any version of imagemagick. I just compiled it with
> ImageMagick 5.5.7 without problems.
>
> Please make sure you are really using the 20040527-2 version.
> If you are, please send me your configure.log and configure.ac files.
>
Here they are.

best
Jocelyn

-- 
Powered by Linux

Re: [SIP-devel] sip-dev-20040527-2 and imagemagick

[Ricardo F. <rf...@if...>]

Hi, Jocelyn,

> After problems compiling the development version, I investigated to find that
> ImageMagick-5.5.7 is not enough for it:

On the contrary.. it had been written so that it will now work with
virtually any version of imagemagick. I just compiled it with
ImageMagick 5.5.7 without problems.

Please make sure you are really using the 20040527-2 version.
If you are, please send me your configure.log and configure.ac files.

>
>  man pages are not built (I  have a Scilab prompt on the console).

This happened with me because I installed a new animal library and
_uninstalled_ the old one, but the old one is required by the old
toolbox.

You may just remove your previous "exec loader.sce" from ~/.scilab and
re-run "make" inside the sip source dir.

Sorry, I must find a way to not require the user to do this.
Suggestions are welcome.

best,
Ricardo.

--
  Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil.
  TEL: +55 016 273.9882  CEL: +55 016 9121.9046  ICQ: 208974212