1. Re: Neural Network Toolbox setup

[Russell jarvis]

I did try a few of the pkg commands from your email, and from Octave
website you linked to. I was too emberrased to admit that initially
because the error messages I was getting gave me the impression that
pkg expected file arguments rather than directory arguments, and I
assumed that it was a silly idea for of mine to try doing this.

Using:

>pkg install (name of package)

Inside Octave seemed to work on some files, in the sense that it
didn't always produce error messages.

It did not produce error messages on files like: 'octave-core' and 'inst'.

All files except one other file and all directories produced error
messages. The error messages refered to the end of a tape. In the case
of directory arguments the error messages stated that the name of the
arguments I provided were directories (assuming this is an error).

Thanks for your persistant help though Jordi.

>From Russell.

On Fri, Aug 1, 2008 at 11:37 PM,  <address@hidden> wrote:
> Send Help-octave mailing list submissions to
>        address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://www.cae.wisc.edu/mailman/listinfo/help-octave
> or, via email, send a message with subject or body 'help' to
>        address@hidden
>
> You can reach the person managing the list at
>        address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Help-octave digest..."
>
>
> Today's Topics:
>
>   1. Re: Neural Network Toolbox setup. ( Jordi Guti?rrez Hermoso )
>   2. How do I read a variable name file? (Rub?n Roa-Ureta)
>   3. How do I read a variable name file? (John W. Eaton)
>   4. Re: How do I read a variable name file? (Bill Denney)
>   5. Where's octave library located? (Abdul Rahman Riza)
>   6. Re: Where's octave library located? (marco cammarata)
>   7. problem with tests on latest octave (Riccardo Corradini)
>   8. Re: problem with tests on latest octave (dbateman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 31 Jul 2008 14:40:33 -0500
> From: " Jordi Guti?rrez Hermoso " <address@hidden>
> Subject: Re: Neural Network Toolbox setup.
> To: "Russell jarvis" <address@hidden>
> Cc: address@hidden
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 2008/7/30 Russell jarvis <address@hidden>:
>> I don't have a Red Hat package of the neural network toolbox and I
>> don't think any are available so I am unsure if running Octave, going
>> into the appropriate directory and typing `doc pkg' will work.
>
> It will. Did you try it? It's Octave's internal package-handling
> mechanism independent of the distribution you use.
>
>> I downloaded nnet-0.1.3 from source forge again.
>>
>> I went inside and found the folder were all of the .M files were
>> stored and copied this folder.
>
> Before you go on, go read the pkg doc.
>
>> Does Linux have an equivalent of `Program Files'?
>
> Uhm, not really. Some versions of GNU/Linux do, like GoboLinux, but
> otherwise, files are scattered all over the tree structure according
> to 30-year-old Unix traditions (which I think is mostly a good thing).
>
>> My first thought was
>> the bin folder but that is stupid because an M file is a script not an
>> executable.
>
> The /usr/bin or /bin directories (I've never liked the "folder"
> metaphor myself), may contain binary executables, but also often
> contain scripts that are set executable and have a shebang line (e.g
> #!/usr/bin/octave).
>
>> I have a folder called `Octave setup' on my desktop. I went inside
>> that and found a folder called `scripts', all of the folders in
>> scripts seem to contain M files. I figure this might be an okay place
>> to put them, except I have a feeling these are only setup files, and
>> the real directory Octave is running from is somewhere else on the
>> directory tree.
>
> Yes. Use "pkg add" from Octave. Handling of software is very different
> under a GNU system than on Windows. In particular, you mostly let the
> packaging tools do the work for you.
>
> - Jordi G. H.
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 31 Jul 2008 21:07:22 -0400
> From: Rub?n Roa-Ureta <address@hidden>
> Subject: How do I read a variable name file?
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi:
>
> I want to read text files that contain a single number but whose names
> changes according to user input, as in:
>
>  >Yr=input('Year :');
> Yr: 1990
>  >filename=['SEPM_',num2str(Yr),'s2.txt']
> filename = SEPM_1990s2.txt
>  >eval(eggstart=['load ',filename])
>
> However, the single number in SEPM_1990s2.txt hasn't been assigned to
> eggstart
>
>  >eggstart
> eggstart = load SEPM_1990s2.txt
>
> whereas if I directly do the loading
>
>  >eggstart = load SEPM_1990s2.txt
> eggstart =  the  single number in SEPM_1990s2.txt
>
> the number is assigned.
>
> What else should I do with the eval function to actually complete the
> assignment?
>
> Thanks
>
> Rub?n
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 31 Jul 2008 22:00:13 -0400
> From: "John W. Eaton" <address@hidden>
> Subject: How do I read a variable name file?
> To: Rub?n Roa-Ureta <address@hidden>
> Cc: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=iso-8859-1
>
> On 31-Jul-2008, Rub?n Roa-Ureta wrote:
>
> | Hi:
> |
> | I want to read text files that contain a single number but whose names
> | changes according to user input, as in:
> |
> |  >Yr=input('Year :');
> | Yr: 1990
> |  >filename=['SEPM_',num2str(Yr),'s2.txt']
> | filename = SEPM_1990s2.txt
> |  >eval(eggstart=['load ',filename])
> |
> | However, the single number in SEPM_1990s2.txt hasn't been assigned to
> | eggstart
> |
> |  >eggstart
> | eggstart = load SEPM_1990s2.txt
> |
> | whereas if I directly do the loading
> |
> |  >eggstart = load SEPM_1990s2.txt
> | eggstart =  the  single number in SEPM_1990s2.txt
> |
> | the number is assigned.
> |
> | What else should I do with the eval function to actually complete the
> | assignment?
>
> You don't need eval for this job.  Use something like
>
>  eggstart = load (sprintf ("SEPM_%ds2.txt", Yr));
>
> jwe
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 31 Jul 2008 22:08:35 -0400
> From: Bill Denney <address@hidden>
> Subject: Re: How do I read a variable name file?
> To: Rub?n Roa-Ureta <address@hidden>
> Cc: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Rub?n Roa-Ureta wrote:
>> Hi:
>>
>> I want to read text files that contain a single number but whose names
>> changes according to user input, as in:
>>
>>  >Yr=input('Year :');
>> Yr: 1990
>>  >filename=['SEPM_',num2str(Yr),'s2.txt']
>> filename = SEPM_1990s2.txt
>>  >eval(eggstart=['load ',filename])
>>
>> However, the single number in SEPM_1990s2.txt hasn't been assigned to
>> eggstart
>>
>>  >eggstart
>> eggstart = load SEPM_1990s2.txt
>>
>> whereas if I directly do the loading
>>
>>  >eggstart = load SEPM_1990s2.txt
>> eggstart =  the  single number in SEPM_1990s2.txt
>>
>> the number is assigned.
>>
>> What else should I do with the eval function to actually complete the
>> assignment?
> Hi Ruben,
>
> What you likely want to do is something like:
>
> Yr=input('Year :');
> filename=['SEPM_',num2str(Yr),'s2.txt']
> eggstart=load(filename);
>
>
> or more simply
>
> Yr=input ('Year :');
> eggstart=load (sprintf ("SEPM_%ds2.txt", Yr));
>
>
> Have a good day,
>
> Bill
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 01 Aug 2008 12:20:01 +0800
> From: Abdul Rahman Riza <address@hidden>
> Subject: Where's octave library located?
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain
>
> Dear Colleagues,
>
> I am wondering where is octave's libraries located. I am working on
> ubuntu 8.04 with octave 3.0 and want to try compile c program using
> octave libraries.
>
> Regards,
> Riza
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 01 Aug 2008 08:45:03 +0200
> From: marco cammarata <address@hidden>
> Subject: Re: Where's octave library located?
> To: Abdul Rahman Riza <address@hidden>
> Cc: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain
>
> Hi,
>
> the command mkoctfile is what you need.
>
> try "mkoctfile --help" and you will see the list of variables that are
> recognized.
>
> for example:
> "mkoctfile -p ALL_CFLAGS" gives on my computer
>
> -I/usr/include/octave-3.0.1 -I/usr/include/octave-3.0.1/octave -mieee-fp
> -O2 -g
>
> You may find interesting the examples here:
> http://info.ee.surrey.ac.uk/Personal/M.Michel/index.php?page=4&site=4
>
> regards,
> marco
>
> btw: linux provide a very powerful command: "locate", try "locate octave
> | grep lib"
>
> On Fri, 2008-08-01 at 12:20 +0800, Abdul Rahman Riza wrote:
>> Dear Colleagues,
>>
>> I am wondering where is octave's libraries located. I am working on
>> ubuntu 8.04 with octave 3.0 and want to try compile c program using
>> octave libraries.
>>
>> Regards,
>> Riza
>>
>> _______________________________________________
>> Help-octave mailing list
>> address@hidden
>> https://www.cae.wisc.edu/mailman/listinfo/help-octave
> --
> Marco Cammarata,
> Post-Doc
> European Synchrotron Radiation Facility
> Material Science Group
> 6, rue Jules Horowitz
> BP 220, Grenoble Cedex 38043, FRANCE
>
> Beamline ID09b
> Office : +33 (0)4 76 88 25 29
> Beamline : +33 (0)4 76 88 26 95
> Fax : +33 (0)4 76 88 27 43
> email: address@hidden
> http://www.esrf.fr/UsersAndScience/Experiments/MaterialsScience/ID09B/
> http://www.fisica.unipa.it/~emoglobina/marco
> ~
>
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 1 Aug 2008 07:53:32 +0000 (GMT)
> From: Riccardo Corradini <address@hidden>
> Subject: problem with tests on latest octave
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all,
> I have successfully complied the latest octave? 3.1.51+
> but the I have some problems with the usual tests
> Here there is the output
> :~/debugoct/octavecvs/octave$ make check
> make -f octMakefile check
> make[1]: Entering directory `/home/corradin/debugoct/octavecvs/octave'
> make -C test check
> make[2]: Entering directory `/home/corradin/debugoct/octavecvs/octave/test'
> ../run-octave --norc --silent --no-history ./fntests.m .
>
> Integrated test scripts:
>
> ? src/DLD-FUNCTIONS/betainc.cc ........................... PASS??? 6/6??
> ? src/DLD-FUNCTIONS/bsxfun.cc ............................ PASS?? 55/55?
> ? src/DLD-FUNCTIONS/cellfun.cc ........................... PASS?? 31/31?
> ? src/DLD-FUNCTIONS/chol.cc .............................. PASS?? 22/22?
> ? src/DLD-FUNCTIONS/conv2.cc ............................. PASS??? 2/2??
> ? src/DLD-FUNCTIONS/dassl.cc ............................. PASS??? 4/4??
> ? src/DLD-FUNCTIONS/det.cc ............................... PASS??? 5/5??
> ? src/DLD-FUNCTIONS/dispatch.cc .......................... PASS?? 13/13?
> ? src/DLD-FUNCTIONS/dlmread.cc ........................... PASS?? 20/20?
> ? src/DLD-FUNCTIONS/dmperm.cc ............................ PASS??? 5/5??
> ? src/DLD-FUNCTIONS/eig.cc ............................... PASS??? 7/7??
> ? src/DLD-FUNCTIONS/expm.cc .............................. PASS??? 8/8??
> ? src/DLD-FUNCTIONS/fft.cc ............................... PASS?? 19/19?
> ? src/DLD-FUNCTIONS/fft2.cc .............................. PASS??? 4/4??
> ? src/DLD-FUNCTIONS/find.cc .............................. PASS??? 9/9??
> ? src/DLD-FUNCTIONS/fsolve.cc ............................ PASS??? 4/4??
> ? src/DLD-FUNCTIONS/gammainc.cc .......................... PASS??? 2/2??
> ? src/DLD-FUNCTIONS/gcd.cc ............................... PASS??? 6/6??
> ? src/DLD-FUNCTIONS/hess.cc .............................. PASS??? 5/5??
> ? src/DLD-FUNCTIONS/hex2num.cc ........................... PASS??? 2/2??
> ? src/DLD-FUNCTIONS/inv.cc ............................... PASS??? 5/5??
> ? src/DLD-FUNCTIONS/lookup.cc ............................ PASS?? 16/16?
> ? src/DLD-FUNCTIONS/lsode.cc ............................. PASS??? 5/5??
> ? src/DLD-FUNCTIONS/lu.cc ................................ PASS?? 12/12?
> ? src/DLD-FUNCTIONS/luinc.cc ............................. PASS??? 2/2??
> ? src/DLD-FUNCTIONS/matrix_type.cc ....................... PASS?? 51/51?
> ? src/DLD-FUNCTIONS/max.cc ............................... PASS?? 12/12?
> ? src/DLD-FUNCTIONS/qr.cc ................................panic: Segmentation 
> fault -- stopping myself...
> make[2]: *** [check] Segmentation fault
> make[2]: Leaving directory `/home/corradin/debugoct/octavecvs/octave/test'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/home/corradin/debugoct/octavecvs/octave'
> make: *** [check] Error 2
>
> Thanks a lot for all your help
> Riccardo
>
>
>
>      Posta, news, sport, oroscopo: tutto in una sola pagina.
> Crea l&#39;home page che piace a te!
> www.yahoo.it/latuapagina
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> https://www.cae.wisc.edu/pipermail/help-octave/attachments/20080801/d78499cd/attachment-0001.html
>
> ------------------------------
>
> Message: 8
> Date: Fri, 1 Aug 2008 06:36:46 -0700 (PDT)
> From: dbateman <address@hidden>
> Subject: Re: problem with tests on latest octave
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
>
>
>
> Riccardo Corradini wrote:
>>
>>   src/DLD-FUNCTIONS/max.cc ............................... PASS   12/12
>>   src/DLD-FUNCTIONS/qr.cc ................................panic:
>> Segmentation fault -- stopping myself...
>> make[2]: *** [check] Segmentation fault
>>
>
> Try
>
> make clean; make all
>
> and try again
>
> D.
> --
> View this message in context: 
> http://www.nabble.com/problem-with-tests-on-latest-octave-tp18770178p18774459.html
> Sent from the Octave - General mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www.cae.wisc.edu/mailman/listinfo/help-octave
>
>
> End of Help-octave Digest, Vol 29, Issue 1
> ******************************************
>