Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

https://codeberg.org/gnuastro/papers
20 June 2024, 17:02:53 UTC
  • Code
  • Branches (9)
  • Releases (0)
  • Visits
NameTargetMessageDate
HEAD 8161194 Configuration: portability fixes in Less and WCSLIB SUMMARY: no change is necessary in your project, unless you use the Fortran features of WCSLIB in your project. Until now, there were two compilation failures on recent macOS computers with an M1 CPU: Less would crash because it couldn't find the relevant PCRE (perl-compatible regular expression) libraries and WCSLIB would crash because the LLVM compiler's Fortran features could not be built. With this commit, both issues have been fixed by disabling the relevant feature. Extensive comments have been placed in both places in case your project needs these features, so please see the comments in the relevant part of 'reproduce/software/make/basic.mk' for Less and 'reproduce/software/make/high-level.mk' for WCSLIB. In fact the previous solution (where we would not have Fortran features in WCSLIB on macOS systems was problematic and non-reproducibile (the features of WCSLIB depended on the operating system!). Another minor change was that for macOS, we now directly use the version-string of WCSLIB to fix the internal linking issue there. As a result, WCSLIB is no longer a "Version-dependent build" software (in 'reproduce/software/config/versions.conf'). Recall that these are software that when changing the version, it is also necessary to inspect their build recipe. These two issues and their fix were discovered and fixed with the help of James Robinson.22 May 2023, 22:44:20 UTC
refs/heads/aas-journals 27d758a references.tex: no @ in email of copyright statement Until now, the @-sign with the email of 'tex/src/references.tex' would conflict with BibTeX (that is necessary with AAS journals) and cause a crash in the build. With this commit, to fix the problem the '@' sign has been replaced by '::at::'.25 February 2024, 16:49:07 UTC
refs/heads/color-faint-gray c5f4830 Including the publication info into the README.md file Until this commit, the publication information was missing in the 'README.md' file. With this commit, since the RNAAS article has been finally published, all information is available and it has been added to the 'README.md' file.10 January 2024, 18:14:30 UTC
refs/heads/maneage 8161194 Configuration: portability fixes in Less and WCSLIB SUMMARY: no change is necessary in your project, unless you use the Fortran features of WCSLIB in your project. Until now, there were two compilation failures on recent macOS computers with an M1 CPU: Less would crash because it couldn't find the relevant PCRE (perl-compatible regular expression) libraries and WCSLIB would crash because the LLVM compiler's Fortran features could not be built. With this commit, both issues have been fixed by disabling the relevant feature. Extensive comments have been placed in both places in case your project needs these features, so please see the comments in the relevant part of 'reproduce/software/make/basic.mk' for Less and 'reproduce/software/make/high-level.mk' for WCSLIB. In fact the previous solution (where we would not have Fortran features in WCSLIB on macOS systems was problematic and non-reproducibile (the features of WCSLIB depended on the operating system!). Another minor change was that for macOS, we now directly use the version-string of WCSLIB to fix the internal linking issue there. As a result, WCSLIB is no longer a "Version-dependent build" software (in 'reproduce/software/config/versions.conf'). Recall that these are software that when changing the version, it is also necessary to inspect their build recipe. These two issues and their fix were discovered and fixed with the help of James Robinson.22 May 2023, 22:44:20 UTC
refs/heads/maskfilled 4f3b5b1 First draft of figure Until now, the figure wasn't complete (not showing the intermediate step between two clips). With this commit, a first draft of a complete figure has been added.29 March 2024, 19:06:59 UTC
refs/heads/pointing-simulate be18976 Minor typo corrected in paper.tex and extra Gnuastro citation removed Until now, a "very" was mistakenly written as "ver", and an extra Gnuastro citation 'akhlaghi19', caused an '?' within the text. With this commit, both these problems have been solved.24 October 2023, 11:54:13 UTC
refs/heads/polar-plot 375e12e The url of the Zenodo has been fixed Until now, the Zenodo uro was not the DOI. With this commit, it has been changed.20 June 2024, 16:58:33 UTC
refs/heads/polarplot 7877ebd Second commets of Mohammad is implemented on paper text Until now, just frist comments of Moahammad was implemented. With this commit, his comments is implemented in paper.31 May 2024, 13:02:57 UTC
refs/heads/radial-profile 872f2a6 Including the publication info into the README.md file Until this commit, the publication information was missing in the 'README.md' file. With this commit, since the RNAAS article has been finally published, all information is available and it has been added to the 'README.md' file.18 January 2024, 09:02:28 UTC
refs/heads/zeropoint c89275e Gnuastro's references goes into the software and empty LaTeX output filled Until now, the Gnuatro references was in the references of the project, while it should be tin software references. Also, fianl tex file of Make files that are obtainging the zero point based on the image and catalog reference were empty and arXiv removed them because they were empty. With this commit, the Gnuastro refered on software references and both of tex files are filled with an comment to allow upload in arXiv.07 December 2023, 12:12:32 UTC

back to top

Software Heritage — Copyright (C) 2015–2026, The Software Heritage developers. License: GNU AGPLv3+.
The source code of Software Heritage itself is available on our development forge.
The source code files archived by Software Heritage are available under their own copyright and licenses.
Terms of use: Archive access, API— Content policy— Contact— JavaScript license information— Web API