With the even increasing use of ChatGPT there is also a debate not only on responsibility but also crediting findings to individual authors.
The artificial-intelligence (AI) chatbot ChatGPT that has taken the world by storm has made its formal debut in the scientific literature — racking up at least four authorship credits on published papers and preprints. Journal editors, researchers and publishers are now debating the place of such AI tools in the published literature, and whether it’s appropriate to cite the bot as an author.
Software recognition of AI generated text is not 100% accurate in particular if there are less than 1000 characters available. And of course, scientific texts will be always edited to evade the classifier.
Having discussed here this issue yesterday, we think that we need some kind of software regulation – sending the generated AI output not only to the individual user but keeping a full logfile of the output that can be accessed, indexed and searched by everybody.
Of 3556 analyzed articles, 3416 contained DAS. The most frequent DAS category (42%) indicated that the datasets are available on reasonable request. Among 1792 manuscripts in which DAS indicated that authors are willing to share their data, 1670 (93%) authors either did not respond or declined to share their data with us. Among 254 (14%) of 1792 authors who responded to our query for data sharing, only 122 (6.8%) provided the requested data.
Both issues took me many years of my scientific life. It is recognized by politics in Germany but also the most recent action plan looks … ridiculous. Why not making data and software sharing mandatory at time of publication?
Leaflet is great for mapping in epidemiology with quick results of just cut & pasting a few lines. Problems do start, however, whenever running a more advanced project. It’s a pain, as plugins overwrite functions and basic css layouts. Or layers do not allow clickable links (as propation is being prohibited). Or geojson data that are rejected for whatever reason. A showcase project, that had been planned for 2 days, took more than 1 week as the documentation is frequently unclear, incomplete and often hard to understand without any (jsfiddle) example. Numerous Google searches helped, as well as peaking into the sourcecode, while also other stack overflow posters have been very helpful. Continue reading Leaflet.js – layer order, layer address and links→
A recent paper identifies 10 rules for better pictures. As I have also given several lectures on that topic, I was excited what the authors think…
1. Know your audience. This is trivial as you never know your audience.
2. Identify your message. True and not true at the same time. True as it makes your findings more evident – not true if you are allowing a reader to find his own message.
3. Adapt the figure to the support medium. Trivial. May be very time consuming.
4. Captions are not optional. Absolutely true, I also suppport good captions – mini stories for those who can’t read the whole text.
5. Do not trust the defaults. Trivial. No one does.
6. Use color efficiently. Not really, avoid colors for those of us who are colorblind and to avoid expensive page charges.
7. Do not mislead the reader. Why should I?
8. Avoid Chartjunk. Absolutely. Most frequent problem.
9. Message trumps beauty. Sure, form follows function.
10. Get the right tool. Maybe correct while the further recommendations look like a poor man’s effort to make his first graphic at zero cost: Gimp, Imagemagick, R…
I am currently switching to Mapfactor Navigator mainly to use now also offline Open Street Maps.
The main problem is to get all those old waypoints converted. Unfortunately it is confusing what developers but users are reporting on different forums. MN obviously used different tools at different times and even different directories.
<body oncontextmenu=”return false;”>
Please try a right click now…
When visiting the offending website, type the following into the URL bar of your browser:
This afternoon I attended a talk at MPI of Yurii Aulchenko about his R package genABEL. He uses a nice trick to convert genotypes into 8 bit (as there are is no 2 bit format 00,01,10,11) which saves quite a lot of memory.
And here is the E type that I have seen a couple of months ago: