i answer some FAQs on my site: kyleclo.com/mentorship/
i answer some FAQs on my site: kyleclo.com/mentorship/
curious your thoughts on other measures like restricting such pieces to senior authors who have a publication record in the surveyed area?
curious your thoughts on other measures like restricting such pieces to senior authors who have a publication record in the surveyed area?
gs tends to have higher cite counts than s2
s2 clusters paper copies & each cluster grants only +1 citation. without proper clusters, each version (eg, preprint vs published) grants citations.
sadly, users can be unhappy when s2 cite counts are lower cuz of this😥
gs tends to have higher cite counts than s2
s2 clusters paper copies & each cluster grants only +1 citation. without proper clusters, each version (eg, preprint vs published) grants citations.
sadly, users can be unhappy when s2 cite counts are lower cuz of this😥
also not widely known but a core difference between gscholar & semantic scholar (s2)
gscholar separates UI & data, so when you merge papers, change is only local to your page but not your coauthors
s2 updates the underlying data, and UI reflects ground truth for all users
also not widely known but a core difference between gscholar & semantic scholar (s2)
gscholar separates UI & data, so when you merge papers, change is only local to your page but not your coauthors
s2 updates the underlying data, and UI reflects ground truth for all users
core is data voyager (arxiv.org/abs/2402.13610) but local LM instead of GPT
it generates code (map-reduce-filter) that transforms data (csvs), a federated platform executes & returns some output back to system. system repeatedly interprets + generates more code
core is data voyager (arxiv.org/abs/2402.13610) but local LM instead of GPT
it generates code (map-reduce-filter) that transforms data (csvs), a federated platform executes & returns some output back to system. system repeatedly interprets + generates more code