date:20201222

Re: [Scilab-users] IPCV upscaling of image

2020-12-22 Thread Claus Futtrup

Hi Philipp

Interesting ... I think this should be part of the help available.
I hope Chin Lun Tan sees this and feel inspired...

Cheers,
Claus

On 21-12-2020 21:54, P M wrote:

Hi Claus,

this works for me:

imgList  =  list();
imgList(1)  =  imread(fullpath(getIPCVpath()  +  
"/images/superres/input001.png"));
imgOut   =  imsuperres(imgList);
figure();
imshow(imgOut);
outPath_1  =  'd:\testIn.png';
outPath_2  =  'd:\testOut.png';
res  =  imwrite(imgList(1),  outPath_1);
res  =  imwrite(imgOut,  outPath_2);
xdel();
The input file is saved as a 64x64 image.
The superresolution image is saved as a 256 x 256 image.

Interestingly enough:
If the output paths are set to "c:\testOut.png", imwrite would not 
work...unsure why.

Regards, Philipp

Am Mo., 21. Dez. 2020 um 11:37 Uhr schrieb Claus Futtrup 
mailto:cfutt...@gmail.com>>:

Hi Philipp

The file was saved automatically. I don't think you can set what
to save, or even the name of the file.
I also did a xs2png, but that only saves the current figure. In my
case a 610 x 460 pixel image (=the screen figure).

Cheers,
Claus

On 21-12-2020 11:21, P M wrote:

Dear Claus,

the example did not include saving the image as a file.

Best guesses:
- use imwrite
- use one of the xs2...-functions (e.g.: xs2bmp)

BR
Philipp

Am Mo., 21. Dez. 2020 um 09:20 Uhr schrieb Claus Futtrup
mailto:cfutt...@gmail.com>>:

Hi Philipp

I see, thank you for explaining it to me. I also see that the
upscale is not 2x2 = 4, but it is 4x4 so the upscaled image
is huge. The output file is saved - I believe - in wherever
your Scilab file browser is currently active.

Best regards,
Claus

On 20-12-2020 22:55, P M wrote:

Dear Claus,

you need to feed a list into imsuperres()not directly
the image.
Following should work.
imgList  =  list();
imgList(1)  =  imread('path_to_image');
imgOut   =  imsuperres(imgList);figure(); imshow(imgList(1)); figure();
imshow(imgOut); BR Philipp

Am So., 20. Dez. 2020 um 19:42 Uhr schrieb Claus Futtrup
mailto:cfutt...@gmail.com>>:

Hi there

I have a 4K picture, which I thought I'll try to upscale
with the
imsuperres in the IPCV toolbox. The code simply looks
like this:

imagefile =
'D:\Userdata\Claus\Pictures\Think_Global_4K.png';
im = imread(imagefile);
imout  = imsuperres(im);

The file is read and I get the following response:
Unsigned Integer 8
bits (2160 x 3840). Then Scilab crashes. I'm running
Scilab 6.1.0 (the
original release) on Windows 10 - in a MS Windows dialog
box I get:

 >Scilab 6.1.0 (Desktop) has stopped working

 >A problem caused the program to stop working
correctly. Windows will
close the program and notify you if a solution is available.

I am not sure that I've understood how to use imsuperres
correctly. I
see in the _params that rfactor = 4 is the default, so I
was expecting
the image to be scaled by a factor 4 (maybe that's 2 x 2
= I get an 8K
image = 4320 x 7680 pixels). The way I understand the
documentation, I
don't need to run imsuperres_params if I'm satisified
with the defaults.

Kind regards,

Claus

___
users mailing list
users@lists.scilab.org 
http://lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org  
http://lists.scilab.org/mailman/listinfo/users  

___
users mailing list
users@lists.scilab.org 
http://lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org  
http://lists.scilab.org/mailman/listinfo/users  

___
users mailing list
users@lists.scilab.org 
http://lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org

Re: [Scilab-users] atomsLoad

2020-12-22 Thread Stéphane Mottelet

I sent you (private message) the modified sources of emd_toolbox, for
the gateway part only. The toolbox compiles and loads, but then there
are problems due to the convention with the empty matrix that changed
since Scilab 6. I hope you will be able to fix them yourself (keep us
informed of your fixes).

Le 22/12/2020 à 16:12, Jean-Yves Baudais a écrit :

Hi,

