Git Product home page Git Product logo

polaris's People

Contributors

abensberg avatar danielseifried avatar jammartin avatar lkeegan avatar martinalvarezsergio avatar mlietzow avatar polaris-mcrt avatar rbrunngraeber avatar robertbrauer1988 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

polaris's Issues

Too many killed photons

Hello, I recently switched from Polaris Version 4.0.4 to 4.0.6. I am using an OctTree grid which I created from FLASH input data (but also a self-written test cube with the same result). With 4.0.4 the TEMP and RAT calculations work fine, but with 4.0.6 I get permanently the message "ERROR: Wrong cell border!" using the standard ISRF source. In the end about 80% of all the photons are "killed". This reduces to about 50% when I decrease the starting radius from "2" to "1". In contrast, with Version 4.0.4 the number of killed photons was marginal.
The read-in of the OctTree seems to work fine, all the data (length, mass, density etc) it reports in the POLARIS output are correct.
Do you have any idea what to look for or to check, as this seems to be relatively deeply embedded in the code? If needed I could provide a small example. Thanks.

Polaris hangs at TEMP calculation

Hi all,
recently me and independently also Michael Küffmeier encountered a problem with the latest Polaris version when trying to calculate the dust temperature. It seems to hang at the line
return phIDs[0];
in the routine getPhaseFunctionID in Parameters.h .

Michael gets the error shown in the image below (which I think is identical):

To my understanding this comes from the fact that phIDs is not an array but a scalar. We both downloaded the clean version and just tried to ran a simple TEMP calculation

image
.

Position of stars in output

Dear developers,
would it be possible to include the position of stars/point sources used for the TEMP/RAT calculation in the screen output of POLARIS for later cross-checking? If I am not mistaken, so far it is only contained in the command file and if that file is changed at a later point, this information is lost.
Best,
Daniel Seifried

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.