Comments (3)
Some cosmetic suggestions for tooltips:
-
Show fluxes rather than log-fluxes in the tooltip
-
(Input, Output) -> (S1, S2) # S being the usual symbol for flux
-
Phase_Centre_distance -> Distance off-axis. And show it in units of deg arcmin arcsec.
Also, the current plot title only reflects one of the input images (or models), which is a bit confusing. May I suggest adding the names to the axis labels instead, so that they say e.g. "log S1: model_or_image_name" and "log S2: model_or_image_name".
Then you just need to figure out an elegant way to display both model names in the position offset plot... maybe in the legend of the right plot, instead of "Model 1" and "Model 2"? Then the title of the left plot can be "Position offsets".
Finally, for filenames, may I suggest FluxOffsets.html
and PositionOffsets.html
? I find the use of "Input" and "Output" confusing, as they're not really inputs or outputs as such, just two models being compared.
from aimfast.
What does "R2" mean? https://en.wikipedia.org/wiki/Coefficient_of_determination?
It gives an overall sense of how well the source fluxes in one sky model fit the other, meaning that a value close to 1 implies a perfect correlation between the two sky models. This cannot be solely relied on but can be used in conjunction with the RMSE which provides the average deviation of the flux differences in units of source flux densities. (It is sensitive to outliers). And then the intercept and the gradient are used to further confirm that the fit follows the expected fit, which is c=0, g=1.
Can we also fit a slope through a 0 intercept (and show it on the same plot)?
Taking care of this.
I find "intercept" a bit difficult to interpret. As reported above, it's the log of a fitted flux offset, I think. Might be good to convert it back into mJy?
Agreed.
I assume the solid blue line is slope 1, intercept 0? In this case please draw it until (0,0), as that makes it clearer what it is. Also, suggest swapping linestyles. The fitted slope(s) are the important lines so should be a solid color, the slope=1 line should be less prominent (i.e. dashed), but maybe that's just me.
The solid blue line is the fit (as indicated in the legend)
Finally: in the plot above, it's clear the slope doesn't actually fit the (brighter) sources all that well, they all seem to lie above it consistently. I think it's that cluster of weak peripheral sources below the slope that's biasing the fit (and yay for the colour scheme, we wouldn't be able to diagnose the problem so easily without it!) We could think of clever schemes to downweigh peripheral sources, but for a start, could we add an option for a distance cutoff?
Taking care of this.
from aimfast.
I can pass in a mask as a detection image (actually @Athanaseus is this supported in aimfast?), and breizorro has enough features to chop islands out now.
With the help of breizorro
this can now be achieved.
breizorro -r mean9.fits --number-islands -o mask9.fits
breizorro -m mask9.fits --extract-islands 262 --make-binary --invert -o mask9-centerhole.fits
aimfast --compare-images image1.fits image2.fits --mask-image mask9-centerhole.fits -c my-source-finder.yml
from aimfast.
Related Issues (19)
- use a label instead of a path when creating stats dictionary
- Dynamic range calculated deepest negative around brightest source not reliable
- Add test suite
- Py3 compatible
- Make modules importable in Jupyter-notebook for plotting
- Have single HTML file with all plots if multiple models are compared
- Support csv and tab formatted catalogs
- if more than on esources are detected with getNearSource use closest or weighted mean HOT 1
- Round off values in tables HOT 2
- NVSS query and cross-matching script HOT 4
- --compare-model output HTML is broken with Firefox HOT 5
- add log-log axis option to --compare-model mode
- --compare-model should filter for compact single-component sources, at least as an option HOT 2
- Aimfast for MOSS HOT 17
- Reading -psf as a directory and not a size HOT 2
- No Output plots created from --compare-models HOT 7
- MeerKAT vs NVSS HOT 1
- aimfast applied to self-calibrated images HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aimfast.