sourceryinstitute/opencoarrays

OpenCoarrays Support Channel

Damian Rouson

@rouson

Both links work now. I love this feature! Just bookmarked it.

Izaak "Zaak" Beekman

@zbeekman

Yup, it's neat... we can adjust the Pull Request rules (and maybe the inporgress rules) if you want to modify them. You can create new columns too, assign issues to people, add tags, etc.

sfilippone

@sfilippone

Hi Zaak, I'm in

If you can see my messages, then we're ok

Izaak "Zaak" Beekman

@zbeekman

Hi Salvatore! Yes I can... I was trying to add you to the private SourceryInstitute channel, however... It's fine though, we can probably chat here if that's OK with @rouson otherwise I think we would need to add you to the SourceryInstitute organization (on github)

to get into the other room

Izaak "Zaak" Beekman

@zbeekman

@sfilippone I don't know if you saw my most recent comment on #164 but I think I know the source of the problem, and it should already be fixed on master

sfilippone

@sfilippone

No, I didn't see it. But I'm now at home, will try again with master version tomorrow.

Izaak "Zaak" Beekman

@zbeekman

OK no rush. I'm fairly confident the next release (and master version) fixes the issue with gcc 6. In the mean time gcc 5.3 should still work (but the latest gcc 5 branch has the same commits as trunk/6, I believe)

sfilippone

@sfilippone

I can confirm the master version builds cleanly.

Izaak "Zaak" Beekman

@zbeekman

Great, thanks! Also, I have added you to the SourceryInstitute organization on Github, per Damian's request. Once you check the invitation in your email and accept, we will be able to add you to the SI only chat room

Izaak "Zaak" Beekman

@zbeekman

@rouson Can I rebase the branch, and push new changes to it, or should I work from a different branch (i.e. are you still working or is it done?)

Izaak "Zaak" Beekman

@zbeekman

@rouson also, if you like, you can start drafting release notes here: https://github.com/sourceryinstitute/opencoarrays/releases/edit/untagged-ae25742153f809093723 I can take care of the final signing, upload, etc.

Izaak "Zaak" Beekman

@zbeekman

@rouson I also noticed that the usage statement for check_version.sh might be a little bit outdated/wrong... there's a reference to a script named 'build' (not build.sh) with some options that don't appear to be supported any more (--query-verison, --default)

Damian Rouson

@rouson

Another great catch! I'll take a quick look.

@zbeekman. It's an easy fix. I can push a new commit or you can just replace the text

./build flex --default --query-version

with the text

./build.sh -V flex

Izaak "Zaak" Beekman

@zbeekman

OK, great. I'll jsut replace it

I'm mid rebase with a bunch of edits

oops, I'm using the wrong gitter room... oh well, no matter

luiceur

@luiceur

Hello

Izaak "Zaak" Beekman

@zbeekman

Hi @luiceur, welcome to the OpenCoarrays support channel. How may we help you?

Damian Rouson

@rouson

@zbeekman I I just created draft release notes for a new 1.7.4 release. Please release it at your earliest convenience.

Izaak "Zaak" Beekman

@zbeekman

Great! I should be able to get to it tonight

Damian Rouson

@rouson

@zbeekman, the tests passed and I merged the latest fixes into the master branch. I think we're ready for release as soon as you can get it out.

Izaak "Zaak" Beekman

@zbeekman

I just released. Let me know if you spot any issues.

Izaak "Zaak" Beekman

@zbeekman

@rouson I'm second guessing myself regarding some CAF semantics. Can you please confirm that there is no synchronization needed between the following two statements:

b(:) = a(:)[me+1]
matches = all( a_local(:) == b(:) )

i.e., the local image won't proceed until the assignment on line one completes

Izaak "Zaak" Beekman

@zbeekman

A pull request has been submitted to Homebrew to get OpenCoarrays into the homebrew package manager for OS X (and at some later date this will get pulled into linuxbrew): Homebrew/homebrew-core#8790

Izaak "Zaak" Beekman

@zbeekman

I am pleased to announce that OpenCoarrays is now available through the Homebrew package manager for OS X!

brew update
brew install --cc=gcc-6 OpenCoarrays # to get gcc to build the library... should also build fine with clang

Neil Carlson

@nncarlson

Hello! I'm finally dipping my toes into coarrays. I've got the master branch built with mpich 3.2 and gcc 6.3.1 and have successfully run the little tally.f90 from the GETTING_STARTED.md file. Now I'm looking for further simple example coarray programs. Are there some web pages or wikis out there where I can find such things?

Izaak "Zaak" Beekman

