Menu
▾
▴
irbem-developpers — Mailing list to reach all irbem developpers
You can subscribe to this list here.
| 2013 |
Jan
|
Feb
|
Mar
(7) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Paul O. <Pau...@ae...> - 2013-03-08 14:00:59
|
Hi folks, I did make it work, but I had to switch svn+ssh:// to https:// because my firewall does not allow svn to just any old host. Also, for those of you like me who check out more than just trunk, you'll want to do something like this: svn co --username=tpoiii https://tp...@sv.../p/irbem/code irbem That will make a folder called irbem just like the old top-level irbem folder, with subfolders like trunk, tags, extras, docs, web, etc. Also, for those of you like me who want to copy all your non-version controlled stuff over into the new repo, you can use this approach: cd ~/ mv irbem irbem.old svn co --username=tpoiii https://tp...@sv.../p/irbem/code irbem cd irbem.old yes 'n' | \cp -i -r * ~/irbem/ That last bit will copy everything from irbem.old into irbem, but will not overwrite files that already exist in the new repo. Thus, it will only copy files that are not under version control and are not part of svn's own bits and pieces. -paul --------- T. Paul O'Brien, PhD Space Science Department/Chantilly The Aerospace Corporation 15049 Conference Center Drive, CH3/330 Chantilly, VA 20151-3824 Greens III, 3043 571-307-3978 571-307-1881 FAX From: Seb...@on... To: irb...@li..., Date: 03/08/2013 06:23 AM Subject: [Irbem-developers] Project upgrade Dear irbem-developers, The IRBEM upgrade on sourceforge has been done succesfully. Any change to the old repositery will not be tken into account on the new sourceforge system. You should have recieved Emails from sourceforge where new details are provided. Isn't it? From my understanding (I still have to dig on the new system): Read only access to the repositery can be done at http://svn.code.sf.net/p/irbem/ (but I can't find how to get a "gnu tarball" as it was available before) For RW access you have to change my login to yours: svn checkout --username=bourdari svn+ssh://bou...@sv.../p/irbem/code/trunk irbem-code I have to make the changes in my eclipse SVN to check if it is fine... Paul: the IRBEM project web pages must be changed accordingly. Most links have to be modified ... and I try to find where is the project homepage (on the new system)... After those changes are OK I will submit an annoucement to SPA newsletter: Bes regards, Sebastien [attachment "Sebastien_Bourdarie.vcf" deleted by Paul OBrien/West/Aerospace/US] ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Irbem-developpers mailing list Irb...@li... https://lists.sourceforge.net/lists/listinfo/irbem-developpers |
|
From: <Seb...@on...> - 2013-03-08 11:23:17
|
Dear irbem-developers, The IRBEM upgrade on sourceforge has been done succesfully. Any change to the old repositery will not be tken into account on the new sourceforge system. You should have recieved Emails from sourceforge where new details are provided. Isn't it? From my understanding (I still have to dig on the new system): Read only access to the repositery can be done at http://svn.code.sf.net/p/irbem/ (but I can't find how to get a "gnu tarball" as it was available before) For RW access you have to change my login to yours: svn checkout --username=bourdari svn+ssh://bou...@sv.../p/irbem/code/trunk irbem-code I have to make the changes in my eclipse SVN to check if it is fine... Paul: the IRBEM project web pages must be changed accordingly. Most links have to be modified ... and I try to find where is the project homepage (on the new system)... After those changes are OK I will submit an annoucement to SPA newsletter: Bes regards, Sebastien |
|
From: <Seb...@on...> - 2013-03-07 11:53:39
|
Hi, I have updated the mailing list of IRBEM developers. Now, I believe, all identifed developers (those who can submit files on sourceforge) are in the mailing list. To change "developpers" into "developers", there is no choice than creating a new mailing list on sourceforge. I will do that on the new sourceforge system (see below). Also note that the I have to upgrade IRBEM project on sourceforge. This is recommended by sourceforge. The existing system will not be available any longer. The effect will be a change in the web address to access the project (project web pages and repositery). The new links will be provided after the upgrade is done. I will let you know then and will put an annoucement in SPA newsletter. I am ready to perform this change. I will do it tomorow morning (friday morning). If you have any problem with this change please let me know before end of today. Best regards, Sebastien |
|
From: Paul O. <Pau...@ae...> - 2013-03-06 18:22:54
|
It sounds like everyone concurs that we should harmonize the different array the field line dimension of the drift routines as well, and put it into the variables.inc file. I already made an attempt that this before I discovered that it would impact both sets of routines. So, I will take this one. I should get to it in the next week or so. I will fix the matlab wrappers as well. -paul --------- T. Paul O'Brien, PhD Space Science Department/Chantilly The Aerospace Corporation 15049 Conference Center Drive, CH3/330 Chantilly, VA 20151-3824 Greens III, 3043 571-307-3978 571-307-1881 FAX From: Hug...@es... To: Paul OBrien <Pau...@ae...>, Cc: DHC...@sk..., Seb...@on..., irb...@li... Date: 03/06/2013 11:30 AM Subject: Re: [Irbem-developpers] IRBEM-LIB significant bug fix to field line tracing Hi Paul, In reverse order to your queries: 1. As you can see, I received a copy so the email list appears to distribute to at least me. ;-) 2. "developer" is correct for English, European English and American English (AFAIK). 3. I've often considered going through the library and moving the parameters and common block variables to separate include files. It does make it much easier and safer to maintain, but is a lot of (mind numbing) work. I'd be happy to help, though. Ta Hugh From: Paul OBrien <Pau...@ae...> To: Seb...@on..., DHC...@sk..., Cc: irb...@li... Date: 04/03/2013 15:56 Subject: [Irbem-developpers] IRBEM-LIB significant bug fix to field line tracing Hi folks, I just checked in a significant bug fix for the field line tracing. The high level fortran routines (e.g., in onera_desp_lib.f) had the long array dimension at 1000. The lower level routines had it a 3000. This was causing segmentation faults on long field line traces. This affects trace_field_line and trace_field_line_toward_earth and their family of routines. I put up a news item about it on the web page. It does not affect L*, drift shell, and drift orbit tracing. As the code is presently organized it is not easy to determine or manage the array sizes in the various field line tracing routines. It may be worth considering a code consolidation so that those parameters appear in variables.inc. The issue with doing that is that at present the variable/parameter names are the same in the field line and drift shell tracing routines, but the values are different. Bringing everything into synch is a good idea, but it cannot be done without breaking some codes (in fact, the code was broken in exactly this way until the fix I just put in). Thoughts? Also, this is the first message to the irb...@li... email list. Did anyone other than Sebastien and Daniel get a copy? Would anyone care if we spelled developpers as developers? I don't know if that's European English (which is fine, then) or if it's just a misspelling by one of our non-native English speakers. -paul --------- T. Paul O'Brien, PhD Space Science Department/Chantilly The Aerospace Corporation 15049 Conference Center Drive, CH3/330 Chantilly, VA 20151-3824 Greens III, 3043 571-307-3978 571-307-1881 FAX ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Irbem-developpers mailing list Irb...@li... https://lists.sourceforge.net/lists/listinfo/irbem-developpers This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Irbem-developpers mailing list Irb...@li... https://lists.sourceforge.net/lists/listinfo/irbem-developpers |
|
From: <Hug...@es...> - 2013-03-06 16:30:25
|
Hi Paul, In reverse order to your queries: 1. As you can see, I received a copy so the email list appears to distribute to at least me. ;-) 2. "developer" is correct for English, European English and American English (AFAIK). 3. I've often considered going through the library and moving the parameters and common block variables to separate include files. It does make it much easier and safer to maintain, but is a lot of (mind numbing) work. I'd be happy to help, though. Ta Hugh From: Paul OBrien <Pau...@ae...> To: Seb...@on..., DHC...@sk..., Cc: irb...@li... Date: 04/03/2013 15:56 Subject: [Irbem-developpers] IRBEM-LIB significant bug fix to field line tracing Hi folks, I just checked in a significant bug fix for the field line tracing. The high level fortran routines (e.g., in onera_desp_lib.f) had the long array dimension at 1000. The lower level routines had it a 3000. This was causing segmentation faults on long field line traces. This affects trace_field_line and trace_field_line_toward_earth and their family of routines. I put up a news item about it on the web page. It does not affect L*, drift shell, and drift orbit tracing. As the code is presently organized it is not easy to determine or manage the array sizes in the various field line tracing routines. It may be worth considering a code consolidation so that those parameters appear in variables.inc. The issue with doing that is that at present the variable/parameter names are the same in the field line and drift shell tracing routines, but the values are different. Bringing everything into synch is a good idea, but it cannot be done without breaking some codes (in fact, the code was broken in exactly this way until the fix I just put in). Thoughts? Also, this is the first message to the irb...@li... email list. Did anyone other than Sebastien and Daniel get a copy? Would anyone care if we spelled developpers as developers? I don't know if that's European English (which is fine, then) or if it's just a misspelling by one of our non-native English speakers. -paul --------- T. Paul O'Brien, PhD Space Science Department/Chantilly The Aerospace Corporation 15049 Conference Center Drive, CH3/330 Chantilly, VA 20151-3824 Greens III, 3043 571-307-3978 571-307-1881 FAX ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Irbem-developpers mailing list Irb...@li... https://lists.sourceforge.net/lists/listinfo/irbem-developpers This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. |
|
From: DHConsultancy <DHC...@sk...> - 2013-03-06 16:15:53
|
I concur with Hugh. We could divide up the grunt work between us (meaning not just me and H!). On 06/03/2013 17:10, Hug...@es... wrote: > Hi Paul, > > In reverse order to your queries: > 1. As you can see, I received a copy so the email list appears to > distribute to at least me. ;-) > 2. "developer" is correct for English, European English and American > English (AFAIK). > 3. I've often considered going through the library and moving the > parameters and common block variables to separate include files. It does > make it much easier and safer to maintain, but is a lot of (mind > numbing) work. I'd be happy to help, though. > > Ta > Hugh > > > > From: Paul OBrien <Pau...@ae...> > To: Seb...@on..., DHC...@sk..., > Cc: irb...@li... > Date: 04/03/2013 15:56 > Subject: [Irbem-developpers] IRBEM-LIB significant bug fix to field > line tracing > > > ------------------------------------------------------------------------ > > > > Hi folks, > > I just checked in a significant bug fix for the field line tracing. The > high level fortran routines (e.g., in onera_desp_lib.f) had the long > array dimension at 1000. The lower level routines had it a 3000. This > was causing segmentation faults on long field line traces. This affects > trace_field_line and trace_field_line_toward_earth and their family of > routines. I put up a news item about it on the web page. > > It does not affect L*, drift shell, and drift orbit tracing. > > As the code is presently organized it is not easy to determine or manage > the array sizes in the various field line tracing routines. It may be > worth considering a code consolidation so that those parameters appear > in variables.inc. The issue with doing that is that at present the > variable/parameter names are the same in the field line and drift shell > tracing routines, but the values are different. Bringing everything into > synch is a good idea, but it cannot be done without breaking some codes > (in fact, the code was broken in exactly this way until the fix I just > put in). Thoughts? > > Also, this is the first message to the > irb...@li... email list. Did anyone other > than Sebastien and Daniel get a copy? Would anyone care if we spelled > developpers as developers? I don't know if that's European English > (which is fine, then) or if it's just a misspelling by one of our > non-native English speakers. > > -paul > > --------- > T. Paul O'Brien, PhD > Space Science Department/Chantilly > The Aerospace Corporation > 15049 Conference Center Drive, CH3/330 > Chantilly, VA 20151-3824 > Greens III, 3043 > 571-307-3978 > 571-307-1881 FAX > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb_______________________________________________ > Irbem-developpers mailing list > Irb...@li... > https://lists.sourceforge.net/lists/listinfo/irbem-developpers > > > This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. > > Please consider the environment before printing this email. > -- D. Heynderickx DH Consultancy Diestsestraat 133/3 B-3000 Leuven Belgium E-mail: DHC...@sk... Tel: +32-16-225860 GSM: +32-474-217768 |
|
From: Paul O. <Pau...@ae...> - 2013-03-04 14:56:50
|
Hi folks, I just checked in a significant bug fix for the field line tracing. The high level fortran routines (e.g., in onera_desp_lib.f) had the long array dimension at 1000. The lower level routines had it a 3000. This was causing segmentation faults on long field line traces. This affects trace_field_line and trace_field_line_toward_earth and their family of routines. I put up a news item about it on the web page. It does not affect L*, drift shell, and drift orbit tracing. As the code is presently organized it is not easy to determine or manage the array sizes in the various field line tracing routines. It may be worth considering a code consolidation so that those parameters appear in variables.inc. The issue with doing that is that at present the variable/parameter names are the same in the field line and drift shell tracing routines, but the values are different. Bringing everything into synch is a good idea, but it cannot be done without breaking some codes (in fact, the code was broken in exactly this way until the fix I just put in). Thoughts? Also, this is the first message to the irb...@li... email list. Did anyone other than Sebastien and Daniel get a copy? Would anyone care if we spelled developpers as developers? I don't know if that's European English (which is fine, then) or if it's just a misspelling by one of our non-native English speakers. -paul --------- T. Paul O'Brien, PhD Space Science Department/Chantilly The Aerospace Corporation 15049 Conference Center Drive, CH3/330 Chantilly, VA 20151-3824 Greens III, 3043 571-307-3978 571-307-1881 FAX |
