Replies: 6 comments
-
Sounds like a good idea. If you want to do a direct translation it can be nice to convert Fortran to Julia then "juliarize" it with better Julia idioms. I used this script for MAESPA and a few other photosynthesis libraries, to at least get me started: https://gist.github.com/rafaqz/fede683a3e853f36c9b367471fde2f56 |
Beta Was this translation helpful? Give feedback.
-
Yes, that would be great. Happy to help any way I can (though I am extremely short of time like everyone!). |
Beta Was this translation helpful? Give feedback.
-
Wow, opendendro has a pretty big codebase, in all the languages (C++, Fortran, R, Python etc). This would be a big task (but then I guess most of these projects are). Ironically the stated goal of the opendendro organisation would seem to be more compatible with porting to julia than with what they are doing, building R wrappers around legacy fortran code:
Did the Opendendro people respond to your mail? |
Beta Was this translation helpful? Give feedback.
-
I did get an email from OpenDendro
So, there is the go ahead for it. The codebase is impressively large. I think a coarse first stage is to 1:1 convert fundamental library code. The Fortran to Julia script given by @rafaqz will be very helpful in that endeavor. Then we can juliarize it (likely in a fork because it will be a large refactoring game). From there, it would be incorporating other dendrotools that have been developed on top of dpl, either as extension packages or as base code. Still uncertain about how exactly that will play out, but baby steps. Honestly, as I interrogate my drive to help Julia grow in scientific computing, I am hatching a plan for some level of collaborative work that can fall under the NSF (Geosciences Open Science Ecosystem (GEO OSE))[https://new.nsf.gov/funding/opportunities/geo-ose-geosciences-open-science-ecosystem] grant. I have some colleagues that have received this grant and know other strong PI's for similar projects, so I'll get some feedback from them, then figure things out, so I'll likely follow up with something on that front. |
Beta Was this translation helpful? Give feedback.
-
That sounds very interesting. I have a few experiences with porting code from other languages to julia, and it can be surprisingly difficult to get the ideoms right. But @rafaqz has much more experience with these things than I do. Will be cool to follow what you do here. I'm guessing the geo channel on the slack should be a good place to find people who might have an interesting in the GEO approach you mention. |
Beta Was this translation helpful? Give feedback.
-
I finally got around to creating this and having the time to share it out. It's extremely WIP, so I won't register it or shift organizations or anything like that until it's in a stable functional spot. But, I think it's setup so that people can open pull requests, and they'll go through review. Let me know if there are any issues. |
Beta Was this translation helpful? Give feedback.
-
Currently, Julia does not have registered packages for dendrochronological methods such as Superposed Epoch Analysis, Cross-dating, chronologies from such datasets, etc. EcoJulia is probably the most appropriate organization to build such a package under. Additionally, I know researchers and analysts that constantly complain about the speed of their analyses but also don't have the time to dive into lower level languages. Julia seems like a prime candidate for these people. I want to know whether you all are interested in adding such a package?
Most of the people I know use R, MatLab, and Python, mostly using the dpl ecosystem. The source code for dpl uses FORTRAN. If we can implement the same functionality in native Julia, this can also provide paleoecologists a pipeline to being a contributor.
I've paired this with an email to opendendro to screen their interest.
Let me know what y'all think.
Beta Was this translation helpful? Give feedback.
All reactions