@zbeekman

Hmmmm well no wiki yet, you're welcome to create a FAQ with questions and we can try to answer them. As for documentation, FORD is in the works.

But have a look in the tests directory for examples. Unit tests are simplest. Also, you could try some of the examples from Damian's book, if you have access.

@rouson or @sfilippone might have some additional ideas.

Jerry DeLisle

@jerryd

Is there a way for this chat window to be out of browser? Is this chatroom private?

Izaak "Zaak" Beekman

@zbeekman

This chat is public

There's a native and phone app

We have a private chat for SI org

I'll look into whether non members can be added if you're interested

Izaak "Zaak" Beekman

@zbeekman

Yes, the private SI chat means you must be member of SI org, which for pricing reasons (which could be fixed... but...) right now it looks like you won't be able to join the private chat

Stefano Zaghi

@szaghi

Dear @zbeekman @rouson I have a problem with your great install.sh script. I am pushing my bosses to adopt opencoarrays, but they are strongly addicted to CentOS, and they are essentially paranoiac (root installation is not viable). The big issue is to install a recent gcc. Indeed, we have manually compiled installed gcc 6.2, but we have problem with gcc 6.3, thus I tried to exploit you script (that I used every week to update my local gcc-developing-trunk). However, I was not able to understand how to set the installer to point to 6.3 trunk instead of 6.1 (the default one). The syntax I use for the developing trunk is:

/install.sh -p gcc -b trunk -i /opt/gcc/bin/7.0.0

Can you let me know how to execute the script for installing 6.3 trunk?
Thank you very much for help!
Cheers

Damian Rouson

@rouson

Hi, Stefano. Thanks for your interest and especially for sharing with us your frequent use of the installation script. You can install any released versions using the --install-version or the equivalent -I option:

./install.sh -p gcc -I 6.3.0 -i /opt/gcc/bin/6.3.0

BTW, there exists a such a broad range of users: some refuse to use anything but a static Makefile; others prefer to use CMake; others use package management; others exclusively use the bash installation script install.sh. I believe we have to support as many installation options as possible and it's great to hear which option important users like you are choosing. Thanks for letting us know!

Stefano Zaghi

@szaghi

@rouson
Dear Damian,

BTW, there exists a such a broad range of users: some refuse to use anything but a static Makefile; others prefer to use CMake; others use package management; others exclusively use the bash installation script install.sh

:smile: I know. My bosses refuse all but CentOS... it is really a nightmare, not only for Fortran just think to LaTeX: using recent LaTeX packages, namely less old than 10 years becomes quickly a problem :smile:

Currently my workflow is strongly based on OpenCoarrays:

I use OpenCoarrays for CAF projects (mainly HASTY);
- I use OpenCoarrays script to install (weekly/monthly) the latest gcc trunk for all Fortran projects;
I use Zaak's docker image for gcc nightly build (occasionally to check if some compiler's issues evolves);
now I will use OpenCoarrays script to install the latest gcc stable on my bosses' workstation :smile:

Thank you very much for the help, you rocks!

P.S. could you be interest on a very abstract designing of Fortran CFD libraries? I recently made important steps toward a really abstract CFD code exploiting many abstract libraries (obviously into which is FOODIE, FOODIE paper will be completed soon...)

Izaak "Zaak" Beekman

@zbeekman

Stefano, great news about FOODIE and your progress! Glad to hear that you're finding the installation script and other tools useful. Just FYI, as far as I know, you can either build a released GCC, OR the latest trunk, but you can't build, e.g., the latest GCC-6 branch... you have to use a release. (I just wanted to clarify that point, based on your original comment/question)

Stefano Zaghi

@szaghi

@zbeekman Dear Zaak, thank you for the clarification, you have anticipated my goal, build the latest 6-branch... :smile: Cheers

Izaak "Zaak" Beekman

@zbeekman

You could edit the script to build the 6 branch...

Damian Rouson

@rouson

@szaghi, yes, I'm very interested. It fits nicely with other things I'm working on. Please schedule some time for us to talk about what you're doing.

@zbeekman, if you're referring to the installer, it should be possible to install any (unreleased) branch, including non-trunk branches, using the --install-branch flag. For example, "./install.sh --install-branch gcc-6-branch" should install the pre-release GCC 6 branch. To see a list of all branches, use "./install.sh --list-branches gcc" or "./install.sh -B gcc".

Stefano Zaghi

@szaghi

@rouson Dear Damian, sure, soon you (and Zaak) will receive some email-spam from me :smile:

Where communities thrive

People

Repo info

Activity