by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 29 14:43
    gijzelaerr unassigned #983
  • May 27 11:09
    aroffringa synchronize #1012
  • May 27 10:57
    aroffringa synchronize #1012
  • May 26 15:33
    aroffringa commented #1024
  • May 26 15:33
    aroffringa commented #1024
  • May 26 15:33
    aroffringa synchronize #1024
  • May 26 15:24
    aroffringa edited #1024
  • May 26 15:24
    aroffringa edited #1024
  • May 26 15:23
    aroffringa ready_for_review #1024
  • May 26 15:19
    aroffringa synchronize #1024
  • May 26 15:12
    aroffringa synchronize #1024
  • May 26 14:18

    dpetry on master

    Use FFTW instead of FFTPack in … Call FFTW initialization functi… Make casacore compile without F… and 1 more (compare)

  • May 26 14:18
    dpetry closed #1029
  • May 26 14:18
    dpetry commented #1029
  • May 26 11:05
    tammojan closed #1032
  • May 26 11:05
    tammojan commented #1032
  • May 26 11:03

    tammojan on master

    Create "regular" UVFITS for LOF… Merge pull request #1033 from k… (compare)

  • May 26 11:03
    tammojan closed #1033
  • May 26 09:28
    aroffringa synchronize #1012
  • May 25 13:39
    dpetry commented #1029
Tammo Jan Dijkema
@tammojan
Not sure if this has screwed things up: casacore/casacore#132
No, existing symbols should not have changed.
Gijs Molenaar
@gijzelaerr
well, the signature of casa/Containers/Block.h looked changed
I don’t have a lot of experience with this, but I think you also want to start versioning your SO's

3.6. Incompatible Libraries

When a new version of a library is binary-incompatible with the old one the soname needs to change.

but that is something for the next release
but it is important to keep in mind
Tammo Jan Dijkema
@tammojan
If CASA_BUILD is true, then a lot of magic is done with so-versioning. So we should be very careful when we change something here. But indeed, so-versioning would be nice.
Gijs Molenaar
@gijzelaerr
you may find this interesting also
i'm looking into a way to auto package and upload tagged github repo's
which would save a lot of time and effort
Gijs Molenaar
@gijzelaerr
we can now use arbitrary contains on travis! http://blog.travis-ci.com/2015-08-19-using-docker-on-travis-ci/
Simon Perkins
@sjperkins
Question for @gervandiepen or @tammojan. Does the measures server created in python-casacore frequently hit disk to perform it's operations? Or does it perform a once off load of the measures data everytime a measures server object is created?
Tammo Jan Dijkema
@tammojan
The underlying c++ measures has caches that are set up upon the first conversion. Since the python layer is quite thin, I think this will hold for python as well.
Adam Ginsburg
@keflavich
hey folks, what’s the interaction between casacore and the NRAO-distributed CASA application? How closely are you guys communicating? (I’m at NRAO in Socorro)
Tammo Jan Dijkema
@tammojan
The CASA developers are part of the casacore team as well. CASA builds on top of casacore. For some procedures see https://safe.nrao.edu/wiki/bin/view/Software/CASA/CasaCoreInfo
Is there anything specific you want to know?
Adam Ginsburg
@keflavich
thanks @tammojan. I have a question about running CASA without ipython that I've asked around here a bit, but still haven't gotten a good answer. I'm trying to run some py.test tests on a continuous integration server (travis-ci) using CASA (see radio-astro-tools/spectral-cube#312), and it appears that py.test won't work with ipython. So, is there any way / what is the best way to use CASA tasks within an environment that is not the usual CASA ipython terminal?
Tammo Jan Dijkema
@tammojan
This is a common problem, several people have tried several solutions.
You could install a minimal version of CASA; there is one in KERN called 'casalite' (a fork of CASA, so not supported by the people in Socorro).
Adam Ginsburg
@keflavich
could you link me to KERN? I've never heard of it
Tammo Jan Dijkema
@tammojan
Kernsuite.info
I don't know where casalite is hosted, but the location of the source should be somewhere in the build scripts.
Tammo Jan Dijkema
@tammojan
Adam Ginsburg
@keflavich
@tammojan - casa-python is something I've worked on; it lets you install packages into the CASA environment but it doesn't change anything about how CASA loads
Tammo Jan Dijkema
@tammojan
Is your goal to load CASA within your own python?
Perhaps this is also useful: http://www.mrao.cam.ac.uk/~bn204/publications/2016/2016-10-nix-casa.pdf , with an install script at https://github.com/bnikolic/casanix . You see: lots of people are trying to achieve this :)
Tammo Jan Dijkema
@tammojan
Unfortunately (?) I don't have experience with this myself, so I'm not sure what to advise you. The python layer is purely casa, which I'm not involved in.
Adam Ginsburg
@keflavich
Thanks! No, my goal is to run tests in an environment maximally similar to the "normal" CASA environment, but these other attempts might point me in the right direction
Adam Ginsburg
@keflavich
does anyone have installation suggestions / instructions for Mac OS, since apt-get can't be used to install the dependencies?
Tammo Jan Dijkema
@tammojan
We don't have a proper write-up. Perhaps this ticket can help: casacore/casacore#589 . As I wrote in the ticket, the dependencies can be installed with homebrew, the system compiler does work for me.
Adam Ginsburg
@keflavich
Thanks @tammojan. I tried again using env -i to sanitize my environment, but I am stuck at the same issue
Tammo Jan Dijkema
@tammojan
It helps to check the output of CMake, it lists the libraries quite nicely:
https://gist.github.com/tammojan/c53b9ce9cecb82c1627c7b1f776b3d23
In that output, you should check that the 2's and 3's line up.
The problem is that even if it does, the error occurs. It could be a C++11-issue, however, I tried compiling casacore both with and without C++11-support and got the same error.
Adam Ginsburg
@keflavich
hm
Tammo Jan Dijkema
@tammojan
Actually the output of CMake is a bit more descriptive, as it contains exactly the variables used in linking (so the list with PYTHON2_Boost_LIBRARIES, PYTHON2_LIBRARIES etc.
They don't seem to end up in CMakeCache.txt
However, I have the impression that it might be something else than just wrong versions of libraries linked together. That's usually the issue on Mac, however I'm quite sure I have everything right here, and still have the error. I'll check with a collegue tomorrow.
Adam Ginsburg
@keflavich
oh, I see.
ok, thank you
I'll try again once you can offer any input
and I'll track my cmake history next time I run it
Tammo Jan Dijkema
@tammojan
Thanks.
I'm off for today.
Gijs Molenaar
@gijzelaerr
hi! I think these channels are quite dead since the maintainers never log in anymore. If you have any questions or issues, please open an issue on the issue tracker!