by jsendak | Aug 12, 2024 | AI
arXiv:2408.04745v1 Announce Type: new
Abstract: Mitigating methane emissions is the fastest way to stop global warming in the short-term and buy humanity time to decarbonise. Despite the demonstrated ability of remote sensing instruments to detect methane plumes, no system has been available to routinely monitor and act on these events. We present MARS-S2L, an automated AI-driven methane emitter monitoring system for Sentinel-2 and Landsat satellite imagery deployed operationally at the United Nations Environment Programme’s International Methane Emissions Observatory. We compile a global dataset of thousands of super-emission events for training and evaluation, demonstrating that MARS-S2L can skillfully monitor emissions in a diverse range of regions globally, providing a 216% improvement in mean average precision over a current state-of-the-art detection method. Running this system operationally for six months has yielded 457 near-real-time detections in 22 different countries of which 62 have already been used to provide formal notifications to governments and stakeholders.
Mitigating Methane Emissions: The Key to Fighting Global Warming
Methane is a potent greenhouse gas that plays a significant role in climate change. While carbon dioxide is the most well-known greenhouse gas, methane is approximately 28 times more effective at trapping heat in the atmosphere over a 100-year period. Therefore, reducing methane emissions is crucial for mitigating global warming in the short-term and buying humanity time to transition to a decarbonized future.
In a groundbreaking development, a team of researchers has introduced MARS-S2L, an automated AI-driven methane emitter monitoring system. This system, designed for Sentinel-2 and Landsat satellite imagery, is being implemented at the United Nations Environment Programme’s International Methane Emissions Observatory. By leveraging the power of artificial intelligence and remote sensing instruments, MARS-S2L aims to routinely monitor and take action on methane plumes worldwide.
The success of this technological advancement lies in the compilation of a global dataset containing thousands of super-emission events, which has been used for training and evaluation. The researchers demonstrate that MARS-S2L is capable of effectively monitoring methane emissions in diverse regions globally. In fact, the system provides a remarkable 216% improvement in mean average precision compared to the current state-of-the-art detection method.
Over the course of six months of operational deployment, the MARS-S2L system has already made 457 near-real-time detections in 22 different countries. These detections have been instrumental in providing formal notifications to governments and stakeholders, highlighting the urgency for action. This represents a significant step towards greater global awareness and accountability in addressing methane emissions and their impact on climate change.
Multi-disciplinary Nature of the Solution
The development and implementation of the MARS-S2L system involves a multi-disciplinary approach, combining expertise from various fields:
- Environmental Science: Understanding the impact of methane emissions on climate change and the urgency for mitigation.
- Data Science and Artificial Intelligence: Designing and training AI models using a global dataset to detect methane plumes in satellite imagery.
- Remote Sensing: Utilizing satellite imagery and remote sensing instruments to identify and monitor methane emissions.
- Policy and International Cooperation: Collaborating with the United Nations Environment Programme’s International Methane Emissions Observatory to provide formal notifications and encourage global action.
The multi-disciplinary nature of this solution highlights the importance of interdisciplinary collaboration in addressing complex global challenges. By leveraging the expertise and insights from these different fields, the MARS-S2L system has made significant strides in monitoring and mitigating methane emissions, contributing to the broader efforts in combating climate change.
Expert Insight: Methane emissions are a critical piece of the climate change puzzle that often receives less attention compared to carbon dioxide. The introduction of an automated AI-driven monitoring system, such as MARS-S2L, is a game-changer in our ability to detect and track methane plumes globally. By providing near-real-time detections and formal notifications, this technology can facilitate prompt action and accountability from governments and stakeholders. It also highlights the power of interdisciplinary collaboration in finding innovative solutions to urgent environmental challenges.
Source: Mitigating methane emissions: The fastest way to stop global warming in the short-term and buy humanity time to decarbonise. (2024). arXiv preprint arXiv:2408.04745v1.
Read the original article
by jsendak | Jul 19, 2024 | DS Articles
Dear rOpenSci friends, it’s time for our monthly news roundup!
You can read this post on our blog.
Now let’s dive into the activity at and around rOpenSci!
rOpenSci HQ
Announcing New Software Peer Review Editors: Beatriz Milz and Margaret Siple
We are excited to welcome Beatriz Milz and Margaret Siple to our team of Associate Editors for rOpenSci Software Peer Review. They join Laura DeCicco, Julia Gustavsen, Anna Krystalli, Mauro Lepore, Noam Ross, Maëlle Salmon, Emily Riederer, Adam Sparks, and Jeff Hollister.
Meet Beatriz and Margaret in their introduction blog post.
Welcome on board to you both, thank you for your service!
A fresh new look for R-universe!
You might have noticed that R-universe got a big refresh. 
Read all about this big overhaul of the interface.
Resources from the rOpenSci community at useR! 2024
While some video recordings have not yet been posted on the useR! YouTube channel, some slidedecks and materials are already available.
Coworking
Read all about coworking!
Join us for social coworking & office hours monthly on first Tuesdays!
Hosted by Steffi LaZerte and various community hosts.
Everyone welcome.
No RSVP needed.
Consult our Events page to find your local time and how to join.
And remember, you can always cowork independently on work related to R, work on packages that tend to be neglected, or work on what ever you need to get done!
Software 
New packages
The following package recently became a part of our software suite:
Discover more packages, read more about Software Peer Review.
New versions
The following nine packages have had an update since the last newsletter: rotemplate (pkgdown-2.0.9
), gitignore (v0.1.7
), nodbi (v0.10.5
), nuts (v1.1.0
), occCite (v0.5.7
), osmapiR (v0.1.0
), phonfieldwork (v0.0.16
), taxlist (v0.3.0
), and waywiser (v0.6.0
).
Software Peer Review
There are eleven recently closed and active submissions and 6 submissions on hold. Issues are at different stages:
Find out more about Software Peer Review and how to get involved.
On the blog
Software Review
Other topics
Use cases
Three use cases of our packages and resources have been reported recently.
Explore other use cases and report your own!
Calls for contributions
Calls for maintainers
If you’re interested in maintaining any of the R packages below, you might enjoy reading our blog post What Does It Mean to Maintain a Package?.
Calls for contributions
Also refer to our help wanted page – before opening a PR, we recommend asking in the issue whether help is still needed.
Package development corner
Some useful tips for R package developers. 
Last call: your opinion on the CRAN submission process!
Shared by Lluís Revilla and Heather Turner in our Slack workspace, a crucial survey ending today!
“If you have R package development experience and would like to share your thoughts on the CRAN submission process, please fill this short survey from the CRAN Cookbook project!”
Please find the Google form and read more about the exciting cookbook project in this post by Jasmine Daly.
Robust type-checking with r-lib
Don’t miss this insightful short post by Josiah Parry, “Type safe(r) R code”.
A related older blog post is “Checking the inputs of your R functions” by Hugo Gruson, Sam Abbott, Carl Pearson.
The one with all the useR! links
The useR! 2024 conference featured quite a few talks relevant to package development, beside the talks we mentioned in the HQ section.
Not all recordings are available yet, but make sure to check out the useR! YouTube channel.
If we missed any relevant content, please get in touch so we might add missing pieces to our next newsletter!
Retrospectives
Kurt Hornik and Torsten Hothorn gave keynote talks “More than 25 years of CRAN” (Slides) and “Some things you can’t read from
a NEWS file” (Slides | Recording) about maintaining a package for decades.
Edzer Pebesma and Roger Bivand reported on “The Retirement of R Packages with Many Reverse Dependencies” (Slides).
On validation of R packages
Coline Zeballos and Yann Féhat from the R Validation Hub discussed how to support (pharma) companies with validation of R Packages (Slides). They use a toolset based on r-hub/repos and the riskmetric package.
Szymon Maksymiuk and Lorenzo Braschi presented a Deep Dive Into Industry R
Package Quality Assessment. Beside introducing the concepts, they mentioned three open-source R packages that they created: checked for running reverse dependencies checks; covtracer for contextualizing tests using covr test traces; rd2markdown for converting .Rd files into Markdown.
Also on reverse dependencies checks, Pawel Rucki and André Veríssimo presented
{verdepcheck} – A Tool for Dependencies Check (Slides | Package Docs).
Franciszek Walkowiak discussed Systems Integration Tests for R Package Cohorts, including the introductions to two open-source utilities, scribe that creates complete build, check and install reports for a collection of R projects and locksmith that helps with renv.lock
creation (Slides).
On good practice
Daniel Sabanés Bové introduced openstatsware’s work on minimal viable good practice standards for R packages.
Pedro Silva listed Seven Deadly Sins Holding You
Back as a Software Developer (Slides).
Hugo Gruson had a poster on A reproducible analysis of CRAN Task Views to understand the state of an R package ecosystem. See the live analysis.
On learning with silly projects
Fonti Kar shared her experience in creating {ohwhaley} – a ‘toy’ R package which serves as a tool for learning package development and upskilling new learners (Slides).
On package design
Hugo Gruson highlighted the benefits of using S3 classes for interoperability in Existing Software Ecosystems (Slides).
See also his recent blog posts on the topic.
Ligia Adamska used an onion analogy to explain Layered Design for R Package
Development: Meeting the Needs of
Pharmaceutical R&D Stakeholders (Slides).
On tools
Daphne Grasselly, Franciszek Walkowiak and Pawel Rucki lead a tutorial on Streamlining R package
development with GitHub Actions
Workflows (Slides).
Emil Hvitfeldt explained how to make better error messages with rlang and cli.
Ella Kaye shared her insights on C for R users (Slides).
Davis Vaughan introduced tree-sitter, an efficient incremental parsing library and the R package treesitter, which provides bindings to tree-sitter whose README states “tree-sitter is useful for a number of things, including syntax highlighting, go-to definition, code reshaping, and more.”
On multilingualism
Elio Campitelli spoke about Building Bilingual Bridges
with Multilingual Manuals (Slides). See also their post on our blog!
On debugging
Shannon Pileggi delivered a tutorial on debugging in R (Materials).
Antoine Fabri gave an overview of the motivations behind, and features of, his constructive package, which, among other things, can be useful for troubleshooting (Package docs).
On wrapping APIs
Hadley Wickham introduced and demo-ed his httr2 package (Package docs).
Simon Haller explained the Automated Generation
of R Client Packages for RESTful APIs (Slides). See also Jon Harmon’s work on the same topic.
On a last resort for archived CRAN packages
Henrik Bengtsson and Lluís Revilla had a poster about their CRANhaven project, a backup solution for end-users when a package falls of CRAN (and which is built using R-universe!).
Last words
Thanks for reading! If you want to get involved with rOpenSci, check out our Contributing Guide that can help direct you to the right place, whether you want to make code contributions, non-code contributions, or contribute in other ways like sharing use cases.
You can also support our work through donations.
If you haven’t subscribed to our newsletter yet, you can do so via a form. Until it’s time for our next newsletter, you can keep in touch with us via our website and Mastodon account.
Continue reading: rOpenSci News Digest, July 2024
Analysis of rOpenSci’s Monthly Updates
The updates from rOpenSci in July 2024 encompass a range of topics, from new software peer review editors and updates to software packages to coworking events and the application of rOpenSci’s packages. The implications of these updates are numerous and extend to a broad field, primarily benefiting R developers and users.
New Software Peer Review Editors
The announcement of Beatriz Milz and Margaret Siple as new Associate Editors for rOpenSci Software Peer Review projects a future where there is an expanded expertise to ensure the robustness of open-source software for scientific research. As these two further contribute their perspectives and skills to the team, we can anticipate more diversified and quality software tools for the open science community.
Advice
For potential software contributors to rOpenSci, ensure your submissions are well-documented and robust. This aids the review process and contributes to the overall quality of the rOpenSci ecosystem.
R-universe Upgrade
The refresh of the R-universe interface suggests an ongoing commitment to improving user experience. Future developments may include additional interface features to facilitate navigation and access to a wealth of R packages.
Advice
Users should take time to familiarize themselves with the new layout and features. For contributors, consider how to optimize package listing and description for improved visibility and user understanding in the new interface.
Community Participation and Events
rOpenSci’s commitment to community engagement is highlighted by the number of events organized and the diversity of topics covered. These include coworking sessions, tutorials, and talks at the useR! 2024 conference. Future developments may entail more sessions geared towards addressing community needs and knowledge gaps.
Advice
Keep an eye on upcoming events and participate actively. Offering feedback and suggestions for new topics could also form part of the community contribution.
Software Updates
The announcement of new packages and updated versions illustrates a continuously evolving software repository. With the inclusion of the osmapiR package, developers and users now have a handy tool for interfacing with the OpenStreetMap API. Expect ongoing evolution of this ecosystem as developers address user needs.
Advice
Stay updated on the latest package updates and consider integrating new and updated packages into your scientific research routines if they fit into your data analysis strategy.
On the Blog
Topics ranging from software reviews, multilingual documentation, community collaborations to the use of social network analysis for managing the digital community are discussed. These resources potentially contribute to improving the understanding and utilization of rOpenSci’s tools.
Advice
Read and engage with rOpenSci’s blog posts to stay informed regarding the latest trends and best practices in the use of R for scientific research.
Concluding Remarks
The long-term implications of these updates from rOpenSci are an increasingly robust and diverse set of open-source tools for scientific research. For potential software contributors, this means a welcoming and supportive infrastructure for producing and refining quality research tools. For users, expect an expanding repertoire of tools tailored to your research needs, paired with the presence of a dynamic and supportive community.
Staying active within the community, whether by contributing code, participating in events, or engaging with blog content, is the best way to maximize the benefits from this evolving ecosystem.
Read the original article
by jsendak | Jun 22, 2024 | DS Articles
Dear rOpenSci friends, it’s time for our monthly news roundup!
You can read this post on our blog.
Now let’s dive into the activity at and around rOpenSci!
rOpenSci HQ
rOpenSci takes over maintenance of the {goodpractice} package
The {goodpractice} package was started by Gábor Csárdi in 2016 to auto-magically provide advice on good practices for your own R package.
rOpenSci’s Dev Guide has recommended using it from the first day we started writing it in 2018.
The package is now a central part of our own internal {pkgcheck} system, which is run automatically on all new submissions, and we recommend that all authors use our ‘pkgcheck-action’ GitHub action, which also runs {goodpractice}.
We are pleased to announce that rOpenSci has now taken over maintenance of the {goodpractice} package, thanks to the approval both of the original author Gábor, and the previous maintainers at ascent.io.
The package has now been moved to our ropensci-review-tools GitHub organization, which holds all software used in our automated checking system.
This also means that documentation for the package is now built by our own documentation system, and will live from here on at docs.ropensci.org/goodpractice/.
rOpenSci at CZI Open Science 2024
From June 10 to June 14 Noam Ross, Mauro Lepore and Yanina Bellini Saibene participated on the CZI Open Science 2024 event.
On Wednesday, we showcased the Champions Program, sharing Champions’ projects, training materials, and the results of the two-year pilot. We had the chance to chat and learn about many other projects during these sessions.
Yanina participated in the closing panel on Case Study Session 3: Demonstrating Impact of Open Science to explore the challenges of using traditional academic metrics to measure project impact and emphasize alternative approaches. In her talk, Yani introduced the work done by different rOpenSci members, the tools and metrics we use to capture their stories, and the impact we achieve together.
The rOpenSci community at upcoming events
Meet rOpenSci team and community members at events in the near future!
-
Two talks by rOpenSci team members, and more contributions by rOpenSci community members, to look forward to at useR! 2024 in Salzburg, Austria.
- Maëlle Salmon’s keynote talk “How your code might get rusty” on Wednesday, July 10 at 09:20 CEST;
- Jeroen Ooms’ talk “Navigating the R Ecosystem Using R-Universe” on Thursday, July 11, 11:30 – 11:50 CEST.
- Jon Harmon’s virtual talk “Learning Together at the Data Science Learning Community” will go live on the useR!2024 YouTube playlist at 10:30am CDT on July 2;
- Paola Corrales’ and Elio Campitelli’s tutorial “Efficient Data Analysis with data.table” on Monday, July 3 (pre-registration required);
- Elio Campitelli’s talk “Building Bilingual Bridges with Multilingual Manuals” on Tuesday, July 4 at 11:40 CEST.
- Hugo Gruson’s talk ”
Building Interoperability in Existing Software Ecosystems with S3 Classes” on Tuesday, July 9 at 14:50, and his poster “A reproducible analysis of CRAN Task Views to understand the state of an R package ecosystem”
- Lluís Revilla’s and Henrik Bengtsson’s poster about CRAN packages archived and a the cranhaven.org R-universe created to reduce the impact of that on users.
- Will Landau’s and Charlie Gao’s talk “Moju-Kapu: How {Mirai} and {Crew} Are Powering the Next Generation of Parallel Computing in R” on Tuesday, July 9 at 11:00 CEST.
- Binod Jung Bogati’s talks “Generate Raw Synthetic Dataset for Clinical Trial – Binod Jung Bogati, Numeric Mind” on Tuesday, July 9 at 13:30 CEST; and “Translate R for Global Reach” on Thursday, July 11 at 12:10 CEST.
-
At posit::conf(2024) in Seattle, US, you’ll get to meet some champions and mentors!
- Look for: Andrea Gomez Vargas; Yi-Chin Sunny Tseng; Luis D. Verde Arregoitia; Francisco Cardozo; Jonathan Keane.
- Don’t miss Luis’ lightning talk “Why’d you load that package for?” on Tuesday, Aug 13 at 1:00 PM PDT
-
We’re excited to share that rOpenSci community manager Yanina Bellini Saibene will deliver a keynote talk at BioNT Community Event & CarpentryConnect-Heidelberg 2024, on November 14th in Heidelberg, Germany.
Coworking
Read all about coworking!
Join us for social coworking & office hours monthly on first Tuesdays!
Hosted by Steffi LaZerte and various community hosts.
Everyone welcome.
No RSVP needed.
Consult our Events page to find your local time and how to join.
And remember, you can always cowork independently on work related to R, work on packages that tend to be neglected, or work on what ever you need to get done!
Software 
New packages
The following three packages recently became a part of our software suite:
-
goodpractice, developed by Mark Padgham together with Karina Marks, Daniel de Bortoli, Gabor Csardi, Hannah Frick, Owen Jones, and Hannah Alexander: Give advice about good practices when building R packages. Advice includes functions and syntax to avoid, package structure, code complexity, code formatting, etc. It is available on CRAN.
-
mregions2, developed by Salvador Fernandez-Bejarano together with Lotte Pohl: Explore and retrieve marine geo-spatial data from the Marine Regions Gazetteer and the Marine Regions Data Products, including the Maritime Boundaries. It has been reviewed.
-
rOPTRAM, developed by Micha Silver: The OPtical TRapezoid Model (OPTRAM) derives soil moisture based on the linear relation between a vegetation index and Land Surface Temperature (LST). The Short Wave Infra-red (SWIR) band is used as a proxy for LST. See: Sadeghi, M. et al., 2017. https://doi.org/10.1016/j.rse.2017.05.041 .
Discover more packages, read more about Software Peer Review.
New versions
The following nine packages have had an update since the last newsletter: goodpractice (v1.0.5
), beastier (v2.5.1
), c14bazAAR (5.0.0
), comtradr (v1.0.1
), DataPackageR (v0.16.0
), dynamite (1.5.2
), readODS (v2.3.0
), rgbif (v3.8.0
), and targets (1.7.1
).
Software Peer Review
There are fourteen recently closed and active submissions and 6 submissions on hold. Issues are at different stages:
Find out more about Software Peer Review and how to get involved.
On the blog
Software Review
Tech Notes
- A fresh new look for R-universe! by Jeroen Ooms. We have given the WebUI for R-universe a big refresh. This is the biggest UX overhaul in since the beginning of the project.
Calls for contributions
Calls for maintainers
If you’re interested in maintaining any of the R packages below, you might enjoy reading our blog post What Does It Mean to Maintain a Package?.
Calls for contributions
Also refer to our help wanted page – before opening a PR, we recommend asking in the issue whether help is still needed.
Package development corner
Some useful tips for R package developers. 
Make your functions compa-tibble
Do the functions of your package use data.frame
as input?
Do not miss Hugo Gruson’s post Make your functions compa-tibble as users of your package might well try and pass a tibble
, which you probably don’t want to be a showstopper!
Use lintr to enforce your package’s function preferences
Do you want to commit to using the cli package instead of base R messaging?
You can configure the lintr settings for your codebase to pick up usage of certain functions, to inform you along with the preferred replacement.
See, as an example, pkgdown’s lintr configuration file and the corresponding GitHub Actions workflow (from r-lib/actions).
This neat safeguard makes use of the Undesirable function linter.
More metadata on CRAN
CRAN pages of packages now show…
A pure GitHub preview workflow for pkgdown websites
If you use a gh-pages branch on GitHub to store the source of your pkgdown website, and use GitHub Pages to deploy it, you could extend that workflow to create (and then clean) subdirectories in that branch to host previews of pull requests.
Check out this GitHub Actions workflow file by Garrick Aden-Buie.
Tips for refactoring test files
Do you put the object as close as possible to the related expectation(s)?
Read about this, and other, tips for refactoring test files.
One more tool for checking inputs of your R functions
Do you check inputs of your R functions?
Beside the aforelinked R-hub blog post by Hugo Gruson, Sam Abbott, Carl Pearson, you might be interested in the experimental stbl package by Jon Harmon.
Last words
Thanks for reading! If you want to get involved with rOpenSci, check out our Contributing Guide that can help direct you to the right place, whether you want to make code contributions, non-code contributions, or contribute in other ways like sharing use cases.
You can also support our work through donations.
If you haven’t subscribed to our newsletter yet, you can do so via a form. Until it’s time for our next newsletter, you can keep in touch with us via our website and Mastodon account.
Continue reading: rOpenSci News Digest, June 2024
Understanding the Role and Continued Expansion of the rOpenSci Project
rOpenSci, an initiative for open source tools serving the scientific community continues to gain momentum, expand and contribute to broad-reaching projects and events in the field of open science. By analyzing recent developments and future endeavors, we can anticipate the long-term implications of its growth and formulate advice for those wishing to contribute or utilise its resources.
Open Source Package Maintenance
Key to rOpenSci’s contribution to the open source community is the stewardship of packages, the most recent being the {goodpractice} package. This package offers advice on the best practices for building R packages. Its maintenance by rOpenSci, following approval from the original author and previous maintainers, solidifies the package’s place in rOpenSci’s internal {pkgcheck} system, used to automatically run checks on new submissions.
The implications of assuming this responsibility extend beyond the improvement of the package itself. When an influential organisation like rOpenSci maintains important packages, it can set a standard of quality and ensure continual updates and improvements. This, in turn, assures users of the package’s reliability and longevity, which encourages usage and contribution from the community.
Actionable Advice:
- For existing users of the {goodpractice} package, continue your usage and consider contributing to its development where possible.
- If you’re not yet using the package, consider integrating it into your workflow for more efficient package building.
rOpenSci’s Impact on Major Events
rOpenSci made a significant impact at the recent CZI Open Science 2024 event where several panel discussions and sessions were organized. The Champions Program, which showcases project results and training materials from open science proponents, was centre stage. Impact measurement techniques in open science, particularly alternatives to traditional academic metrics, were also a point of discussion.
Through participation in such major events, rOpenSci not only highlights its own initiatives but also contributes to a wider discourse on open science. Discussing impact measurement, for example, helps to shape future assessment frameworks and validates the work being done outside of academia. Sharing learning materials and project highlights raises awareness and shares knowledge, both of which foster the growth of the open science community.
Actionable Advice:
- Stay informed about the major events that rOpenSci is participating in to follow important discussions and developments.
- Learn from the resources and information shared at these events.
- Consider how you can contribute to the discourse or use the knowledge shared to improve your own open science practices.
Upcoming rOpenSci Involvement
The global footprint of rOpenSci is set to expand with its members participating in numerous upcoming events, hosting technical discussions, informative talks, and tutorials. These include contributions to useR! 2024, posit::conf(2024), and CarpentryConnect-Heidelberg 2024, among others.
Participation in diverse, global events demonstrates the growing influence and relevance of rOpenSci within the open science community. Such contributions not only extend the group’s impact but also provide opportunities for members of the community to learn and collaborate.
Actionable Advice:
- Keep an eye on the schedule of upcoming events involving rOpenSci and decide which to attend based on your areas of interest.
- Take the opportunity to meet team members, share your thoughts, and collaborate on projects of mutual interest that can help to further expand the open science community.
Incorporating Peer Review and Call for Contributions
rOpenSci’s power is in its community, as demonstrated by the continuous calls for peer review and the maintenance and improvement of diverse packages.
Inviting community contribution reinforces the collaborative philosophy of open source, encouraging sharing and improving the quality, reliability, and functionality of tools.
Actionable Advice:
- Even if not a professional developer, consider reviewing and contributing to the packages that interest you. This not only improves the tool but also develops your own professional skills.
- The call for contributions should not only be seen as a responsibility but also an excellent opportunity for learning and professional growth.
Promoting Good Practice
rOpenSci also offers resources and advice for package developers to help them improve their work’s efficiency and quality; for instance, it is recommended to make functions compatible with both data.frame and tibble.
Such advice helps to standardize open source contribution and make it easier for users to gain the maximum benefit from the resources available.
Actionable Advice:
- If you’re a package developer, ensure your functions are compatible with tibble and data.frame formats.
- Be proactive in seeking out and applying advice from the community, especially if it enhances the usability of your package.
rOpenSci is a community dedicated to open tools for open science, and their work significantly impacts the open science and open source landscape. By staying connected with rOpenSci’s activities, aspiring developers and science enthusiasts can contribute to and benefit from the community. Whether by extending the reach of relevant tools, participating in events, or involving themselves in peer review, prospective contributors are encouraged to be part of the growth and promotion of open science.
Read the original article
by jsendak | Jun 16, 2024 | Science

