PyBDSF

[EFOcran]

The latest version of the code and installations instructions are available on the PyBDSF GitHub page at https://github.com/lofar-astron/PyBDSF.

[Shadowphax]

Hi,

We have redeployed the container based on a number of improvements within the build definition file. There are currently two source finding containers. The most recent one is " sourcefinding.img" which is a symbolic link to the "sourcefinding-.img". Please test and update this issue.

Please no longer use the "source-finding.img" container.

[daikema]

So taking a peak at this, I don't see a pybdsf binary but there is a pybsdm one now (which I don't think was there before. @EFOcran does the pybdsf binary work for you?

[Shadowphax]

Have not received any feedback related to this issue. Please reopen if still broken.

[EFOcran]

pybdsf doesn't work but pybdsm works fine.

[Shadowphax]

Hi,

I have added pybdsf to the container. Can you test and confirm ?

Regards

Timothy

[1453983687829_image002.png] Timothy Carr - /\/¯¯¯¯¯\/\ Senior Technical Specialist Tel: +27 21 650 3014 Cell: +27 83 457 2568

---

From: EFOcran notifications@github.com Sent: 18 October 2017 11:26:30 AM To: idia-astro/idia-container-sourcefinding Cc: Timothy Carr; State change Subject: Re: [idia-astro/idia-container-sourcefinding] PyBDSF (#2)

pybdsf doesn't work but pybdsm works fine.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHubhttps://protect-za.mimecast.com/s/KbNeBqsJe8aRi9, or mute the threadhttps://protect-za.mimecast.com/s/eJpRBkho32dKsw.

Disclaimer - University of Cape Town This e-mail is subject to UCT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. If this e-mail is not related to the business of UCT, it is sent by the sender in an individual capacity. Please report security incidents or abuse via csirt@uct.ac.za