Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(68) |
Feb
(72) |
Mar
(46) |
Apr
(44) |
May
(40) |
Jun
(54) |
Jul
(26) |
Aug
(86) |
Sep
(95) |
Oct
(151) |
Nov
(65) |
Dec
(34) |
2003 |
Jan
(22) |
Feb
(70) |
Mar
(24) |
Apr
(28) |
May
(50) |
Jun
(31) |
Jul
(17) |
Aug
(42) |
Sep
(27) |
Oct
(71) |
Nov
(27) |
Dec
(71) |
2004 |
Jan
(40) |
Feb
(30) |
Mar
(20) |
Apr
(22) |
May
(41) |
Jun
(9) |
Jul
(24) |
Aug
(41) |
Sep
(35) |
Oct
(8) |
Nov
(5) |
Dec
(4) |
2005 |
Jan
(27) |
Feb
(13) |
Mar
(18) |
Apr
(7) |
May
(10) |
Jun
(36) |
Jul
(28) |
Aug
(17) |
Sep
(1) |
Oct
(11) |
Nov
(12) |
Dec
(15) |
2006 |
Jan
(99) |
Feb
(5) |
Mar
(31) |
Apr
(26) |
May
(20) |
Jun
(33) |
Jul
(45) |
Aug
(18) |
Sep
(2) |
Oct
(19) |
Nov
(3) |
Dec
(8) |
2007 |
Jan
(1) |
Feb
(15) |
Mar
(20) |
Apr
|
May
(4) |
Jun
(6) |
Jul
(11) |
Aug
(11) |
Sep
(11) |
Oct
(19) |
Nov
(25) |
Dec
(46) |
2008 |
Jan
(42) |
Feb
(20) |
Mar
(43) |
Apr
(24) |
May
(4) |
Jun
|
Jul
(19) |
Aug
(63) |
Sep
(33) |
Oct
(17) |
Nov
(36) |
Dec
(20) |
2009 |
Jan
(36) |
Feb
(18) |
Mar
(144) |
Apr
(36) |
May
(11) |
Jun
(7) |
Jul
(8) |
Aug
(21) |
Sep
(33) |
Oct
(7) |
Nov
(2) |
Dec
(1) |
2010 |
Jan
(33) |
Feb
(3) |
Mar
(34) |
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
(3) |
Aug
(28) |
Sep
(8) |
Oct
(12) |
Nov
(11) |
Dec
(44) |
2011 |
Jan
(30) |
Feb
(10) |
Mar
(8) |
Apr
(23) |
May
(8) |
Jun
(9) |
Jul
(3) |
Aug
(9) |
Sep
(5) |
Oct
(9) |
Nov
(11) |
Dec
(24) |
2012 |
Jan
(6) |
Feb
(32) |
Mar
(8) |
Apr
(26) |
May
(13) |
Jun
(51) |
Jul
(21) |
Aug
(7) |
Sep
(9) |
Oct
(13) |
Nov
(5) |
Dec
(10) |
2013 |
Jan
(56) |
Feb
(6) |
Mar
(15) |
Apr
(4) |
May
(24) |
Jun
(4) |
Jul
(9) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(8) |
2014 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
(12) |
Jun
(3) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(19) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(22) |
Dec
(25) |
2016 |
Jan
(9) |
Feb
(9) |
Mar
(13) |
Apr
|
May
|
Jun
(2) |
Jul
(4) |
Aug
|
Sep
|
Oct
(11) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
1
|
2
(3) |
3
|
4
(1) |
5
|
6
|
7
(1) |
8
(3) |
9
(6) |
10
(8) |
11
(3) |
12
|
13
|
14
(2) |
15
|
16
(1) |
17
|
18
(4) |
19
|
20
(2) |
21
(1) |
22
(4) |
23
|
24
|
25
|
26
|
27
|
28
(1) |
29
|
30
|
31
(2) |
|
|
From: Amitha Perera <amithaperera@us...> - 2008-01-31 15:06:04
|
Folks, We've had a couple of messages on this list about vnl and rounding: http://sourceforge.net/mailarchive/message.php?msg_id=44C13A99.80709%40kitware.com http://sourceforge.net/mailarchive/message.php?msg_id=470E5E5A.9020605%40kitware.com The issue is about what the halfway cases round to, and about how fast one can do it. Right now, the comment on vnl_math_rnd says "0.5 rounds up", but the assembly implementation doesn't agree on Visual C++. I suggest the following as a permanent solution: vnl_math_rnd rounds away from zero (same as the C99 function lround). -13.5 -> -14 -12.5 -> -13 12.5 -> 13 13.5 -> 14 A new function vnl_math_int[*] rounds to an integer as efficiently as possible, with halfway cases being converted in an unspecified but consistent way. (Kinda like lrint.) Folks can use this when they are just converting to an integer, and aren't sensitive to the rounding on the halfway cases. And, of course, good old vcl_floor, vcl_ceil, and int() exist for the cases where you really care about the rounding. (Cast to int is guaranteed to truncate. -1.5 -> -1, 1.5 -> 1.) Thoughts? Amitha. [*] Maybe name it vnl_math_fast_rnd instead? |
From: Amitha Perera <amithaperera@us...> - 2008-01-31 13:35:27
|
Folks, The vxl dashboard is down, as I'm sure you've noticed because you check every day. There is some system issues that are being worked on. Unfortunately, I will be traveling next week, so it may be the week after before everything is working again. Amitha. |
From: Peter Vanroose <peter_vanroose@ya...> - 2008-01-28 07:50:56
|
Dear all, Following a recent bug report, I've added tests in vnl/tests/test_bignum.cxx which expose this bug (and hence fail). I believe it's important enough to have the test failure there until the bug is fixed. I've spent some time, without luck, looking into the source code of divide() in vnl/vnl_bignum.cxx Maybe someone else would mind looking into this? Seems that something goes wrong in the implementation of Knuth's division algorithm (Knuth, V.2, Section 4.3.1, Algorithm D). It's the methods estimate_q_hat() and multiply_subtract() which apparently have a problem. Any of you who is somewhat familiar with Knuth's V.2 ? This bug could have been there since 1991's COOL implementation (by Texas Instruments) or have been introduced when porting from COOL to vnl in 2002, since none of the original COOL tests expose this bug. -- Peter. -- __________________________________________________________ Ta semester! - sök efter resor hos Yahoo! Shopping. Jämför pris på flygbiljetter och hotellrum här: http://shopping.yahoo.se/c-169901-resor-biljetter.html?partnerId=96914052 |
From: Wheeler, Frederick W (GE, Research) <wheeler@cr...> - 2008-01-22 14:25:19
|
Doxygen has a built-in search engine, enabled with this command in the doxygen config file. SEARCHENGINE =3D YES This uses apache mod_php. On an internal FreeBSD machine I use /usr/ports/lang/php5/. Fred -----Original Message----- From: vxl-maintainers-bounces@... [mailto:vxl-maintainers-bounces@...] On Behalf Of Amitha Perera Sent: Tuesday, January 22, 2008 9:13 AM To: Ian Scott Cc: 'vxl-maintainers' Subject: Re: [Vxl-maintainers] vxl documentation Ian Scott wrote: > To run a search, you could create a form that constructed a google=20 > search along the lines of [...] Yes. But there may be more local search options; I need to do a little more digging. (I'm still new here, is my excuse.) Amitha. ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Vxl-maintainers mailing list Vxl-maintainers@... https://lists.sourceforge.net/lists/listinfo/vxl-maintainers |
From: Amitha Perera <amitha@th...> - 2008-01-22 14:12:47
|
Ian Scott wrote: > To run a search, you could create a form that constructed a google > search along the lines of [...] Yes. But there may be more local search options; I need to do a little more digging. (I'm still new here, is my excuse.) Amitha. |
From: Ian Scott <ian.m.scott@st...> - 2008-01-22 10:19:04
|
Amitha The hosting looks good. Glad you were able to get those scripts to work. Thanks for your efforts here. It is good to see the doc pages up again. To run a search, you could create a form that constructed a google search along the lines of inurl:vxl inurl:release inurl:doc site:public.kitware.com vnl_vector or http://www.google.co.uk/search?q=inurl%3Avxl+inurl%3Arelease++site%3Apublic.kitware.com+vnl_vector It looks like google hasn't crawled the pages yet, but it should work in a day or two. Ian. Amitha Perera wrote: > I hear all of you on the preceived ownership ownership issue. That > wasn't my intent, but I can see how it could be interpreted that way. > So, let's leave the main pages at sourceforge, updated via CVS, and the > generated doxygen can be hosted at Kitware and anywhere else that wants > to (but see the note below). At Kitware, the updated links are > > (a) http://public.kitware.com/vxl/doc/release/ > (b) http://public.kitware.com/vxl/doc/development/ > > The books are generated in there too. Right after this email, I'll > commit changes to the main webpages to change links appropriately. > > Note, however, that the Kitware hosted webpages are Kitware branded. > This is a side effect of hosting on the public webserver, and is > difficult to avoid. If this is a problem, someone else should host the > documentation. > > I've removed the Brown mirror from the main documentation too, since it > seems to be down as well. Hopefully someone can get that set up. > > I've also removed links to the search functionality until I've figured > out the best way to get a search into just the vxl documentation. > > Amitha. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Vxl-maintainers mailing list > Vxl-maintainers@... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers |
From: Brendan McCane <brendan.mccane@gm...> - 2008-01-22 04:01:39
|
Looks good to me Amitha. Thanks muchly for doing that. Cheers, Brendan. On 22/01/2008, Amitha Perera <amitha@...> wrote: > I hear all of you on the preceived ownership ownership issue. That > wasn't my intent, but I can see how it could be interpreted that way. > So, let's leave the main pages at sourceforge, updated via CVS, and the > generated doxygen can be hosted at Kitware and anywhere else that wants > to (but see the note below). At Kitware, the updated links are > > (a) http://public.kitware.com/vxl/doc/release/ > (b) http://public.kitware.com/vxl/doc/development/ > > The books are generated in there too. Right after this email, I'll > commit changes to the main webpages to change links appropriately. > > Note, however, that the Kitware hosted webpages are Kitware branded. > This is a side effect of hosting on the public webserver, and is > difficult to avoid. If this is a problem, someone else should host the > documentation. > > I've removed the Brown mirror from the main documentation too, since it > seems to be down as well. Hopefully someone can get that set up. > > I've also removed links to the search functionality until I've figured > out the best way to get a search into just the vxl documentation. > > Amitha. > -- Cheers, Brendan |
From: Amitha Perera <amitha@th...> - 2008-01-21 21:10:52
|
I hear all of you on the preceived ownership ownership issue. That wasn't my intent, but I can see how it could be interpreted that way. So, let's leave the main pages at sourceforge, updated via CVS, and the generated doxygen can be hosted at Kitware and anywhere else that wants to (but see the note below). At Kitware, the updated links are (a) http://public.kitware.com/vxl/doc/release/ (b) http://public.kitware.com/vxl/doc/development/ The books are generated in there too. Right after this email, I'll commit changes to the main webpages to change links appropriately. Note, however, that the Kitware hosted webpages are Kitware branded. This is a side effect of hosting on the public webserver, and is difficult to avoid. If this is a problem, someone else should host the documentation. I've removed the Brown mirror from the main documentation too, since it seems to be down as well. Hopefully someone can get that set up. I've also removed links to the search functionality until I've figured out the best way to get a search into just the vxl documentation. Amitha. |
From: Joseph Mundy <mundy@le...> - 2008-01-20 14:32:25
|
Amitha, I am in agreement with Brendan and Matt. I think it is great if Kitware = can host the book. I appreciate your stepping into the breach. Maybe we can evolve to something a bit less cumbersome than texi.=20 However, I think we need to maintain an appearance of neutrality as to = the ownership of vxl.=20 This neutrality is best guaranteed by keeping the vxl webpage served = from sourceforge. Joe From: vxl-maintainers-bounces@... [mailto:vxl-maintainers-bounces@...] On Behalf Of = Brendan McCane Sent: Saturday, January 19, 2008 10:20 PM To: Matt Leotta Cc: vxl-maintainers; Amitha Perera Subject: Re: [Vxl-maintainers] vxl documentation I too have mild objections to the main page moving to kitware - mostly because I usually update the main page every time I do a new release and it's convenient to have it under the same csv as the source code. Further, it gives more flexibility if someone else decides to take over making releases. No problems with the documentation, although it would be good to get the vxl book back up ... Cheers, Brendan. On 19/01/2008, Matt Leotta <matt.leotta@...> wrote: > I second Peter's comments. Everything is fine with me except moving > the VXL main page to Kitware. I don't have a problem with kitware > hosting the pages, but that URL give the false impress that Kitware > somehow "owns" VXL. > > Also, what about the VXL Book? I thought part of the reason for this > move was to get the book back online. Will Kitware host that too? > > --Matt > > On Jan 18, 2008 1:36 PM, Peter Vanroose <peter_vanroose@...> wrote: > > > I've set up the VXL documentation on a Kitware server. > > > > > > (a) http://kitware.com/vxl/ > > > (b) http://kitware.com/vxl/doxygen/release/ > > > (c) http://kitware.com/vxl/doxygen/development/ > > > > Great! Seems like a very reasonable setup. > > > > > > > 1. Shall we move the "main" VXL pages from SourceForge > > > to Kitware (http://kitware.com/vxl)? > > > > I wouldn't do that. > > Depends of course on the ease of maintaining one or the other. > > > > > > > 3. I'd like to set (b) and (c) as "the" documentation pages, with > > > the Manchester and Brown pages labelled mirrors. > > > > Agreed. > > > > -- Peter. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > __________________________________________________________ > > L=E5na pengar utan s=E4kerhet. J=E4mf=F6r vilkor online hos Yahoo! > > http://shopping.yahoo.se/c-100390123-lan-utan-sakerhet.html?partnerId=3D9= 69150 14 > > > > > > -------------------------------------------------------------------------= > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Vxl-maintainers mailing list > > Vxl-maintainers@... > > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > > > > = -------------------------------------------------------------------------= > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Vxl-maintainers mailing list > Vxl-maintainers@... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > --=20 Cheers, Brendan -------------------------------------------------------------------------= This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Vxl-maintainers mailing list Vxl-maintainers@... https://lists.sourceforge.net/lists/listinfo/vxl-maintainers |
From: Brendan McCane <brendan.mccane@gm...> - 2008-01-20 03:19:30
|
I too have mild objections to the main page moving to kitware - mostly because I usually update the main page every time I do a new release and it's convenient to have it under the same csv as the source code. Further, it gives more flexibility if someone else decides to take over making releases. No problems with the documentation, although it would be good to get the vxl book back up ... Cheers, Brendan. On 19/01/2008, Matt Leotta <matt.leotta@...> wrote: > I second Peter's comments. Everything is fine with me except moving > the VXL main page to Kitware. I don't have a problem with kitware > hosting the pages, but that URL give the false impress that Kitware > somehow "owns" VXL. > > Also, what about the VXL Book? I thought part of the reason for this > move was to get the book back online. Will Kitware host that too? > > --Matt > > On Jan 18, 2008 1:36 PM, Peter Vanroose <peter_vanroose@...> wrot= e: > > > I've set up the VXL documentation on a Kitware server. > > > > > > (a) http://kitware.com/vxl/ > > > (b) http://kitware.com/vxl/doxygen/release/ > > > (c) http://kitware.com/vxl/doxygen/development/ > > > > Great! Seems like a very reasonable setup. > > > > > > > 1. Shall we move the "main" VXL pages from SourceForge > > > to Kitware (http://kitware.com/vxl)? > > > > I wouldn't do that. > > Depends of course on the ease of maintaining one or the other. > > > > > > > 3. I'd like to set (b) and (c) as "the" documentation pages, with > > > the Manchester and Brown pages labelled mirrors. > > > > Agreed. > > > > -- Peter. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > __________________________________________________________ > > L=E5na pengar utan s=E4kerhet. J=E4mf=F6r vilkor online hos Yahoo! > > http://shopping.yahoo.se/c-100390123-lan-utan-sakerhet.html?partnerId= =3D96915014 > > > > > > -----------------------------------------------------------------------= -- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Vxl-maintainers mailing list > > Vxl-maintainers@... > > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Vxl-maintainers mailing list > Vxl-maintainers@... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > --=20 Cheers, Brendan |
From: Matt Leotta <matt.leotta@gm...> - 2008-01-18 19:12:56
|
I second Peter's comments. Everything is fine with me except moving the VXL main page to Kitware. I don't have a problem with kitware hosting the pages, but that URL give the false impress that Kitware somehow "owns" VXL. Also, what about the VXL Book? I thought part of the reason for this move was to get the book back online. Will Kitware host that too? --Matt On Jan 18, 2008 1:36 PM, Peter Vanroose <peter_vanroose@...> wrote: > > I've set up the VXL documentation on a Kitware server. > > > > (a) http://kitware.com/vxl/ > > (b) http://kitware.com/vxl/doxygen/release/ > > (c) http://kitware.com/vxl/doxygen/development/ > > Great! Seems like a very reasonable setup. > > > > 1. Shall we move the "main" VXL pages from SourceForge > > to Kitware (http://kitware.com/vxl)? > > I wouldn't do that. > Depends of course on the ease of maintaining one or the other. > > > > 3. I'd like to set (b) and (c) as "the" documentation pages, with > > the Manchester and Brown pages labelled mirrors. > > Agreed. > > -- Peter. > > > > > > > > > > > > > > > -- > > > __________________________________________________________ > L=E5na pengar utan s=E4kerhet. J=E4mf=F6r vilkor online hos Yahoo! > http://shopping.yahoo.se/c-100390123-lan-utan-sakerhet.html?partnerId=3D9= 6915014 > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Vxl-maintainers mailing list > Vxl-maintainers@... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > |
From: Amitha Perera <amitha@th...> - 2008-01-18 19:05:56
|
Just a heads up: the actual server will be public.kitware.com, not http://www.kitware.com (or kitware.com); the latter is for the commercial side of Kitware, and the former for the open source side. I'll send an updated link set when I've moved the files. Amitha. |
From: Peter Vanroose <peter_vanroose@ya...> - 2008-01-18 18:36:47
|
> I've set up the VXL documentation on a Kitware server. > > (a) http://kitware.com/vxl/ > (b) http://kitware.com/vxl/doxygen/release/ > (c) http://kitware.com/vxl/doxygen/development/ Great! Seems like a very reasonable setup. > 1. Shall we move the "main" VXL pages from SourceForge > to Kitware (http://kitware.com/vxl)? I wouldn't do that. Depends of course on the ease of maintaining one or the other. > 3. I'd like to set (b) and (c) as "the" documentation pages, with > the Manchester and Brown pages labelled mirrors. Agreed. -- Peter. -- __________________________________________________________ Låna pengar utan säkerhet. Jämför vilkor online hos Yahoo! http://shopping.yahoo.se/c-100390123-lan-utan-sakerhet.html?partnerId=96915014 |
From: Amitha Perera <amitha@th...> - 2008-01-18 16:34:57
|
I've set up the VXL documentation on a Kitware server. (a) http://kitware.com/vxl/ (b) http://kitware.com/vxl/doxygen/release/ (c) http://kitware.com/vxl/doxygen/development/ I invite comments on the following: 1. Shall we move the "main" VXL pages from SourceForge to Kitware (http://kitware.com/vxl)? We can make vxl.sourceforge.net automatically redirect. 2. Link (b) is the generated documentation for the latest vxl release, and will be updated on each release. Link (c) is the generated documentation from the CVS tree, and will be updated much more frequently (most likely nightly). Both will be *copies* of an off-line generation, so that if a particular nightly build fails, the web pages will still be available but slightly out of date. Does this seem reasonable? 3. I'd like to set (b) and (c) as "the" documentation pages, with the Manchester and Brown pages labelled mirrors. Thoughts? 4. The "search this documentation tree" needs to be updated. I'll look at that. Amitha. |
From: Brendan McCane <brendan.mccane@gm...> - 2008-01-16 01:59:29
|
-- Cheers, Brendan |
From: Amitha Perera <amithaperera@us...> - 2008-01-14 14:12:20
|
Kitware is willing to host the vxl documentation. I'll sort out the details and post back within the week. Amitha. |
From: Brendan McCane <brendan.mccane@gm...> - 2008-01-14 04:31:24
|
Hi Fred, That's great - thanks. On 12/01/2008, Wheeler, Frederick W (GE, Research) <wheeler@...> wrote: > > I just tested it with MSVC 8.0. Everything built. 4 tests failed. > Install process seemed to work. > > The following tests FAILED: > 481 - pseudo_match_2d_mult_test (OTHER_FAULT) > 597 - bmrf_test_network (OTHER_FAULT) > 610 - vifa_test_int_faces_attr (OTHER_FAULT) > 611 - vifa_test_int_faces_adj_attr (OTHER_FAULT) > > The build process I used is below. Let me know if there is anthing else > that should be done or if there is anything that should be done > differently to test a release. > > Fred > > ######################################################################## > #### > > ## test VXL release with MSVC 8.0 on laptop > > DEVTOPWIN="`cygpath -m $DEVTOP`" > cd "$DEVTOPWIN" > # get zip file > unzip vxl-1.10.0-beta1.zip > > mkdir vxlrel_bld > mkdir vxlrel_usr > cd vxlrel_bld > > . $HOME/etc/config/vsvars32_80.sh > > "c:/Program Files/CMake 2.4/bin/cmake" \ > -G"NMake Makefiles" \ > -DCMAKE_INSTALL_PREFIX:PATH="$DEVTOPWIN/vxlrel_usr" \ > -DCMAKE_BUILD_TYPE:STRING=Release \ > -DWXWIDGETS_ROOT_DIR:PATH="$DEVTOPWIN/wxWidgets-2.6.3" \ > -DBUILD_VGUI:BOOL=YES \ > "$DEVTOPWIN/vxl-1.10.0-beta1" > > time nice -20 nmake > time nmake test > time nmake install > > ######################################################################## > #### > > > -----Original Message----- > From: vxl-maintainers-bounces@... > [mailto:vxl-maintainers-bounces@...] On Behalf Of > Brendan McCane > Sent: Thursday, January 10, 2008 8:45 PM > To: vxl-maintainers > Subject: [Vxl-maintainers] Anyone tested 1.10-beta1 yet? > > G'day All, > > Just wondering if anyone has tested 1.10 yet? One possible glitch is > that Ian's fix for multi-plane image saving won't be in 1.10. Should it > be? > > -- > Cheers, > > Brendan > > ------------------------------------------------------------------------ > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for just about anything Open > Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketp > lace > _______________________________________________ > Vxl-maintainers mailing list > Vxl-maintainers@... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > -- Cheers, Brendan |
From: Wheeler, Frederick W (GE, Research) <wheeler@cr...> - 2008-01-11 15:53:16
|
I just tested it with MSVC 8.0. Everything built. 4 tests failed. Install process seemed to work. The following tests FAILED: 481 - pseudo_match_2d_mult_test (OTHER_FAULT) 597 - bmrf_test_network (OTHER_FAULT) 610 - vifa_test_int_faces_attr (OTHER_FAULT) 611 - vifa_test_int_faces_adj_attr (OTHER_FAULT) The build process I used is below. Let me know if there is anthing else that should be done or if there is anything that should be done differently to test a release. Fred ######################################################################## #### ## test VXL release with MSVC 8.0 on laptop DEVTOPWIN=3D"`cygpath -m $DEVTOP`" cd "$DEVTOPWIN" # get zip file unzip vxl-1.10.0-beta1.zip mkdir vxlrel_bld mkdir vxlrel_usr cd vxlrel_bld . $HOME/etc/config/vsvars32_80.sh "c:/Program Files/CMake 2.4/bin/cmake" \ -G"NMake Makefiles" \ -DCMAKE_INSTALL_PREFIX:PATH=3D"$DEVTOPWIN/vxlrel_usr" \ -DCMAKE_BUILD_TYPE:STRING=3DRelease \ -DWXWIDGETS_ROOT_DIR:PATH=3D"$DEVTOPWIN/wxWidgets-2.6.3" \ -DBUILD_VGUI:BOOL=3DYES \ "$DEVTOPWIN/vxl-1.10.0-beta1" time nice -20 nmake time nmake test time nmake install ######################################################################## #### =20 -----Original Message----- From: vxl-maintainers-bounces@... [mailto:vxl-maintainers-bounces@...] On Behalf Of Brendan McCane Sent: Thursday, January 10, 2008 8:45 PM To: vxl-maintainers Subject: [Vxl-maintainers] Anyone tested 1.10-beta1 yet? G'day All, Just wondering if anyone has tested 1.10 yet? One possible glitch is that Ian's fix for multi-plane image saving won't be in 1.10. Should it be? -- Cheers, Brendan ------------------------------------------------------------------------ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketp lace _______________________________________________ Vxl-maintainers mailing list Vxl-maintainers@... https://lists.sourceforge.net/lists/listinfo/vxl-maintainers |
From: Sam Hasinoff <hasinoff@cs...> - 2008-01-11 02:28:02
|
From: Brendan McCane <brendan.mccane@gm...> - 2008-01-11 01:44:34
|
G'day All, Just wondering if anyone has tested 1.10 yet? One possible glitch is that Ian's fix for multi-plane image saving won't be in 1.10. Should it be? -- Cheers, Brendan |
From: Ian Scott <ian.m.scott@st...> - 2008-01-10 16:51:12
|
Amitha Perera wrote: > sf.net provides 100Mb of project space. If the core documentation part > fits within this limit[*], Well I have just finished a build of the documentation for vxl-1.10, and it is 362Mb. Does anyone else want to volunteer to host it. If so you can find it in the VXL file release system. If not, I will ask SF if we can more quota. Ian. |
From: Amitha Perera <amithaperera@us...> - 2008-01-10 15:20:04
|
Ian Scott wrote: > If there is a simple way to publish it on SF then we can do that. > However, I don't want to put all the doxygen and texi output into the > CVS repository, which is how we currently mange the SF website. There is > somewhere between 100 and 300Mb of documentation, and minor changes to > the documentation control files or doxygen versions can result in every > html file needing to be stored in full. sf.net provides 100Mb of project space. If the core documentation part fits within this limit[*], then we can generate the documentation somewhere and rsync it to the sourceforge space. If the rsync process only runs when the documentation generation process successfully completes, sourceforge will always contain an accessible copy of the documentation. Right now, we are using a little bit of the 100Mb for the webpages. I can't tell exactly how much because I'm having trouble logging into the sourceforge shell. Amitha. [*] We could also request a space increase. |
From: Ian Scott <ian.m.scott@st...> - 2008-01-10 09:40:06
|
I was going to suggest that we change the doc hosting scheme sometime soon anyway. The current scheme at on paine.man.ac.uk generates the doc in place, so when something goes wrong, there is no existing copy the system can display instead. The system also spews vast amounts of diagnostic output into hundreds of files, making it rather hard to track down the errors in the texi or c++/doxygen source that cause the build to fail. I run a manual documentation build inside imorphics occasionally. I would be happy to run a full documentation build for VXL every time there is a release. I can tar it up, and send it to anybody who is willing to host it. If there is a simple way to publish it on SF then we can do that. However, I don't want to put all the doxygen and texi output into the CVS repository, which is how we currently mange the SF website. There is somewhere between 100 and 300Mb of documentation, and minor changes to the documentation control files or doxygen versions can result in every html file needing to be stored in full. Ian. Amitha Perera wrote: > I'll look into doing the documentation on SourgeForge when I'm back in > the office on Monday. > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Vxl-maintainers mailing list > Vxl-maintainers@... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers |
From: Tim Cootes <tim.cootes@ma...> - 2008-01-10 07:29:31
|
Hi Folks, Strictly I'm responsible for that server, as Ian is now at imorphics. My colleague David Cristinacce has been looking into it, but isn't yet = familiar enough with the set up to guarantee a quick fix. I'll keep you posted on progress. Tim Tim Cootes Professor of Computer Vision Imaging Science and Biomedical Engineering tel (+44) 0161 275 5146 The University of Manchester fax (+44) 0161 275 5145 Manchester M13 9PT , UK mailto:t.cootes@... = http://www.isbe.man.ac.uk/~bim -----Original Message----- From: vxl-maintainers-bounces@... on behalf of Amitha = Perera Sent: Thu 1/10/2008 4:09 AM To: Brendan McCane Cc: Joseph Mundy; vxl-maintainers Subject: Re: [Vxl-maintainers] vxl book? =20 I'll look into doing the documentation on SourgeForge when I'm back in=20 the office on Monday. -------------------------------------------------------------------------= Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpl= ace _______________________________________________ Vxl-maintainers mailing list Vxl-maintainers@... https://lists.sourceforge.net/lists/listinfo/vxl-maintainers |
From: Amitha Perera <amithaperera@us...> - 2008-01-10 04:10:52
|
Matt Leotta wrote: > Personally I don't see any reason to keep 3.2.x either, but maybe others do. I second. |