Fire predictions pushed to locals’ smartphones could save forests, and lives, say researchers
Ensuring the safety of forests and the lives of people living in fire-prone areas has become increasingly important in recent years. Climate change and human encroachment into natural habitats have raised the risk of wildfires, making it crucial to develop effective strategies for preventing and managing these disasters. Researchers have now proposed a novel approach that utilizes smartphones to push fire predictions to locals, potentially revolutionizing the way we combat forest fires and ultimately saving lives.
The Power of Predictive Technology
Predicting where and when a fire will occur is a complex task, requiring a combination of meteorological data, satellite imagery, and on-the-ground observations. Traditional methods of disseminating fire predictions typically involve official channels such as websites or emergency services, but these often fail to reach the people who need them most in a timely manner.
The proposed solution is to leverage the prevalence of smartphones in today’s society, turning them into powerful tools for instant fire prediction dissemination. By developing user-friendly apps that can access relevant data from meteorological agencies, satellites, and fire monitoring stations, individuals living in fire-prone areas can receive real-time updates and alerts regarding potential fire risks.
Potential Future Trends
If implemented successfully, this smartphone-based fire prediction system could have several significant future trends:
- Improved Fire Preparedness: By providing instant fire predictions directly to locals, individuals can proactively take steps to safeguard themselves and their properties. This can include actions such as clearing dry vegetation, preparing evacuation plans, or ensuring fire extinguishing equipment is readily available. Overall, this can contribute to the collective effort of fire prevention and preparedness.
- Enhanced Early Warning Systems: Traditional early warning systems can be limited in their coverage and accessibility. Smartphone apps that deliver fire predictions can bridge this gap, reaching a wider audience in a shorter period. This could be particularly advantageous for remote or rural areas where official warnings might take longer to reach or may not be prioritized.
- Data-Driven Fire Management: Gathering data from smartphone apps can provide invaluable insights into fire patterns, behavior, and geographical hotspots. By consolidating this crowd-sourced information, fire management agencies can make more informed decisions about resource allocation, organizing firefighting efforts, and implementing preventative measures.
- Collaborative Citizen Science: Engaging the public through smartphone apps can foster a sense of community involvement in fire prevention. Local residents can contribute their observations, photos, and information about potential fire risks, creating a network of citizen scientists. This collective data can significantly supplement official data sources and improve overall fire prediction accuracy.
- Smartphone Technology Advancements: As smartphones continue to advance with better sensors, increased computational power, and improved connectivity, the capabilities for fire prediction apps will also expand. Future enhancements may include the integration of Artificial Intelligence (AI) algorithms for more accurate predictions, augmented reality features for real-time fire visualization, or even the utilization of drones for on-the-ground situational awareness.
Conclusion and Recommendations
The potential of smartphone-based fire predictions is immense, offering a new frontier in combatting wildfires and protecting lives. For this technology to reach its full potential, cooperation between researchers, governments, and technology companies is crucial. Further development of user-friendly apps, integration of multiple data sources, and continuous improvement of prediction algorithms are essential steps to enhance the effectiveness and reliability of this system.
Additionally, public awareness campaigns and incentives should be implemented to encourage widespread adoption of fire prediction apps and ensure maximum participation from local communities. Governments should allocate resources for necessary infrastructure, such as reliable mobile networks in remote areas, to ensure equitable access to this technology.
In conclusion, the future of fire prediction lies in the palm of our hands. By harnessing the power of smartphones and leveraging real-time data, we can create a more proactive and community-driven approach to fire prevention, ultimately saving forests and lives.
Reference: Nature, Published online: 14 June 2024; doi:10.1038/d41586-024-01758-2
by jsendak | May 24, 2024 | DS Articles
Dear rOpenSci friends, it’s time for our monthly news roundup!
You can read this post on our blog.
Now let’s dive into the activity at and around rOpenSci!
rOpenSci HQ
rOpenSci in the Research Organization Registry
rOpenSci was added to the Research Organization Registry (ROR) in its latest release. The ROR is a global, community-led registry of open persistent identifiers for research organizations. ROR IDs help link and disambiguate metadata about organizations in the scholarly record, much like DOIs and ORCiDs do for manuscripts and researchers. Linked metadata is rOpenSci’s love language
! Find us at https://ror.org/019jywm96.
What are the rOpenSci Champions up to now?
Our Champions and mentors have been carrying out various programmed activities.
The first stage of the program has a very important training component. This year, we divided the training into technical and community tracks, with several one to two-hour sessions each. Here, you can find the openly available material for each session.
The Technical Track is focused on good software and package development practices:
The Community Track is focused on community-building skills:
Next month, we will complete the training with a workshop on Git and GitHub and another on Event Organization.
Coworking
Read all about coworking!
Join us for social coworking & office hours monthly on first Tuesdays!
Hosted by Steffi LaZerte and various community hosts.
Everyone welcome.
No RSVP needed.
Consult our Events page to find your local time and how to join.
-
Tuesday, June 4th, 09:00 Australia Western (01:00 UTC), R in the Wild with cohosts Ernest Guevarra, Tomás Zaba, Nicholus Tint Zaw, Zython Paul Lachica and Steffi LaZerte.
- Work on some of your own wild workflows
- Learn how others use R in the Wild (at work, with or without teams)
- Chat with our cohosts, discuss the challenges they face, and wins they have through their work
-
Tuesday, July 2nd, 14:00 Europe Central (12:00 UTC), Git and GitHub with cohost Zhian Kamvar and Steffi LaZerte.
- Read up on Git and GitHub and how they might serve you
- Start your first Git/GitHub project
- Chat with our cohost about the pros and cons of Git & GitHub, resources for getting started and tips and tricks.
And remember, you can always cowork independently on work related to R, work on packages that tend to be neglected, or work on what ever you need to get done!
Software 
New packages
The following package recently became a part of our software suite:
- dendroNetwork, developed by Ronald Visser: Creating dendrochronological networks based on the similarity between tree-ring series or chronologies. The package includes various functions to compare tree-ring curves building upon the dplR package. The networks can be used to visualise and understand the relations between tree-ring curves. These networks are also very useful to estimate the provenance of wood as described in Visser (2021) DOI:10.5334/jcaa.79 or wood-use within a structure/context/site as described in Visser and Vorst (2022) DOI:10.1163/27723194-bja10014. It is available on CRAN. It has been reviewed by Kaija Gahm and Zachary Gajewski.
Discover more packages, read more about Software Peer Review.
New versions
The following nine packages have had an update since the last newsletter: comtradr (v1.0.0
), dendroNetwork (0.5.4
), drake (7.13.10
), fellingdater (v1.0.2
), melt (v1.11.4
), nasapower (v4.2.1
), osmextract (v0.5.1
), stplanr (v1.2.0
), and traits (v0.5.1
).
Software Peer Review
There are thirteen recently closed and active submissions and 7 submissions on hold. Issues are at different stages:
Find out more about Software Peer Review and how to get involved.
On the blog
Calls for contributions
Calls for maintainers
If you’re interested in maintaining any of the R packages below, you might enjoy reading our blog post What Does It Mean to Maintain a Package?.
Calls for contributions
Also refer to our help wanted page – before opening a PR, we recommend asking in the issue whether help is still needed.
Package development corner
Some useful tips for R package developers. 
Token now needed for code coverage via codecov and {covr} on GitHub Actions
Test coverage reports are useful when assessing and improving tests of an R package.
One can run the covr package locally, or send results to an interface like codecov.io that provides interactive exploration of the output.
It is possible to compute test coverage and send the results to codecov.io on GitHub Actions, using the r-lib/actions actions.
Now, recently, workflows have started to fail if one did not set a codecov.io token as an environment variable.
How to solve this
Notes on package repositories
Lluís Revilla Sancho wrote about Packaging R: getting in repositories.
We particularly note his two definitions of package repositories: the first one consists in making install.packages()
work, the second in adding a layer of checks to packages in the repository.
He then added “R-universe is using the first definition but could be used to generate repositories with checks that comply with the second definition.”
Standardize a DESCRIPTION file in one function call
Do you know about the desc::desc_normalize()
function that orders and formats DESCRIPTION fields in a standard way?
Once you start using it, there’s no way back.
You can also call it indirectly via usethis::use_tidy_description()
that also sets the Encoding field to UTF-8.
Automated refactoring with xmlparsedata
Refactoring code can be tedious manual work, but it can also be tedious automated work. 
Read a post about how to replace all occurrences of a given function call with another one using an XML representation of the code.
What’s your favorite IDE?
Athanasia Monica Mowinckel wrote an informative post about the IDEs she uses.
Code review resources
Beside the tidyverse code review guidance, we can now recommend you check out the code review anxiety workbook by Carol Lee and Kristen Foster-Marks, that explains what code review anxiety is, and describes efficient methods to deal with it.
Last words
Thanks for reading! If you want to get involved with rOpenSci, check out our Contributing Guide that can help direct you to the right place, whether you want to make code contributions, non-code contributions, or contribute in other ways like sharing use cases.
You can also support our work through donations.
If you haven’t subscribed to our newsletter yet, you can do so via a form. Until it’s time for our next newsletter, you can keep in touch with us via our website and Mastodon account.
Continue reading: rOpenSci News Digest, May 2024
Long-term Implications and Future Developments in rOpenSci
The continuous developments at rOpenSci strengthen its position as a key player in the open science community. The organization’s addition to the Research Organization Registry highlights its central role in linking and disambiguating metadata about research organizations in the scholarly record.
rOpenSci Champions Program
The rOpenSci Champions program emphasizes the importance of continuous learning and development. By incorporating technical and community tracks, the program ensures its Champions are well-rounded in both hard and soft skills, making them excellent collaborators in open science projects. It sets the stage for similar initiatives focused on offering comprehensive training in open science skills. Future program iterations might include even more specialized tracks or collaborative partnerships with other open science organizations.
Software Development and Peer Review
The creation and review of new software packages represent a continuous cycle at rOpenSci. The organization is always eager to welcome new package submissions and contributes to the development robust, peer-reviewed software for the open science community. The renewal of packages such as dendroNetwork and comtradr demonstrates the continuous improvement that is integral to software development at rOpenSci. Keeping up with updates and modifications pushes developers to strive for excellence and to stay ahead of the curve in their research fields.
Coworking and Community Building
The embrace of coworking sessions manifests rOpenSci’s commitment to fostering community and collaboration. These sessions allow individuals to come together, learn from each other, and tackle challenges as a collective. This initiative may trigger similar community events fostering collaboration in the open science space.
Actionable Advice Based on Insights
For R Developers:
- Consistently update the packages you develop. Consider submitting your packages to rOpenSci for peer review. It can result in wider uptake of your package by providing an assurance of quality to potential users.
- Take advantage of trainings and workshops hosted by rOpenSci. Repetitive learning and exposure to new ideas and practices can help improve your development skills.
For Open Science Enthusiasts:
- Participate in coworking sessions. It’s not just about coding; it’s an opportunity to network, discuss challenges, and learn from experts.
- Consider becoming an rOpenSci Champion. You will get access to mentoring and training sessions that can boost your profile as an open science practitioner.
For Organizations:
- Follow rOpenSci’s model of creating flexible training programs for your contributors. Catering to different learning styles and areas of interest can increase participant engagement and skill set.
- Encourage team members to participate in rOpenSci’s coworking sessions. This can enhance their skills while allowing them to network with other developers and enthusiasts.
Read the original article