wavepacket-ng-devel — List for development topics (C++-version)

Re: [Wavepacket-ng-devel] SourceForge user names

[Sakthi <sak...@gm...>]

Hi all,
       my sf username is : codingprince

Also I have another question. I would like to ask the for the choice of OS.
I am so used to linux and unix like systems and did nothing on windows . So
it'd be nice to know the OS choice ?



Thanks.

-Sakthivel Sundaresan
*Whatever you do, work at it wholeheartedly as though you were doing it for
the Lord and not merely for people.
Col 3.23 (ISV)
*


On Mon, Dec 3, 2012 at 4:56 AM, Andrea at dotIT <me...@an...> wrote:

> Hi there,
>
> this is my SF account: agirardi77
>
> Andrea
>
>
> On Sun, Dec 2, 2012 at 11:46 PM, Ulf Lorenz <ul...@wa...> wrote:
>
>> Hi again,
>>
>> another thing: I would like to add all of you to the project, so that
>> you can get write permissions for the wiki, repository etc. For this,
>> you need to get a sourceforge account if you do not have one yet, and
>> tell me the account name. Please do so.
>>
>>
>> Ulf
>>
>>
>> ------------------------------------------------------------------------------
>> Keep yourself connected to Go Parallel:
>> DESIGN Expert tips on starting your parallel project right.
>> http://goparallel.sourceforge.net/
>> _______________________________________________
>> Wavepacket-ng-devel mailing list
>> Wav...@li...
>> https://lists.sourceforge.net/lists/listinfo/wavepacket-ng-devel
>>
>
>
>
> --
> "Experience is what you get when you don't get what you want", Dan Stanford
>
> Andrea Girardi
> blog: http://www.andreagirardi.it
> linkedin: http://www.linkedin.com/in/andreagirardiverona
> web http://www.agdev.net
>
>
>
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel:
> DESIGN Expert tips on starting your parallel project right.
> http://goparallel.sourceforge.net/
> _______________________________________________
> Wavepacket-ng-devel mailing list
> Wav...@li...
> https://lists.sourceforge.net/lists/listinfo/wavepacket-ng-devel
>
>

Re: [Wavepacket-ng-devel] Version control system

[Sakthi <sak...@gm...>]

Hello Ulf and all,
      I have the working  experience of working with mercurial. It is quite
easy to get started .If you have any specific questions, please shoot and
we can discuss on those.

Thanks.

-Sakthivel Sundaresan

*Whatever you do, work at it wholeheartedly as though you were doing it for
the Lord and not merely for people.
Col 3.23 (ISV)
*


On Mon, Dec 3, 2012 at 4:14 AM, Ulf Lorenz <ul...@wa...> wrote:

> s anyone have any

Re: [Wavepacket-ng-devel] SourceForge user names

[Andrea at d. <me...@an...>]

Hi there,

this is my SF account: agirardi77

Andrea

On Sun, Dec 2, 2012 at 11:46 PM, Ulf Lorenz <ul...@wa...> wrote:

> Hi again,
>
> another thing: I would like to add all of you to the project, so that
> you can get write permissions for the wiki, repository etc. For this,
> you need to get a sourceforge account if you do not have one yet, and
> tell me the account name. Please do so.
>
>
> Ulf
>
>
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel:
> DESIGN Expert tips on starting your parallel project right.
> http://goparallel.sourceforge.net/
> _______________________________________________
> Wavepacket-ng-devel mailing list
> Wav...@li...
> https://lists.sourceforge.net/lists/listinfo/wavepacket-ng-devel
>



-- 
"Experience is what you get when you don't get what you want", Dan Stanford

Andrea Girardi
blog: http://www.andreagirardi.it
linkedin: http://www.linkedin.com/in/andreagirardiverona
web http://www.agdev.net

[Wavepacket-ng-devel] Programming language

[Ulf L. <ul...@wa...>]

Another thing that came to my mind between the project help request and
now is that there is another option for the programming language.

Basically, there are two ways (there are more, but they will not be
more attractive...).

We can use C++, especially C++-11, as suggested in the help request.
There is little to say here. However, an alternative that I came across
would be to use Java.

The advantages, which brought up the whole idea:

+ It has much better integration in IDE's and with testing toolkits
  (JUnit, JMock etc.)

+ It is an easier language for the end user; garbage collection does
  not need to be kind of added, and there are less horrible language
  features than for C++.

