<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 02/17/2016 02:24 PM, Philipp
Mühlmann a écrit :<br>
</div>
<blockquote
cite="mid:CACf7ODt9PYpUZu-hrf35rDX5WMBe9WAghfnfqEW7ScsgZiawAA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Quote:</div>
<div><br>
</div>
<div>''Concerning the first issue, image processing with scilab,
I think a basic core image support should be part of scilab.''</div>
<div><br>
</div>
<div>Well, agreed to this.</div>
<div><br>
</div>
<div><br>
</div>
<div>However here a different approach:</div>
<div><br>
</div>
<div>I wonder if it couldn't be helpful to connect Scilab with a
native Image processing Programm...like Inkscape.</div>
<div><br>
</div>
<div>Why trying to convert Scilab into a image processing tool,
while there are dedicated programs for it?</div>
<div><br>
</div>
<div>Yes I know: It might be better to have everything in one
package, beeing independent from other Software.</div>
<div>As I use IPD very much I'm glad to have this available.</div>
<div><br>
</div>
<div>I just have to think about a discussion about one
complaining about Images, trying to manage his images with
MS-Word instead of using a proper Software.</div>
<div><br>
</div>
<div><br>
</div>
<div>Basic Image processing functions like rotate, shift, etc.
might be done using the "dos" command and Inkscape as well.</div>
</div>
</blockquote>
<br>
Hi Philipp,<br>
<br>
I think we are not talking about the same kind of processing here.<br>
Image processing in the context of Scilab is more opencv-like than
inkscape-like.<br>
I want to import into scilab an image (3*8bits RGB bmp, 3*32bits RGB
bmp, 16bits grayscale TIFF, ...) and map it to the most relevant
variable in scilab (HxWX3 hypermatrix of uint8 for HxW 8bitRGB bmp,
...), in order to do some number crunching on the data contained in
the image.<br>
It's not really cropping, rotating or some sort of "photoshoping"
that I need, it's basically a way to "process" (as in signal
processing).<br>
<br>
Cheers,<br>
<br>
Antoine<br>
<br>
<blockquote
cite="mid:CACf7ODt9PYpUZu-hrf35rDX5WMBe9WAghfnfqEW7ScsgZiawAA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div><br>
</div>
<div>BR</div>
<div>Philipp</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-02-17 12:21 GMT+01:00 Alasdair
McAndrew <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:amca01@gmail.com" target="_blank">amca01@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">The poor quality of image processing
toolboxes is what turned me off Scilab to GNU Octave,
which has a very good imaging toolbox. Or Python, which
with its various imaging libraries and scientific/numeric
libraries is now a serious competitor for matrix-oriented
software like Matlab/Scilab/Octave. I've written two
image processing textbooks, and at no time has Scilab ever
been a serious contender for their software.<br>
</div>
<div class="gmail_extra">
<div>
<div class="h5"><br>
<div class="gmail_quote">On Wed, Feb 17, 2016 at 7:20
PM, <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:amonmayr@laas.fr" target="_blank">amonmayr@laas.fr</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px
0px 0px
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div bgcolor="#FFFFFF" text="#000000"><span>
<div>Le 02/17/2016 01:23 AM, AlvaroOsvaldo a
écrit :<br>
</div>
<blockquote type="cite">I am worried, in
previous versions of scilab, I implemented a
medium project for scientific computing with
scilab at that time had many memory leaks
and had been a nightmare. With the new
updates that was fixed and this much better.
But now I am implementing another project
involving massive image processing. And the
three atoms for this, one does not work, one
does not load images but the manual says
they can do, and other charges but leak the
computer's memory and it took me longer
skirting the problem than implementing the
solution. And worse, because this the system
is much slower than it should. This atom
memory failure it has been known, however,
despite it make impraticable to use the atom
for medium and large projects, makes three
years that no one gets the bug. <a
moz-do-not-send="true"
href="http://forge.scilab.org/index.php/p/IPD/issues/992/"
target="_blank">forge.scilab.org/index.php/p/IPD/issues/992/</a>
There are high expectations with Scilab 6
and I believe we will have a much better
platform. But for what you know, in the
meantime we will run out of many atoms, and
this greatly reduces the possibility of
working in scilab. What is the future of
Scilab? For now, the impression I have is
that the atoms are abandoned and without the
atoms the usefulness of scilab is reduced a
lot. <br>
</blockquote>
<br>
</span> Hi,<br>
<br>
I think there are two issues here:<br>
<br>
1) The sad state of image processing toolbox
with Scilab. It's terrrible. Image processing
with Scilab is a nightmare. Every other language
I use is far better than Scilab in this area
(even extremely young language like Julia offers
a better experience. The 3 toolboxes are either
broken, unmaintained or difficult (or
impossible) to install. And the experience is
even worse under Linux (IPD for example requires
a very old version of opencv to be manually
installed under Linux which is a daunting task
for most user and which introduces many
compatibility issues with other softwares
relying on opencv).<br>
<br>
2) The lack of information on the life (or lack
of life) for a given atoms module. I know some
information is available on the atoms website,
but I've always found it difficult to determine
whether the package was long dead or under
active development. There are some long dead
modules that are still listed alongside with
actively maintained ones and that show excellent
rating. It's a bit confusing.<br>
<br>
Concerning the first issue, image processing
with scilab, I think a basic core image support
should be part of scilab.<br>
<br>
Antoine<br>
<br>
<br>
<br>
<br>
<blockquote type="cite"><span>
<hr width="300" align="left"> View this
message in context: <a
moz-do-not-send="true"
href="http://mailinglists.scilab.org/What-is-the-future-of-Scilab-tp4033471.html"
target="_blank">What is the future of
Scilab?</a><br>
Sent from the <a moz-do-not-send="true"
href="http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html"
target="_blank">Scilab users - Mailing
Lists Archives mailing list archive</a> at
Nabble.com.<br>
<br>
<fieldset></fieldset>
<br>
</span>
<pre>_______________________________________________
users mailing list
<a moz-do-not-send="true" href="mailto:users@lists.scilab.org" target="_blank">users@lists.scilab.org</a>
<a moz-do-not-send="true" href="http://lists.scilab.org/mailman/listinfo/users" target="_blank">http://lists.scilab.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<br>
</div>
<br>
_______________________________________________<br>
users mailing list<br>
<a moz-do-not-send="true"
href="mailto:users@lists.scilab.org"
target="_blank">users@lists.scilab.org</a><br>
<a moz-do-not-send="true"
href="http://lists.scilab.org/mailman/listinfo/users"
target="_blank" rel="noreferrer">http://lists.scilab.org/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
</div>
</div>
<span class="HOEnZb"><font color="#888888">-- <br>
<div>
<div dir="ltr"><img moz-do-not-send="true"
alt="http://www.facebook.com/alasdairmcandrew"
src="https://docs.google.com/uc?id=0B8eumYy7fHJzWVVSUHAza1pYN3c&export=download">
<a moz-do-not-send="true"
href="https://twitter.com/amca01"
target="_blank"><img moz-do-not-send="true"
alt="https://twitter.com/amca01"
src="https://docs.google.com/uc?export=download&id=0B8eumYy7fHJzMUJuWnBfWjBIdUk&revid=0B8eumYy7fHJzenhmd2NGRlIxRituSHFlRjV6WGdLUUNDL2owPQ"></a>
<span><span><img moz-do-not-send="true"
src="https://docs.google.com/uc?export=download&id=0B8eumYy7fHJzQjVVTzBjeGVJOVE&revid=0B8eumYy7fHJzN21BS0xtckJJNlBQTVJEQ29aVWNCNWx0WnpBPQ">
<a moz-do-not-send="true"
href="https://www.linkedin.com/in/alasdair-mcandrew-108178a"
target="_blank"><img moz-do-not-send="true"
src="https://docs.google.com/uc?export=download&id=0B8eumYy7fHJzb21hNW8zSWZFdjQ&revid=0B8eumYy7fHJzSmgrZy9BR25Edm52MHNwWnVqQkVaVVVYSmRVPQ"></a></span></span>
<a moz-do-not-send="true"
href="https://plus.google.com/+AlasdairMcAndrew/posts"
target="_blank"><img moz-do-not-send="true"
src="https://docs.google.com/uc?export=download&id=0B8eumYy7fHJzV1BjWUxuTVNkQ2c&revid=0B8eumYy7fHJzQjBWRS8vblp6TzVzVTZLZmNWbTRyS1YrZkpJPQ"></a><br>
</div>
</div>
</font></span></div>
<br>
_______________________________________________<br>
users mailing list<br>
<a moz-do-not-send="true"
href="mailto:users@lists.scilab.org">users@lists.scilab.org</a><br>
<a moz-do-not-send="true"
href="http://lists.scilab.org/mailman/listinfo/users"
target="_blank" rel="noreferrer">http://lists.scilab.org/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature">There we have the salad.</div>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Antoine Monmayrant LAAS - CNRS
7 avenue du Colonel Roche
BP 54200
31031 TOULOUSE Cedex 4
FRANCE
Tel:+33 5 61 33 64 59
email : <a class="moz-txt-link-abbreviated" href="mailto:antoine.monmayrant@laas.fr">antoine.monmayrant@laas.fr</a>
permanent email : <a class="moz-txt-link-abbreviated" href="mailto:antoine.monmayrant@polytechnique.org">antoine.monmayrant@polytechnique.org</a>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
</pre>
</body>
</html>