From: Toan T Nguyen <ntt@physics.ucla.edu>
To: gsl-discuss@sources.redhat.com
Subject: Help: working with large gsl_vector
Date: Sat, 11 Dec 2004 07:44:00 -0000 [thread overview]
Message-ID: <200412102351.20027.ntt@physics.ucla.edu> (raw)
Hi,
I'm using the multidimensional minimization procedure in GSL and have problem
with large vectors. The dimensionality of my vectors is 300000 which means my
index variable is of long integer type. gsl_vector, however, works only with
size_t type only. I couldnot even call gsl_vector_alloc(300000) . It says:
gsl: init_source.c:29: ERROR: vector length n must be positive integer
Default GSL error handler invoked.
Can somebody here give an advice? I'm quite new to GSL and I search the
mailing list archives but could not find an answer?
For clarity, my system is an Athlon64 using SuSE x86_64, gcc 3.3.3
Thanks a lot in advance,
Toan
next reply other threads:[~2004-12-11 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 7:44 Toan T Nguyen [this message]
2004-12-13 18:41 ` Linas Vepstas
2004-12-13 18:51 ` Fabrice Rossi
2004-12-14 23:03 ` Toan T Nguyen
2004-12-15 11:12 ` Fabrice Rossi
2004-12-15 12:11 ` Robert G. Brown
2004-12-15 17:31 ` Linas Vepstas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412102351.20027.ntt@physics.ucla.edu \
--to=ntt@physics.ucla.edu \
--cc=gsl-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).