+ Deployment is way easier. If we could implement the basic algorithms
  in Java only or find a library, one could have a stand-alone Java
  program in the end. Imagine a course on some quantum mechanics, and
  the students could just download a jar file and write their programs
  without having to compile or care about operating systems and such
  (of course, with a considerable performance penalty, but that might
  not be a big issue for small demo systems and today's computers).

+ Possibly easier scripting language support. I know that at least
  Matlab supports directly importing and working with java objects from
  scratch. Possibly something like this might hold for other scripting
  languages as well.


However, some disadvantages:

- there is some performance penalty associated with the use of Java. I
  once did a search and only found a factor of >= 2 in runtime for raw
  numerics; I have no idea how much the overhead would be for the rest
  of the code.

- I did not find good Java-only numerical libraries. Also, for
  performance reasons, we would have to interface the low-level
  numerical details (matrix handling, FFT and such) with
  platform-dependent code. I have no idea how well this works, what
  quirks there are and so on. Also, the project would then
  probably contain different programming languages, build systems etc.,
  which is kind of ... unaesthetic.

- It might be that for some (large?) setups, setting up a Java Runtime
  environment is not trivial (e.g., parallel computing), so it might be
  that we effectively block this kind of usage. On the other hand, for
  large setups, people will usually write their own wavepacket code
  that is not portable to other problems, but well adapted to the
  targeted problem, which we will have a hard time beating anyway, or
  use a big monster like MCTDH, which is difficult to handle, but can
  handle large problems with additional approximations.


I am not really decided either way, and as written, I have no feeling
for several of the points, so I would put this to discussion and joint
decision. Feel free to discuss and give a verdict. It might also be
that we agree on testing something out, that would also be fine.


Ulf

[Wavepacket-ng-devel] SourceForge user names

[Ulf L. <ul...@wa...>]

Hi again,

another thing: I would like to add all of you to the project, so that
you can get write permissions for the wiki, repository etc. For this,
you need to get a sourceforge account if you do not have one yet, and
tell me the account name. Please do so.


Ulf

[Wavepacket-ng-devel] Version control system

[Ulf L. <ul...@wa...>]

Hi,

another thing that needs to be discussed and decided on is the version
control system. Unfortunately, I have not too much experience with
anything except subversion, so I hope you can help here.

The offered systems are subversion, git, and mercurial. Since branching
might be a realistic use-case (and to learn something new, and
because I found I commonly need logs and diffs, which take ages with
svn), I would suggest not to use subversion, but go for one of the
distributed VCS.

Does anyone have any experience with git or mercurial? And/Or which one
would you prefer?


Ulf

[Wavepacket-ng-devel] Project name

[Ulf L. <ul...@wa...>]

First thing to decide on: How do we want to name the project?

There are two names: The public name (what labels appear and so on),
and an internal name that serves as the link on the sourceforge pages.

So how would we call the new subproject? It should be clearly related
to WavePacket, but somehow be set apart from the "normal" project.
Ideas I can come up with right now:

WavePacket-ng
WavePacket++
OOWavePacket

Other ideas?

For the internal name, I have used wavepacket-ng for now (ng = next
generation). We can change this to another one, however, I do not know
what characters are allowed (probably alphanumeric + "-"). Ideas?


Ulf

[Wavepacket-ng-devel] Todo list

[Ulf L. <ul...@wa...>]

Hi,

I had a quick talk with Andrea today (that was a random choice, he was
the first to ask for my status), and summarized a set of things to do
before we start with the coding. I would detail each item in a separate
mail, and hope for some discussion. :)

1. We need to decide on a revision control system

2. Assemble a reading list
   Since you are all computer scientists with a bit of background, and
   have not worked with wavepacket propagation, it would be a good idea
   to spend some time on refreshing the math/physics background.
   I would talk this over with Burkhard, which books would be a good
   read for introduction and the numerical stuff, and what
   knowledge or topics you should aim for as an orientation.

3. Add you to the project, so that you have permission to modify things.

4. Naming the project

5. Decide on a ticket system to keep track of what is being done, to do
   etc.

6. Update the roadmap / tasks what to do
   Since we are now 4 people, we are enough for two parallel
   development tracks. The current, very primitive, roadmap does not
   accomodate that.

7. Converge to a coherent objective (mostly I have to write the
   motivation in a way that is, well, motivating, but if you have
   input, that would be fine).

8. I had a bit more ideas regarding programming language. This I would
   like to discuss.


If 8. is settled, a few more things have to be discussed:

9. We need to decide on a build system.

10. We need to come up with some coding conventions as far as it makes
    sense now.

11. We need to figure out and play around a bit with prospective
    libraries.


Ulf

[Wavepacket-ng-devel] Mailing list problems hopefully solved

[Ulf L. <ul...@wa...>]

Hi,

just for your information: There seem to be some bugs concerning
mailing lists in subprojects, which made the source forge server
randomly drop mails to the list. As a result, I have dropped this, and
created the list in the main context. This has the additional advantage
that the mailing list name is a bit more comprehensive.

I will leave it at that now, and start using the list.


Ulf