GNU Astronomy Utilities - Tasks: task #14131, Utility to match catalogs of...
You are not allowed to post comments on this tracker with your current authentication level.
task #14131: Utility to match catalogs of objects and find warpings
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Thu 25 Aug 2016 08:13:53 AM UTC | ||
Should Start On: | Wed 24 Aug 2016 03:00:00 PM UTC | Should be Finished on: | Wed 24 Aug 2016 03:00:00 PM UTC |
Category: | New program | Priority: | 5 - Normal |
Item Group: | None | Status: | Postponed |
Privacy: | Public | Percent Complete: | 50% |
Assigned to: | None | Open/Closed: | Open |
Effort: | 0.00 |
( Jump to the original submission )
Thu 19 Mar 2020 06:37:55 PM UTC, comment #8: |
Mohammad Akhlaghi <makhlaghi>![]() |
Thu 19 Mar 2020 12:52:32 PM UTC, comment #7: How should I prepare a draft proposal? I started to go through the code of astronomy.net but it is so vast to be evaluated within the given time.
|
Sachin Kumar Singh <sks_15>![]() |
Thu 19 Mar 2020 12:22:14 AM UTC, comment #6: That was a great review Sachin and a good question ;-).
|
Mohammad Akhlaghi <makhlaghi>![]() |
Wed 18 Mar 2020 09:53:55 PM UTC, comment #5: Sorry comment#25 task #13658 was meant to be here. |
Sachin Kumar Singh <sks_15>![]() |
Sun 15 Mar 2020 11:16:26 PM UTC, comment #4: Indeed, this is arguably one of the top things I had in mind when I wrote the GSoC general ideas! It is a critical step to add to Gnuastro for reaching the version 1.0 vision.
|
Mohammad Akhlaghi <makhlaghi>![]() |
Sun 15 Mar 2020 10:43:57 PM UTC, comment #3: I read the paper and also saw its Python implementation. This is a big feature to implement and I can add this to my proposal.
|
Sachin Kumar Singh <sks_15>![]() |
Tue 10 Mar 2020 02:31:27 PM UTC, comment #2: arXiv:1909.02946 provides an algorithm to find the necessary warp which may be interesting. |
Mohammad Akhlaghi <makhlaghi>![]() |
Sat 02 Dec 2017 07:49:45 PM UTC, comment #1: The new Match program, will now match two catalogs based on positions.
|
Mohammad Akhlaghi <makhlaghi>![]() |
Thu 25 Aug 2016 08:13:53 AM UTC, original submission:
Due to issues like the cosmic rays and also to increase the resolution and cover contiguous wide regions, astronomical images are often taken in short exposures. Each short exposure is usually "dithered" (slightly moved) compared to the previous exposure for better coverage and resolution.
|
Mohammad Akhlaghi <makhlaghi>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-12-02 | makhlaghi | Percent Complete | 10% | ![]() |
50% |
I just posted a general set of suggestions for the proposal on the main GSoC issue. Hopefully that should be good for some tips on how to organize your proposal.
In general, at this stage you don't need to go into the fine detail of the coding of astrometry.net, astroalign, or any other library/program you want to look into (details like "which particular files to be used and what features are to be implemented").
The same applies to the FITS and WCS standards.
The mere fact that you have read their papers/manuals, and have a general understanding of the problem and their code is enough to write an excellent proposal ;-).