It is quite easy (a 10 min. job). I made the needed modifications and it
compiles and loads under OSX. If you give me the rights on Gitlab I can commit
the modifications this afternoon.

Ok, but I don't how to do this, but I'm ready to learn :-) So, could you give me the step
starting with "stftb" source?
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/atoms.scilab.org/toolboxes/stftb/2.0.2/files/stftb-2.0.2-src.zip
(I'm regular with Linux command-line, not too much with makefile)

Or, maybe there already exists a document explaining the steps?

--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users

--
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
http://www.utc.fr/~mottelet

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

2020-12-22 Thread Stéphane Mottelet


Hi,

Le 22/12/2020 à 16:12, Jean-Yves Baudais a écrit :

Hi,


It is quite easy (a 10 min. job). I made the needed modifications and it
compiles and loads under OSX. If you give me the rights on Gitlab I can commit
the modifications this afternoon.

Ok, but I don't how to do this, but I'm ready to learn :-) So, could you give me the step 
starting with "stftb" source? 
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/atoms.scilab.org/toolboxes/stftb/2.0.2/files/stftb-2.0.2-src.zip
 (I'm regular with Linux command-line, not too much with makefile)

Or, maybe there already exists a document explaining the steps?


First, uncompress the zip file. In the obtained directory, go to the 
sci_gateway/c folder and remove


#include 

at line 8 in the file kiss_fft.h

Then in main toolbox directory, exec builder.sce as already said by 
Clément. If you had no error just "exec loader.sce".


S.



--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users


--
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
http://www.utc.fr/~mottelet

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

2020-12-22 Thread Clément David

Hello,

>From the source directory, you could use `exec builder.sce` [1]. Atoms 
>toolboxes only rely on Scilab scripts to describe and execute the build 
>(Makefiles are used behind the scene) ; for just rebuilding the toolbox, it 
>should be as simple as executing the builder, bumping the version and zip the 
>directory.

[1]: https://wiki.scilab.org/howto/Create%20a%20toolbox#Build_and_load_a_module
howto/Create a toolbox - Scilab 
Wiki
Creating an ATOMS toolbox. This page describes the usual method to create, 
package, and distribute a Scilab external module (ATOMS Toolbox). In the first 
part, we show how to structure the module by creating directories, 
sub-directories and files at the right place.
wiki.scilab.org
Thanks,

Clément

De : users  de la part de Jean-Yves Baudais 

Envoyé : mardi 22 décembre 2020 16:12
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] atomsLoad

Hi,

> It is quite easy (a 10 min. job). I made the needed modifications and it
> compiles and loads under OSX. If you give me the rights on Gitlab I can commit
> the modifications this afternoon.

Ok, but I don't how to do this, but I'm ready to learn :-) So, could you give 
me the step starting with "stftb" source? 
https://atoms.scilab.org/toolboxes/stftb/2.0.2/files/stftb-2.0.2-src.zip (I'm 
regular with Linux command-line, not too much with makefile)

Or, maybe there already exists a document explaining the steps?

--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

2020-12-22 Thread Jean-Yves Baudais

Hi,

> It is quite easy (a 10 min. job). I made the needed modifications and it
> compiles and loads under OSX. If you give me the rights on Gitlab I can commit
> the modifications this afternoon.

Ok, but I don't how to do this, but I'm ready to learn :-) So, could you give 
me the step starting with "stftb" source? 
https://atoms.scilab.org/toolboxes/stftb/2.0.2/files/stftb-2.0.2-src.zip (I'm 
regular with Linux command-line, not too much with makefile)

Or, maybe there already exists a document explaining the steps?

--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

2020-12-22 Thread Stéphane Mottelet

Seems that emd_toolbox is not on the forge...

Le 22/12/2020 à 15:17, Stéphane Mottelet a écrit :

Hi,

Le 22/12/2020 à 14:47, Clément David a écrit :

Hello,

It looks like the scilab 5.5.2 binary is not compatible with your
system (nc_putchar version error). IMHO it should be better to use
the latest Scilab version and try to build dependencies by hand ;
regarding the toolboxes:
* http://forge.scilab.org/index.php/p/stftb/

is not published for 6.1 but might compile on it ; get the sources
and try to build on your own machine.
* https://atoms.scilab.org/toolboxes/emd_toolbox/

already uses the pvApiCtx symbol ; it might be possible to port it to
scilab 6.1 without a big refactoring.

It is quite easy (a 10 min. job). I made the needed modifications and
it compiles and loads under OSX. If you give me the rights on Gitlab I
can commit the modifications this afternoon.

Thanks,

Clément

*De :* users de la part de Jean-Yves
Baudais

*Envoyé :* mardi 22 décembre 2020 12:36
*À :* Users mailing list for Scilab
*Objet :* Re: [Scilab-users] atomsLoad
Hi,

> You must use Scilab 5.5.2 and install the 1.2 version of the
toolbox. It

> should run out of the box.

Ok. I installed it. "scilab" command and "scilab -nw" or "-nb" or
"-ns" or "-noatomsautoload" give the so funny "Segmentation fault"
:-( Hopefully, "scilab -nwni" works, but I only have the
head_comments help and no plot. So, not so funny, but I can juggle
between scilab-5.5.2 and scilab-6.1.0

"scilab -debug" does not work anymore (but I not able to use gdb!)

gdb: SCI/lib/thirdparty/libtinfo.so.5: no version information
available (required by gdb)
gdb: SCI/lib/thirdparty/libtinfo.so.5: no version information
available (required by /lib/x86_64-linux-gnu/libreadline.so.7)

[...]
gdb: relocation error: /lib/x86_64-linux-gnu/libncursesw.so.5: symbol
_nc_putchar version NCURSES_TINFO_5.9.20150530 not defined in file
libtinfo.so.5 with link time reference

and "scilab -nogui" gives (maybe more informative)

Scilab startup function detected that the function proposed to the
engine is the wrong one. Usually, it comes from a linker problem in
your distribution/OS.
Here, Scilab should have 'libscijvm-disable' defined but gets
'libscijvm' instead.
If you do not know what it means, please report a bug on
http://bugzilla.scilab.org/
.
If you do, you probably know that you should change the link order in
SCI/modules/Makefile.am

Is there a simple way to solve this JVM problem? (Note that the
default scilab-6.0 installed in my Unbuntu has a JVM problem also and
does not work. Maybe I will try to solve it another time.)

--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

2020-12-22 Thread Stéphane Mottelet

Hi,

Le 22/12/2020 à 14:47, Clément David a écrit :

Hello,

It looks like the scilab 5.5.2 binary is not compatible with your
system (nc_putchar version error). IMHO it should be better to use the
latest Scilab version and try to build dependencies by hand ;
regarding the toolboxes:
* http://forge.scilab.org/index.php/p/stftb/

is not published for 6.1 but might compile on it ; get the sources and
try to build on your own machine.
* https://atoms.scilab.org/toolboxes/emd_toolbox/

already uses the pvApiCtx symbol ; it might be possible to port it to
scilab 6.1 without a big refactoring.

It is quite easy (a 10 min. job). I made the needed modifications and it
compiles and loads under OSX. If you give me the rights on Gitlab I can
commit the modifications this afternoon.

Thanks,

Clément

*De :* users de la part de Jean-Yves
Baudais

*Envoyé :* mardi 22 décembre 2020 12:36
*À :* Users mailing list for Scilab
*Objet :* Re: [Scilab-users] atomsLoad
Hi,

> You must use Scilab 5.5.2 and install the 1.2 version of the toolbox. It
> should run out of the box.

Ok. I installed it. "scilab" command and "scilab -nw" or "-nb" or
"-ns" or "-noatomsautoload" give the so funny "Segmentation fault" :-(
Hopefully, "scilab -nwni" works, but I only have the head_comments
help and no plot. So, not so funny, but I can juggle between
scilab-5.5.2 and scilab-6.1.0

"scilab -debug" does not work anymore (but I not able to use gdb!)

[...]
gdb: relocation error: /lib/x86_64-linux-gnu/libncursesw.so.5: symbol
_nc_putchar version NCURSES_TINFO_5.9.20150530 not defined in file
libtinfo.so.5 with link time reference

and "scilab -nogui" gives (maybe more informative)

Is there a simple way to solve this JVM problem? (Note that the
default scilab-6.0 installed in my Unbuntu has a JVM problem also and
does not work. Maybe I will try to solve it another time.)

--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

2020-12-22 Thread Clément David

Hello,

It looks like the scilab 5.5.2 binary is not compatible with your system 
(nc_putchar version error). IMHO it should be better to use the latest Scilab 
version and try to build dependencies by hand ; regarding the toolboxes:
 * http://forge.scilab.org/index.php/p/stftb/ is not published for 6.1 but 
might compile on it ; get the sources and try to build on your own machine.
 * https://atoms.scilab.org/toolboxes/emd_toolbox/ already uses the pvApiCtx 
symbol ; it might be possible to port it to scilab 6.1 without a big 
refactoring.

Thanks,

Clément

De : users  de la part de Jean-Yves Baudais 

Envoyé : mardi 22 décembre 2020 12:36
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] atomsLoad

Hi,

> You must use Scilab 5.5.2 and install the 1.2 version of the toolbox. It
> should run out of the box.

Ok. I installed it. "scilab" command and "scilab -nw" or "-nb" or "-ns" or 
"-noatomsautoload" give the so funny "Segmentation fault" :-( Hopefully, 
"scilab -nwni" works, but I only have the head_comments help and no plot. So, 
not so funny, but I can juggle between scilab-5.5.2 and scilab-6.1.0

"scilab -debug" does not work anymore (but I not able to use gdb!)

gdb: SCI/lib/thirdparty/libtinfo.so.5: no version information available 
(required by gdb)
gdb: SCI/lib/thirdparty/libtinfo.so.5: no version information available 
(required by /lib/x86_64-linux-gnu/libreadline.so.7)
[...]
gdb: relocation error: /lib/x86_64-linux-gnu/libncursesw.so.5: symbol 
_nc_putchar version NCURSES_TINFO_5.9.20150530 not defined in file 
libtinfo.so.5 with link time reference

and "scilab -nogui" gives (maybe more informative)

Scilab startup function detected that the function proposed to the engine is 
the wrong one. Usually, it comes from a linker problem in your distribution/OS.
Here, Scilab should have 'libscijvm-disable' defined but gets 'libscijvm' 
instead.
If you do not know what it means, please report a bug on 
http://bugzilla.scilab.org/. If you do, you probably know that you should 
change the link order in SCI/modules/Makefile.am

Is there a simple way to solve this JVM problem? (Note that the default 
scilab-6.0 installed in my Unbuntu has a JVM problem also and does not work. 
Maybe I will try to solve it another time.)

--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

2020-12-22 Thread Jean-Yves Baudais

Hi,

> You must use Scilab 5.5.2 and install the 1.2 version of the toolbox. It
> should run out of the box.

Ok. I installed it. "scilab" command and "scilab -nw" or "-nb" or "-ns" or 
"-noatomsautoload" give the so funny "Segmentation fault" :-( Hopefully, 
"scilab -nwni" works, but I only have the head_comments help and no plot. So, 
not so funny, but I can juggle between scilab-5.5.2 and scilab-6.1.0

"scilab -debug" does not work anymore (but I not able to use gdb!)

gdb: SCI/lib/thirdparty/libtinfo.so.5: no version information available 
(required by gdb)
gdb: SCI/lib/thirdparty/libtinfo.so.5: no version information available 
(required by /lib/x86_64-linux-gnu/libreadline.so.7)
[...]
gdb: relocation error: /lib/x86_64-linux-gnu/libncursesw.so.5: symbol 
_nc_putchar version NCURSES_TINFO_5.9.20150530 not defined in file 
libtinfo.so.5 with link time reference

and "scilab -nogui" gives (maybe more informative)

Scilab startup function detected that the function proposed to the engine is 
the wrong one. Usually, it comes from a linker problem in your distribution/OS.
Here, Scilab should have 'libscijvm-disable' defined but gets 'libscijvm' 
instead.
If you do not know what it means, please report a bug on 
http://bugzilla.scilab.org/. If you do, you probably know that you should 
change the link order in SCI/modules/Makefile.am

Is there a simple way to solve this JVM problem? (Note that the default 
scilab-6.0 installed in my Unbuntu has a JVM problem also and does not work. 
Maybe I will try to solve it another time.)

-- 
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] IPCV upscaling of image

Re: [Scilab-users] atomsLoad

Re: [Scilab-users] atomsLoad

Re: [Scilab-users] atomsLoad

Re: [Scilab-users] atomsLoad

Re: [Scilab-users] atomsLoad

Re: [Scilab-users] atomsLoad

Re: [Scilab-users] atomsLoad

Re: [Scilab-users] atomsLoad

9 matches

Site Navigation

Mail list logo

Footer information