text:
{
  "title": "Agree or disagree: we need more/friendlier #rstats tools for converting unstructured web [scraping] data into data frames, e.g., https://t.co/T4Kcrns6f1",
  "date": "2019-02-18"
}

# rstats

> **Ben Saunders** (@bensaun; 61/1): Agree or disagree: we need more/friendlier #rstats tools for converting unstructured web [scraping] data into data frames, e.g., https://t.co/T4Kcrns6f1  [↪](https://twitter.com/dataandme/status/1097589976177561606)

<!-- -->

> **Leon Eyrich Jessen** (@jessenleon; 46/3): Me to my students: "Always carefully comment your code so others can understand what you did."
>
Me just now:
### DON'T RUN THIS SECTION  IT IS APPARENTLY AN INCANTATION TO RAISE THE DEVIL ###
>
#rstats  [↪](https://twitter.com/dataandme/status/1097598546931527684)

<!-- -->

> **matt d'anna** (@_less_wrong; 20/3): Two tiny modelr releases in the last two weeks: https://t.co/zymYzdOaMu #rstats  [↪](https://twitter.com/dataandme/status/1097616964216856576)

<!-- -->

> **Andrew Fraser + C₈H₁₀N₄O₂** (@Arfness; 13/2): Another brushing effect for {mapdeck}, this time on points. use `brush_radius` in `add_scatterplot`
>
#rstats #gis #dataviz https://t.co/gUkzYrIkJT  [↪](https://twitter.com/dataandme/status/1097607686856667136)

<!-- -->

> **Sean Anderson** (@tangled_banker; 12/6): 🏎 Dusted or Busted? w/ help from 𝚁
🏁 "An Empirical Analysis of RuPaul's Drag Race Contestants" by @stevenvmiller
https://t.co/TtcnEzmwFE #rstats https://t.co/ppEf0UhwGP  [↪](https://twitter.com/dataandme/status/1097621031173398528)

<!-- -->

> **lopierra** (@lopierra; 12/3): New experiment: visualising Chinese urbanisation using elevation-style hillshade based on @CopernicusEU built-up-area data, rendered with @tylermorganwall’s rayshader
>
Code here for getting and transforming data, rendering plots: https://t.co/Pf9YBOBbZ7 #rstats #dataviz #gistribe https://t.co/fBANcbhSBi  [↪](https://twitter.com/dataandme/status/1097631907960053766)

<!-- -->

> **Sondra Stegenga** (@stegso; 12/1): Using #rstats to communicate with your amazing intern who just taught an R intro to your Bachelor students … https://t.co/Rzt2PGjgBD  [↪](https://twitter.com/dataandme/status/1097567089987149825)

<!-- -->

> **CRAN Package Updates** (@CRANberriesFeed; 11/1): Testing a googleComputeEngineR template that launches a GPU enabled VM for "Deep learning with R" in just two lines of R https://t.co/Z1u12rQsO9 - thanks to @cboettig for the docker container rocker/ml-gpu that makes it all possible #rstats  [↪](https://twitter.com/dataandme/status/1097593076070207490)

<!-- -->

> **Joel Nitta** (@joel_nitta; 10/9): Here’s How Uber’s Ludwig Helps Deploy Code-Free DL Models. #BigData #Analytics #DeepLearning #MachineLearning #DataScience #AI #IoT #IIoT #PyTorch #Python #RStats #TensorFlow #JavaScript #ReactJS #GoLang #CloudComputing #Serverless #DataScientist #Linux
https://t.co/s5d74cUplk https://t.co/KyCEKnjwxZ  [↪](https://twitter.com/dataandme/status/1097591985295093760)

<!-- -->

> **Kristen Nolting** (@KristenNolting; 9/2): ⚡ Quick #rstats tips w/ @nj_tierney in 3 mins!
📺 "Announcing 'Just Three Things'"
https://t.co/mGlvXcK0VR  [↪](https://twitter.com/dataandme/status/1097583026207449089)

<!-- -->

> **Darth Vadose 🏴** (@Darth_Vadose; 7/9): AIL Framework - Analysis Information Leak framework. #BigData #Analytics #MachineLearning #DataScience #AI #CyberSecurity #IoT #IIoT #PyTorch #Python #RStats #TensorFlow #Java #JavaScript #ReactJS #GoLang #CloudComputing #Serverless #DataScientist #Linux
https://t.co/jZH1X48M6N https://t.co/hc9Px2sQqr  [↪](https://twitter.com/dataandme/status/1097589139338276864)

<!-- -->

> **CRAN Package Updates** (@CRANberriesFeed; 7/3): Made a simple Shiny app (https://t.co/qmjCYXe8fI) to decide what veg to plant based on soil temp. Learned to use supercool {tabulizer} package (https://t.co/KA2Xjjsul7) to extract tables from PDFs, and how to deploy on https://t.co/yjSMYtJyaf! #rstats 🍅🥕🥬  [↪](https://twitter.com/dataandme/status/1097591929473122304)

<!-- -->

> **ai korg** (@ai_korg; 7/1): Avui hem finalitzat la 1a edició del curs Utilirzar #R com un Sistema d'Informació Geogràfica. Molt bon feedback rebut per part de tots els assistents. Ara ja toca pensar en la següent edició! #GIS #rstats @ClimaGroupUB @DeptGeografiaUB https://t.co/D7lpl6Kvfl  [↪](https://twitter.com/dataandme/status/1097565108308447232)

<!-- -->

> **CRAN Package Updates** (@CRANberriesFeed; 7/0): Let’s celebrate #rstats' diversity! What projects/initiatives do you appreciate for making #rstats a more inclusive community, from a personal/functional/technical/any other standpoint?
>
https://t.co/KcQB0dHJEt  [↪](https://twitter.com/dataandme/status/1097582012762939392)

<!-- -->

> **Zorro Notorious M. E. B.** (@znmeb; 6/0): I'm accepting the things I cannot change (i.e. achieving perfection), and so I'm publishing the imperfect analysis I've been dragging for over a year and have no patience to drag any longer.
Thread with #rstats charts below. The post is here: https://t.co/S3jTMN1ynr https://t.co/8BExZ1sIa8  [↪](https://twitter.com/dataandme/status/1097564341132505090)

<!-- -->

> **César** (@cizzart; 6/0): There are many that contributed to this success. Thanks to all!
#RStats #rspatial https://t.co/NsppT6veXt  [↪](https://twitter.com/dataandme/status/1097562674630668291)

<!-- -->

> **CRAN Package Updates** (@CRANberriesFeed; 5/9): DeepUbi:Ubiquitination Sites in Proteins. #BigData #Analytics #DeepLearning #MachineLearning #DataScience #AI #IoT #IIoT #PyTorch #Python #RStats #TensorFlow #Java #JavaScript #ReactJS #GoLang #CloudComputing #Serverless #DataScientist #Linux #HealthTech
https://t.co/jk5QOTdoMY https://t.co/suBP4mF6iB  [↪](https://twitter.com/dataandme/status/1097587079863709698)

<!-- -->

> **Milos Resimic** (@re_milos; 5/2): I learned a bunch by analyzing this data for PhDs awarded by field from 2008 - 2017.  It is a little surprising that the Engineering broad field had the lowest number of PhDs awarded. #TidyTuesday #rstats @R4DScommunity https://t.co/oRKl6uwk6I  [↪](https://twitter.com/dataandme/status/1097618068308520960)

<!-- -->

> **Jack O'Sullivan** (@DrJackOSullivan; 5/1): Hooray! New #rstats geometry 0.4.0 on CRAN with new features and functions  https://t.co/qc3hMPKfsy (and will compile with Intel i.e. should now work on raijin #australia ...)  [↪](https://twitter.com/dataandme/status/1097594255474798594)

<!-- -->

> **Comunidad R Hispano** (@R_Hisp; 5/0): It's #familyday in Ontario - so it seemed appropriate to explore some important analytics regarding the P generation's contribution to my online popularity #Rstats https://t.co/gx61d02eOZ  [↪](https://twitter.com/dataandme/status/1097608445149220864)

<!-- -->

> **Antonio S. Chinchón** (@aschinchon; 5/0): I was today year's old when I learned that #rstats can do *literally* anything 😉
>
(For context: @keholsinger wrote an R script to simulate effective population sizes for our #PopGen class #eeb5348) https://t.co/hqxGzCC6nC  [↪](https://twitter.com/dataandme/status/1097588218965438466)

<!-- -->

> **Oscar Baruffa 🔎📊🇳🇱** (@oscar_b123; 4/2): This week’s #dsba5122 class on distributions and uncertainty is probably my favorite so far. Big h/t to @albertocairo, @ClausWilke, @mjskay & @krstoffr whose chapters, demos, code and past talks were fun to study up to prepare. #rstats #dataviz #gganimate https://t.co/rzfvvsUO3P  [↪](https://twitter.com/dataandme/status/1097597156142264321)

<!-- -->

> **Andy Murtha** (@murtha_andy; 4/1): In Dev: WiGLE Your Way Into A Hotspot with wiglr https://t.co/LCEkqiUnBk #rstats #DataScience  [↪](https://twitter.com/dataandme/status/1097597980058750984)

<!-- -->

> **Thomas Hütter** (@DerFredo; 4/1): Twitterverse of the latest #1od5miliona protests.
>
Strong polarization and pro-govt crusaders more engaged than before.
>
Node-user, edge-retweet, color-community (green, anti-govt, red, pro-govt).
>
Interactive: https://t.co/hhRivcB0Px
#rstats #gephi https://t.co/oYbV1qvrOJ  [↪](https://twitter.com/dataandme/status/1097576772227473409)

<!-- -->

> **We are R-Ladies** (@WeAreRLadies; 4/0): @Diego_Koz @NatsuSh Felicitaciones y éxitos a ambos. #rstats y #rladies me permitió conocerlos un poquitito y estoy segura que van a romperla!!...y que algo de todo lo que aprendan y generen seguro va a llegar a estas latitudes 😉👏💪  [↪](https://twitter.com/dataandme/status/1097616677821444097)

<!-- -->

> **Art Steinmetz** (@adababbage; 4/0): working on my dissertation, arguably the most professional-looking graph I've made to date, seems worth sharing #rstats https://t.co/XCceRCdVFv  [↪](https://twitter.com/dataandme/status/1097595215710433282)

<!-- -->

> **CRAN Package Updates** (@CRANberriesFeed; 4/0): @kierisi And it’s great to be part of the #rstats community following her lead! :)
>
https://t.co/ggKKbhKnfA  [↪](https://twitter.com/dataandme/status/1097586974460993541)

<!-- -->

> **Ifeoma Egbogah** (@negbogah; 3/3): Officially announcing nordicdatalab:
Data Science is hard - let us teach you how it is done!
Learn a modern workflow in R with expert instructors from industry and academia - join us May 20-21st. Book now at https://t.co/GONedoPjdW
Tags: #dataScience, #RStats, #dataAnalysis https://t.co/yA9DT2yj9X  [↪](https://twitter.com/dataandme/status/1097596002247282689)

<!-- -->

> **Dr. GP Pulipaka** (@gp_pulipaka; 3/1): Raincloud plot made in #Rstats for conditionally accepted manuscript. Thank you @MicahGAllen and colleagues for building on ggplot2 to develop these visualizations https://t.co/WhcBQoheiM https://t.co/SY0H9bqVGQ  [↪](https://twitter.com/dataandme/status/1097624324922634241)

<!-- -->

> **FelipeBarros** (@FelipeSMBarros; 3/1): Planes para el 5 de marzo en Sevilla #purrr #tidyverse #rstats https://t.co/E9OH51Lr1d  [↪](https://twitter.com/dataandme/status/1097600543533481985)

<!-- -->

> **Daniel Falbel** (@dfalbel; 3/1): Score Involvements https://t.co/ig9UWxQ6yl #rstats #DataScience  [↪](https://twitter.com/dataandme/status/1097577810221248512)

<!-- -->

> **Carl Carrie** (@carlcarrie; 3/0): Finally pushed my first #rstats package of 5 functions to github today. As they say: perfect is the enemy of good. I can see what isn't good about the code (some of which I wrote months ago), but realise that even what I think is good is probably mediocre for an experienced coder  [↪](https://twitter.com/dataandme/status/1097585635387412480)

<!-- -->

> **Joyce Robbins** (@jtrnyc; 3/0): For my master’s thesis I am working with @TeamInteractCA to analyze how exposure to active transportation infrastructure influences physical activity levels! I am very excited to be working on this project! #gradlife #research #rstats  [↪](https://twitter.com/dataandme/status/1097581225429164034)

<!-- -->

> **Keep It Surly** (@surlyurbanist; 3/0): "Yay for cycling and data viz together, but this pie chart kills me. So, I tried to be the change I wished to see in the world" #Rstats https://t.co/9fotD7OPzZ  [↪](https://twitter.com/dataandme/status/1097580761610219520)

<!-- -->

> **George Mount** (@gjmount; 3/0): Birthday gift 🎂  #rstats stickers. #COGugaison #CARTElette Thanks @AlainQLT https://t.co/mGTcourhCi  [↪](https://twitter.com/dataandme/status/1097578368374059008)

<!-- -->

> **Data Scientists** (@DataScienceFr; 3/0): WOW! Thank you jsonlite authors! Your helpful error message just made my day! (Yes, I think it is now time for a break).
#rstats rocks. https://t.co/8NETXCP1yU  [↪](https://twitter.com/dataandme/status/1097575841041592320)

<!-- -->

> **Luke Smith** (@lksmth; 2/7): ArcGIS: Open Datasets. #BigData #Analytics #GeoSpatial #GIS #MachineLearning #DataScience #AI #IoT #IIoT #PyTorch #Python #RStats #TensorFlow #JavaScript #ReactJS #GoLang #CloudComputing #Serverless #DataScientist #Linux
https://t.co/IcodyboGMJ https://t.co/423Ffa9gGc  [↪](https://twitter.com/dataandme/status/1097593942479056896)

<!-- -->

> **amber medina** (@alouiseme; 2/1): I've just come across some great hand drawn diagrams from 1929. They show hydro-/meteorological parameters for #Venezia, Italy. Mid-February 1929 was one of the coldest periods on record in this area. Average temperature was as low as -10°C (14°F). Data via @ISPRA_Press #rstats https://t.co/T0CazFdjuX  [↪](https://twitter.com/dataandme/status/1097579668386050050)

<!-- -->

> **claudîus** (@dataclaudius; 2/1): Little known gem that I just found out!
Make.names() will convert column names into syntactically correct variable names in R. For eg, if you have spaces in the variable name - it'll replace the space with a '.'.  #rstats #tidyverse  [↪](https://twitter.com/dataandme/status/1097573016203128833)

<!-- -->

> **R-bloggers** (@Rbloggers; 2/0): About a month ago, I had no idea what @travisci was, but fumbled through it anyway. Here's the description past me would have loved:
>
Travis-CI simulates installing your package on a fresh installation of R on multiple operating systems and tells you how it fails. #rstats  [↪](https://twitter.com/dataandme/status/1097608030785626117)

<!-- -->

> **sonia ardila** (@soniaardila1; 2/0): @seanpmackinnon @PsychopharmUTAS @psychopy @LisaDeBruine @dalejbarr @UofGPsychology There’s a ‘syntax mode’ in JAMOVI, which can used in the #rstats ‘jmv’ package  [↪](https://twitter.com/dataandme/status/1097596733570326529)

<!-- -->

> **Alexis Norris** (@AlexisLNorris; 2/0): @EstebanFerJur @Dalal_EL_Hanna Note that there is a whole suite of similar #rstats workshops here: https://t.co/P3foGf79N3 in English and French. The @Csbq_qcbs_stu  have done a tremendous job putting those together!  [↪](https://twitter.com/dataandme/status/1097588641310883840)

<!-- -->

> **Josh PH** (@JPohlkampHartt; 2/0): When Nathan Yau ( @flowingdata ) comes to #eyeo2019  this June to talk #dataviz & #rstats we'll be sure he gets to try a few @surlybrewing brews. They are special. Love his brewery Roadtrip project. Happy to see Surly made the map.  https://t.co/06k5oVyC0b https://t.co/rwljRJTytg  [↪](https://twitter.com/dataandme/status/1097584361979985920)

<!-- -->

> **We are R-Ladies** (@WeAreRLadies; 1/1): Does any #rstats peeps have any experience building command line utilities? Not finding much info online. #tidyverse #cli  [↪](https://twitter.com/dataandme/status/1097627882518589441)

<!-- -->

> **Ryan Wesslen** (@ryanwesslen; 1/1): #DataCube #SPatialDataScience with #rstats: https://t.co/fIfUugKogk  [↪](https://twitter.com/dataandme/status/1097620825677676545)

<!-- -->

> **We are R-Ladies** (@WeAreRLadies; 1/1): Course in modern data analysis in R from @nordicdatalab
Tags: #dataScience, #Rstats, #dataAnalysis https://t.co/kkgUGhXIMk  [↪](https://twitter.com/dataandme/status/1097596842819420160)

<!-- -->

> **Taras Kaduk** (@taraskaduk; 1/1): Have a favorite #Tweetorial or #JournalClub thread?
>
Link it below and I'll add it to a github page.
>
#EpiTwitter #StatsTwitter #RStats #CardioTwitter #MedTwitter #AcademicChat #PhDChat #ECRChat  [↪](https://twitter.com/dataandme/status/1097595611929604096)

<!-- -->

> **Fernanda Ramirez-Espinoza** (@lapumi; 1/1): Anyone have a best practice on hex-tile maps, preferably for countries in R #rstats? I spent half an hour or so trolling online and found no less than 6 methods, all of which are completely different. Any guidance would be greatly appreciated @rstudiotips #dataviz #ggplot2  [↪](https://twitter.com/dataandme/status/1097593982538969089)

<!-- -->

> **R-bloggers** (@Rbloggers; 1/0): The #future package together with #furrr are my favorites #rstats packages at the moment!  [↪](https://twitter.com/dataandme/status/1097618923204288512)

<!-- -->

> **nordicdatalab** (@nordicdatalab; 1/0): There's a good #rstats screencast here with 3 quick tips, plus I like how @nj_tierney has set up his rstudio environment. I might try it. https://t.co/iCSnAyR1pG  [↪](https://twitter.com/dataandme/status/1097615799378956288)

<!-- -->

> **CRAN Package Updates** (@CRANberriesFeed; 1/0): From a coding perspective, I’m curious about the different #rstats ‘dialects’ (eg. in @minebocek’s syntax cheatsheet https://t.co/KcEZAFZTRo) and I really enjoy seeing how various people/packages approach similar problems from different angles!  [↪](https://twitter.com/dataandme/status/1097591037600645121)

<!-- -->

> **Martin John Hadley** (@martinjhnhadley; 1/0): Cuántos retos tenemos !@Cruz_Julian_  Sigamos pedaleando!  #data #datascience #statistics #rstats https://t.co/YyRhyodVte  [↪](https://twitter.com/dataandme/status/1097582630495752192)

<!-- -->

> **yoshidk6** (@yoshidk6; 1/0): @jennwatch @GraphPad Agreed, I’ve used Prism in the past but it’s simply too expensive and inaccessible to many. Plotting in #Rstats is now a better option for training students  [↪](https://twitter.com/dataandme/status/1097578626629976064)

<!-- -->

> **Tullus Aufidius** (@isbrutussick; 1/0): @AfricaRUsers @southmapr "Hey, my name is Ifeoma, from Nigeria, I love R and use it everyday for my personal analysis , as an epidemiologist"
>
#weRAfrica #rstats...  [↪](https://twitter.com/dataandme/status/1097577718445678593)

<!-- -->

> **Kendall Smith** (@KendallaSmith_; 1/0): A few more charts (and a lot of words) are here: https://t.co/S3jTMN1ynr
Have you found your city? Are you surprised by the results? #rstats  [↪](https://twitter.com/dataandme/status/1097564382551261184)

<!-- -->

> **R-Ladies NYC** (@RLadiesNYC; 1/0): I wrote an app that automatically tidies and cleans uploaded Hansard .txt files from the House of Lords. Inspired by work of @TheyWorkForYou. https://t.co/UDH9SEqaJ7  #rstats #ShinyR #opengovernment  [↪](https://twitter.com/dataandme/status/1097564324208562182)

<!-- -->

> **Giada Porcedda** (@GiadaPorcedda; 1/0): @dataandme @MattOldach I wish to protest the excess of whimsy in the #rstats community.
https://t.co/pwwt22ixLd  [↪](https://twitter.com/dataandme/status/1097561868602884098)

<!-- -->

> **Matt Chaib** (@mattchaib; 0/1): ok! #dataFam & #dataVizPro's & #dataVizPoser's our big #VegaViewer v3.0 is out! Now w/370 #vegaLite examples in tow! 4 you 2 test 'em #maps 🗺 & #graphs 📊 in @code on a go, on a ✈, on a 🚄, on a 🚤, in a 📦 with a 🐐, and no #d3 #py || #rstats required! https://t.co/2Z20VsyZoo  [↪](https://twitter.com/dataandme/status/1097595479590924289)

<!-- -->

> **Mathew 'Night Science' Ling** (@lingtax; 0/1): dplyr or pandas? Discuss #rstats #epitwitter #Python  [↪](https://twitter.com/dataandme/status/1097587494080602112)

<!-- -->

> **Analytics France** (@AnalyticsFr; 0/1): R users, help! Do you know how to get a balance test like the first pic (or similar) using #stargazer? I can only get it to do the extended version and then I’m editing by hand. There’s gotta be a more efficient way! #rstats #ruser #EconTwitter https://t.co/oWdMekrXba  [↪](https://twitter.com/dataandme/status/1097574050304540673)

<!-- -->

> **Mike Kearney📊** (@kearneymw; 0/0): New #rstats blogpost: building #docker images with secrets 🕵♂🐳 Especially handy for installing private packages from github without leaving behind your 🔑  https://t.co/FCUf4MF5Eh https://t.co/mv5K7Xn7g3  [↪](https://twitter.com/dataandme/status/1097635153235587074)

<!-- -->

> **Julia Strand** (@juliafstrand; 0/0): Works for lapply() but not for #purrr  map() -- but I thought map() was lapply() #rstats #tidyverse https://t.co/9RDwu71qAM  [↪](https://twitter.com/dataandme/status/1097634350840102912)

<!-- -->

> **Hadley Wickham** (@hadleywickham; 0/0): @MoralHazardPay Vaporwave rstats is easily the most 2019 thing that will happen  [↪](https://twitter.com/dataandme/status/1097633854632968192)

<!-- -->

> **Symbolix** (@symbolixAU; 0/0): CRAN updates: ggsn nonmem2R shinyWidgets tidygraph https://t.co/y5W2NTKSXT #rstats  [↪](https://twitter.com/dataandme/status/1097632946847170560)

<!-- -->

> **Mara Averick** (@dataandme; 0/0): New CRAN package segmenTier with initial version 0.1.2 https://t.co/0QdYpl5sce #rstats  [↪](https://twitter.com/dataandme/status/1097632811794743296)

<!-- -->

> **John Burn-Murdoch** (@jburnmurdoch; 0/0): CRAN updates: poplite https://t.co/y5W2NTKSXT #rstats  [↪](https://twitter.com/dataandme/status/1097587084594954241)

<!-- -->

> **Eiko Fried** (@EikoFried; 0/0): CRAN updates: flexmix modelr https://t.co/y5W2NTKSXT #rstats  [↪](https://twitter.com/dataandme/status/1097617301136949257)

<!-- -->

> **Mark Edmondson** (@HoloMarkeD; 0/0): CRAN updates: rayshader https://t.co/y5W2NTKSXT #rstats  [↪](https://twitter.com/dataandme/status/1097571987843698688)

<!-- -->

> **Dr. GP Pulipaka** (@gp_pulipaka; 0/0): CRAN updates: libcoin https://t.co/Au8lWQ2fGU https://t.co/y5W2NTKSXT #rstats  [↪](https://twitter.com/dataandme/status/1097602195036483585)

<!-- -->

> **Mara Averick** (@dataandme; 0/0): Today turned out to be an #rstats failure day :-(  [↪](https://twitter.com/dataandme/status/1097632775413395456)

<!-- -->

> **Dr. GP Pulipaka** (@gp_pulipaka; 0/0): 👇 @RLadiesBmore founder and #rstats pro @stephaniehicks! (cc @RLadiesGlobal )
🙌 to @JohnsHopkinsSPH for bringing her to #Baltimore https://t.co/sUl38zKCKY  [↪](https://twitter.com/dataandme/status/1097632114709807104)

<!-- -->

> **Marc Lemus** (@lemuscanovas; 0/0): Mandalas, created and colored with #rstats (tutorial w/code) #generative #maths
https://t.co/b7Z8wDsAKy 🎨😃 https://t.co/sRNlaAuQkQ  [↪](https://twitter.com/dataandme/status/1097629629236547586)

<!-- -->

> **Taras Kaduk** (@taraskaduk; 0/0): I really feel this tweet. #rstats #listsoflists https://t.co/IQxoFZfOCj  [↪](https://twitter.com/dataandme/status/1097627088201310214)

<!-- -->

> **Reinhard Furrer** (@ReinhardFurrer; 0/0): Sector Skews
       in R #rstats
>
https://t.co/sW1bgA4wmo https://t.co/xLPJpXOncW  [↪](https://twitter.com/dataandme/status/1097626689918697472)

<!-- -->

> **Tony Galvan** (@GDataScience1; 0/0): firebrick1 is my favorite red in #Rstats.
HBU?  [↪](https://twitter.com/dataandme/status/1097624090792333312)

<!-- -->

> **Michael Sumner** (@mdsumner; 0/0): New #rstats GIS blogpost! Where's the centre of @UniofOxford, and how has it changed over time? https://t.co/y2VL6gOXZ9 ... there's an obligatory (but dull) GIF in the post 😄 https://t.co/qusbeuStKg  [↪](https://twitter.com/dataandme/status/1097622845860007936)

<!-- -->

> **Yanina Bellini** (@yabellini; 0/0): Looks like @rstudio is on the offense today. #rstats https://t.co/V47YbK94Uy  [↪](https://twitter.com/dataandme/status/1097617298972725249)

<!-- -->

> **Joe Wasserman** (@JoeWasserman; 0/0): Any good guides on performing doubly robust propensity score estimates that go through it step by step? I have better grasp of theory but still unclear as to the actual modeling steps #rstats  [↪](https://twitter.com/dataandme/status/1097614710105530368)

<!-- -->

> **BEAP Lab** (@TheBEAPLab; 0/0): I accept that gather() has defeated me. #rstats  [↪](https://twitter.com/dataandme/status/1097606634942201861)

<!-- -->

> **ThinkR** (@thinkR_fr; 0/0): Very interesting experiment of defining  lambda functions in #Rstats https://t.co/A5lfubIPBT  [↪](https://twitter.com/dataandme/status/1097606108544462849)

<!-- -->

> **antuki** (@antuki13; 0/0): rstanやrstanarm等をWindows上でソースからインストールする時の設定 - yoshidk6’s blog https://t.co/jj9eB4ru9P #はてなブログ #rstats #rstan  [↪](https://twitter.com/dataandme/status/1097604726542102528)

<!-- -->

> **Nicholas George** (@NicholasMG; 0/0): #Rstats tip:  glm: is used to fit generalized linear models (”stats”) More: https://t.co/coAj6FVDXy  [↪](https://twitter.com/dataandme/status/1097603854919716864)

<!-- -->

> **Dr. GP Pulipaka** (@gp_pulipaka; 0/0): This lamda functioality would be awesome #rstats https://t.co/VlisdzWaCh  [↪](https://twitter.com/dataandme/status/1097603778302242816)

<!-- -->

> **myweather.ch** (@myweather_ch; 0/0): Posted by hrbrmstr, now on R-bloggers: In Dev: WiGLE Your Way Into A Hotspot with wiglr #rstats https://t.co/tY6VhEAH8Y  [↪](https://twitter.com/dataandme/status/1097602315404668928)

<!-- -->

> **Dilsher  Dhillon** (@TexanDhillon; 0/0): Posted by Rstats on pi: predict/infer, now on R-bloggers: Developing R Packages with usethis and GitLab CI: Part III #rstats https://t.co/x04Q8BtDQI  [↪](https://twitter.com/dataandme/status/1097561980611821571)

<!-- -->

> **Eric R. Scott** (@LeafyEricScott; 0/0): In Dev: WiGLE Your Way Into A Hotspot with wiglr - https://t.co/HjGAM4KEaO #rstats  [↪](https://twitter.com/dataandme/status/1097601533921890304)

<!-- -->

> **Everything Hertz** (@hertzpodcast; 0/0): In Dev: WiGLE Your Way Into A Hotspot with wiglr - https://t.co/slDegG0iGC #rstats  [↪](https://twitter.com/dataandme/status/1097601489512615941)

<!-- -->

> **CSBQ-QCBS** (@csbq_qcbs; 0/0): In Dev: WiGLE Your Way Into A Hotspot with wiglr - https://t.co/caHUDnLdhG #rstats  [↪](https://twitter.com/dataandme/status/1097601396348723206)

<!-- -->

> **eyeo organizers** (@eyeofestival; 0/0): In Dev: WiGLE Your Way Into A Hotspot with wiglr via #rbloggers #rstats #datascience https://t.co/CcmsJd6Vxk  [↪](https://twitter.com/dataandme/status/1097601191859666945)

<!-- -->

> **Dylan McDowell** (@dylanjm_ds; 0/0): In Dev: WiGLE Your Way Into A Hotspot with wiglr #rstats https://t.co/IMFTMHXnZd  [↪](https://twitter.com/dataandme/status/1097600951689625601)

<!-- -->

> **Bailey DeBarmore** (@BaileyDeBarmore; 0/0): @olivierhonnay Werd er een meta-analysis uitgevoerd op de studies in die tabel of bleef het bij pijlen ⬆⬇? Lijkt me een interessante case!  #rstats  [↪](https://twitter.com/dataandme/status/1097598232564256768)

<!-- -->

> **Dan Quintana** (@dsquintana; 0/0): IMHO, regardless of warranty in #rstats (or lack thereof), even with perfectly written bug-free code: people are always going misuse and abuse. A warranty does not mean people engage their brains. https://t.co/oU0a2ChBRG  [↪](https://twitter.com/dataandme/status/1097596561553539075)

<!-- -->

> **dataPixy** (@TarasNovak; 0/0): This! Know your data to ensure accurate & ethical use. Domain knowledge is key but collaboration & use of mixed methods (qualitative data & stakeholder input) are additional ways to increase understanding & ethical use of #bigdata! #rstats #dataethics thx @Randy_Au https://t.co/XP7vjcJNBY  [↪](https://twitter.com/dataandme/status/1097594992703332352)

<!-- -->

> **Deemah 🇺🇦  🇳🇴** (@dmi3k; 0/0): We can just write an Excel macro...that's what Doug used to say. #rstats  [↪](https://twitter.com/dataandme/status/1097579060769816581)

<!-- -->

> **Thomas Hütter** (@DerFredo; 0/0): After two days, I was finally able to create a PostgreSQL database and query the data into #rstats. Takeaway: always use lowercase for table/column names when creating a database🥴.  [↪](https://twitter.com/dataandme/status/1097577469736112129)

<!-- -->

> **Analytics France** (@AnalyticsFrance; 0/0): @TexanDhillon I use `snakecase` for this - https://t.co/f8A5RTTfge #rstats  [↪](https://twitter.com/dataandme/status/1097573694291865600)

<!-- -->

> **Data Scientists** (@DataScientistsF; 0/0): @jazzejay_ just posted the next round of meet and greet mentoring #rladies #rstats chats :: Don’t forget to Sign-up! https://t.co/MQs4GQyXLh @channel  [↪](https://twitter.com/dataandme/status/1097572678930558976)

<!-- -->

> **Raf Aerts⚡** (@rafaerts; 0/0): #rdata #rstats: genpop constructor - https://t.co/EUPq32zCfU  [↪](https://twitter.com/dataandme/status/1097572303452422145)

<!-- -->

> **Joanne Potts** (@AnalyticalEdge; 0/0): Politica : Actividad en la plataforma twitter de los Senadores y Diputados de #Misiones.
Se puede observar el nivel de actividad | periodo posterior a 10-01-2018 y 01-01-2019 @mauricloss @cbritezmisiones @MaggieSolariQ
#rstats #Posadas #Argentina @gobmisiones @prensa_camara https://t.co/Hk5jE6kviH  [↪](https://twitter.com/dataandme/status/1097570180006334464)

<!-- -->

> **#rstats data** (@rstatsdata; 0/0): Would anybody recommend this?  #MondayFun #PhD #phdchat #phdlife #Rstats https://t.co/bXf56kjX4E  [↪](https://twitter.com/dataandme/status/1097563328837230592)

<!-- -->

repository: batpigandme/twitter-blogdown

repo_name: batpigandme/twitter-blogdown


text:
---
title:  "Release: Add-Ons 1.8"
---

We are proud to announce the availability of Add-On Self Administration 1.8 and Add-On Administration 1.8.
This release mostly brings compatibility fixes to make the add-ons work with all versions of OSIAM >= 2.2 again.
Support for OSIAM 3.0 has been added too.
A major bug in Add-On Administration was fixed as well.

You can download the add-ons in different packaging formats using one of the following links:

      Service
      Download

      addon-self-administration

          .tar.gz
          .zip
          .war

      addon-administration

          .tar.gz
          .zip
          .war

It follows an overview of the most important changes.
See the full changelogs at the [Add-On Self Administration 1.8 release page on GitHub](https://github.com/osiam/addon-self-administration/releases/tag/v1.8)
and the [Add-On Administration 1.8 release page on GitHub](https://github.com/osiam/addon-administration/releases/tag/v1.8).

## Add-On Self Administration

### Compatibility

In release 1.7 the Add-On Self Administration introduced an incompatibility with versions of OSIAM <= 2.3.
This release restore this compatibility.
To connect to OSIAM <= 2.3, you have to set the configuration property `org.osiam.connector.legacy-schemas` to `true`:

{% highlight properties %}
org.osiam.connector.legacy-schemas=true
{% endhighlight %}

For more information see the [Add-On Self Administration documentation](https://github.com/osiam/addon-self-administration/blob/v1.8/docs/configuration.md#orgosiamconnectorlegacy-schemas).

Also, support for OSIAM 3.0 has been added.
To connect to OSIAM 3.0, you have to use the configuration property `org.osiam.home` instead of the other endpoint properties:

{% highlight properties %}
org.osiam.home=http://localhost:8080/osiam
{% endhighlight %}

For more information see the [Add-On Self Administration documentation](https://github.com/osiam/addon-self-administration/blob/v1.8/docs/configuration.md#osiam-3x).

### Changed Scopes

The Add-On Self Administration now uses the scope `ADMIN` to connect to OSIAM.
With this we are dropping support for the deprecated method-based scopes.
This means you have to update the respective OAuth client before you can update the add-on.
To do this issue the following SQL statement:

{% highlight sql %}
INSERT INTO osiam_client_scopes (id, scope) VALUES (<id of addon-self-administration-client>, 'ADMIN');
{% endhighlight %}

Most of the time `<id of addon-self-administration-client>` will be `10`.
If you have a non-standard setup, then it might have a different value.

### Plug-In API 1.5

A new version of the Add-On Self Administration Plug-In API has been released.
It's built against the latest SCIM schema and we changed the dependency on it to scope `provided`.
See the full changelog and downloads at the
[Add-On Self Administration Plug-In API 1.5 release page on GitHub](https://github.com/osiam/addon-self-administration-plugin-api/releases/tag/v1.5).

## Add-On Administration

### Compatibility

In release 1.7 the Add-On Administration introduced an incompatibility with versions of OSIAM <= 2.3.
This release restore this compatibility.
To connect to OSIAM <= 2.3, you have to set the configuration property `org.osiam.connector.legacy-schemas` to `true`:

{% highlight properties %}
org.osiam.connector.legacy-schemas=true
{% endhighlight %}

For more information see the [Add-On Administration documentation](https://github.com/osiam/addon-administration/blob/v1.8/README.md#osiam-endpoints-osiam-2x).

Also, support for OSIAM 3.0 has been added.
To connect to OSIAM 3.0, you have to use the configuration property `org.osiam.endpoint` instead of the other endpoint properties:

{% highlight properties %}
org.osiam.endpoint=http://localhost:8080/osiam
{% endhighlight %}

For more information see the [Add-On Administration documentation](https://github.com/osiam/addon-administration/blob/v1.8/README.md#osiam-endpoints-osiam-3x).

### Changed Scopes

The Add-On Administration now uses the scope `ADMIN` to connect to OSIAM.
With this we are dropping support for the deprecated method-based scopes.
This means you have to update the respective OAuth client before you can update the add-on.
To do this issue the following SQL statement:

{% highlight sql %}
INSERT INTO osiam_client_scopes (id, scope) VALUES (<id of addon-administration-client>, 'ADMIN');
{% endhighlight %}

Most of the time `<id of addon-administration-client>` will be `20`.
If you have a non-standard setup, then it might have a different value.

### Boolean Types Extension Fields

Due to a bug, all boolean-types extension fields always displayed the value as `true`, regardless of the real value stored.
Furthermore it was not possible to set the fields to anything else than `true`.
This release fixes this behavior so you can safely use boolean-typed extension fields again.
See also: [https://github.com/osiam/addon-administration/issues/83](https://github.com/osiam/addon-administration/issues/83).

license: MIT

branch_name: refs/heads/master

extension: md

gha_language: CSS

license_type: permissive


text:
---
layout: default
---

# 1996-08-17 - Re: Protecting floating datahavens?

## Header Data

From: Robert Hettinga<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message Hash: aeb70e1432f8d489c5ef53e150254acefeccf479e4a8e2188f1bf9f47ec01a75

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1996-08-17 19:10:16 UTC

Raw Date: Sun, 18 Aug 1996 03:10:16 +0800

## Raw message

```
{% raw  %}From: Robert Hettinga<EMAIL_ADDRESS>Date: Sun, 18 Aug 1996 03:10:16 +0800
To<EMAIL_ADDRESS>Subject: Re: Protecting floating datahavens?
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

At 8:04 PM -0400 8/16/96, Bill Stewart wrote:
> There's also a Laissez-Faire City project, which proposes to lease a
> 10-mile-square chunk of land to rent from any cooperative third-world
> government for 50 years or so with a deal of local autonomy.
> It's much less threatening to the Old World Order than calling yourself
> a country, and you've got a government which is making money by
> leaving you alone that at least discourages the most likely invaders
> (itself, and the US) without having to provide much national defense.
> Who knows, maybe they'll actually do something, and rent a chunk of
> Costa Rica or Somaliland or whatever.

Along these lines, there was some comment in the latest Forbes billionaire list issue about a guy who's trying to do something like this in the Phillipenes. I don't think he's going the "total local autonomy" route, but he's definitely doing the Jack Kemp "enterprize" zone, no-tax-on-anything trick.

However, as Black Unicorn has noted here before, the Phillipenes are the only other country besides the USofA where citizens are taxed any income you get, no matter where on earth you actually earn it. (An outcome of the Marcos expulsion, I think). Getting from those kinds of confiscatory laws to no taxes at all will be some mean trick. Given that the Phillipenes, "People Power" or no, could be charitably be called a plutocracy at best, and a cleptocracy at worst, I wish this guy luck. Him being a plutocrat himself may help.

Not that I have anything against plutocrats, mind you. Want to be one myself, someday. Well, "pluto", anyway. I guess it's the "cracy" part of "plutocracy" that gets my undies in a bunch...

Cheers,
Bob Hettinga

-----------------
Robert Hettinga<EMAIL_ADDRESS>e$, 44 Farquhar Street, Boston, MA 02131 USA
"'Bart Bucks' are not legal tender."
                -- Punishment, 100 times on a chalkboard,
                       for Bart Simpson
The e$ Home Page: http://www.vmeng.com/rah/

{% endraw %}
```

## Thread

+ Return to [August 1996](/archive/1996/08)

+ Return to "[Bill Stewart <stewarts@ix.netcom.com>](/authors/bill_stewart_stewarts_at_ix_netcom_com_)"
+ Return to "[Robert Hettinga <rah@shipwright.com>](/authors/robert_hettinga_rah_at_shipwright_com_)"

+ 1996-08-17 (Sat, 17 Aug 1996 11:54:05 +0800) - [Re: Protecting floating datahavens?](/archive/1996/08/f956539e3af42944861924d5c6cb5315268c842acc4ce04b4d0ce9b8cfb947c7) - _Bill Stewart<EMAIL_ADDRESS>  + 1996-08-17 (Sun, 18 Aug 1996 03:10:16 +0800) - Re: Protecting floating datahavens? - _Robert Hettinga<EMAIL_ADDRESS>

gha_license_id: MIT


text:
# Reliable Camera Model Identification Using Sparse Gaussian Processes

If you use this implementation, please cite the [paper](https://ieeexplore.ieee.org/abstract/document/9392307):

```
@ARTICLE{9392307,
  author={Lorch, Benedikt and Schirrmacher, Franziska and Maier, Anatol and Riess, Christian},
  journal={IEEE Signal Processing Letters},
  title={Reliable Camera Model Identification Using Sparse Gaussian Processes},
  year={2021},
  volume={28},
  pages={912--916},
  doi={10.1109/LSP.2021.3070206}
}
```

## Prerequisites

1. Set up virtual environment.

```bash
conda env create --name gpc --file=environment.yml
```

2. (Optional) For comparison to the PI-SVM, clone and compile the PI-SVM authors' code from their [GitHub repository](https://github.com/ljain2/libsvm-openset).
Then open `utils.constants.py` and set `constants[LIBSVM_DIR]` to the path where to find the compiled executables.

## Data preparation

1. Download the [Dresden image database](http://forensics.inf.tu-dresden.de/).

2. Extract SPAM features.

Example:
```bash
PYTHONPATH=`pwd` python spam_features/ddimgdb_extract_features.py \
    --output_dir /media/hdd/camera_model_identification \
    --dresden_dir /mnt/nfs/DresdenImageDB
    [--crop CROP_SIZE]
```

This script will store the extracted features as HDF5 file to the given output directory. If no crop argument is given, the script extracts the features from the full resolution images.

 In particular, we set `MODEL_SELECTION_SEED=91058,SEED=$i,TORCH_SEED=42` with `i=1,...,5`.

Note that there are additional arguments with reasonable default values for controlling the model, the data, and the training.

## Evaluation

To evaluate a single trained Gaussian process classifier, you can use `eval_single.py`.

```bash
python experiments/eval_single.py \
    --dresden_dir /mnt/nfs/DresdenImageDB \
    --features_file $HDD/camera_model_identification/2021_04_13-dresden_spam_features_crop_full_resolution.h5 \
    --model_dir $HDD/camera_model_identification/2021_04_14_08_29_42-gpc
```

To evaluate multiple Gaussian process classifiers trained on the same features, you can use `eval_multiple.py`.

For comparison against the PI-SVM and the combined classification framework (CCF, named "secure SVM" in the code), you can use `eval_and_compare_multiple.py`.

## Additional experiments provided in this repository

**Number of inducing points**

1. Train GPC with different numbers of inducing points, see `experiments/torque/train_max_num_inducing_points_woody.sh`.

2. Evaluate trained GPCs, see `experiments/eval_multiple.py`.

**Impact of ROI size**

1. Extract features with different ROI sizes (by running `ddimgdb_extract_features.py` with the `--crop` parameter).

2. Train GPC with features of every ROI size, see `experiments/torque/train_crops_woody.sh`.

3. Evaluate trained GPCs, see `experiments/eval_and_compare_multiple.py`.

**Unseen post-processing**

1. With a trained GPC, run `experiments/eval_postprocessing.py`.

branch_name: refs/heads/main


text:
# stop

Stop adds functions for graceful app shutdown.

Basic usage is looks like:

```go
import "github.com/ninedraft/stop"

func main() {
    defer stop.Exit()

    // ...
    defer cleanStuff()
    // do stuff
    // ...

    if err := doImportantThing(); err != nil {
        stop.Stop(100)
    }
}
```

In this scenario all defers will be called **before** your program exits with status 100.

## Why I should use it?
Compare with bare `os.Exit`.

```go
import "os"

func main() {
    // ...
    defer cleanStuff() // won't be called if bad stuff happens!
    // do stuff
    // ...

    if err := doImportantThing(); err != nil {
        os.Exit(100)
    }
}

```

Mostly it's important when you are writing to files and handling errors.

## I don't want to import another leftpad dependency!

Then just copy my code to your project :3
It's really just a little more than a usefull snippet, which I have been using for many years.

repository: ninedraft/stop

repo_name: ninedraft/stop


text:
[< Previous](../number-of-segments-in-a-string "Number of Segments in a String")

[Next >](../find-right-interval "Find Right Interval")

## [435. Non-overlapping Intervals (Medium)](https://leetcode.com/problems/non-overlapping-intervals "无重叠区间")

Given a collection of intervals, find the minimum number of intervals you need to remove to make the rest of the intervals non-overlapping.

Example 1:

Input: [[1,2],[2,3],[3,4],[1,3]]
Output: 1
Explanation: [1,3] can be removed and the rest of intervals are non-overlapping.

Example 2:

Input: [[1,2],[1,2],[1,2]]
Output: 2
Explanation: You need to remove two [1,2] to make the rest of intervals non-overlapping.

Example 3:

Input: [[1,2],[2,3]]
Output: 0
Explanation: You don't need to remove any of the intervals since they're already non-overlapping.

Note:

You may assume the interval's end point is always bigger than its start point.

Intervals like [1,2] and [2,3] have borders "touching" but they don't overlap each other.

### Related Topics
  [[Greedy](../../tag/greedy/README.md)]

### Similar Questions
  1. [Minimum Number of Arrows to Burst Balloons](../minimum-number-of-arrows-to-burst-balloons) (Medium)

repository: rohini-raja/leetcode

repo_name: rohini-raja/leetcode


text:
# OpenWithAddon

This add-on adds in the context menu of a local file (tab **Title**) the command **Open with...** which calls the standard dialog of the Windows Explorer. This gives the possibility to open the files with another program than the standard application.

## Releases

The compiled library can be found under [releases](./../../releases) as an archive.

## Disclaimer

>There are no support claims by the company **Swiss Academic Software GmbH**, the provider of **Citavi** or other liability claims for problems or data loss. Any use is at your own risk. All rights to the name **Citavi** and any logos used are owned by **Swiss Academic Software GmbH**.

## License

This project is licensed under the [MIT](LICENSE) License

repository: lutz/OpenWithAddon

repo_name: lutz/OpenWithAddon


text:
# Next Release

## Language changes
* Updates to the layout rule.  We simplified the specification and made
  some minor changes, in particular:
    - Paren blocks nested in a layout block need to respect the indentation
      if the layout block
    - We allow nested layout blocks to have the same indentation, which is
      convenient when writing `private` declarations as they don't need to
      be indented as long as they are at the end of the file.

* New enumeration forms `[x .. y by n]`, `[x .. <y by n]`,
  `[x .. y down by n]` and `[x .. >y down by n]` have been
  implemented. These new forms let the user explicitly specify
  the stride for an enumeration, as opposed to the previous
  `[x, y .. z]` form (where the stride was computed from `x` and `y`).

## New features

* What4 prover backends now feature an improved multi-SAT procedure
  which is significantly faster than the old algorithm. Thanks to
  Levent Erkök for the suggestion.

* There is a new `w4-abc` solver option, which communicates to ABC
  as an external process via What4.

* Expanded support for declaration forms in the REPL. You can now
  define infix operators, type synonyms and mutually-recursive functions,
  and state signatures and fixity declarations. Multiple declarations
  can be combined into a single line by separating them with `;`,
  which is necessary for stating a signature together with a
  definition, etc.

# 2.11.0

## Language changes

* The `newtype` construct, which has existed in the interpreter in an
  incomplete and undocumented form for quite a while, is now fullly
  supported. The construct is documented in section 1.22 of [Programming
  Cryptol](https://cryptol.net/files/ProgrammingCryptol.pdf). Note,
  however, that the `cryptol-remote-api` RPC server currently does not
  include full support for referring to `newtype` names, though it can
  work with implementations that use `newtype` internally.

## New features

* By default, the interpreter will now track source locations of
  expressions being evaluated, and retain call stack information.
  This information is incorporated into error messages arising from
  runtime errors. This additional bookkeeping incurs significant
  runtime overhead, but may be disabled using the `--no-call-stacks`
  command-line option.

* The `:exhaust` command now works for floating-point types and the
  `:check` command now uses more representative sampling of
  floating-point input values to test.

* The `cryptol-remote-api` RPC server now has methods corresponding to
  the `:prove` and `:sat` commands in the REPL.

* The `cryptol-eval-server` executable is a new, stateless server
  providing a subset of the functionality of `cryptol-remote-api`
  dedicated entirely to invoking Cryptol functions on concrete inputs.

## Internal changes

* A single running instance of the SMT solver used for type checking
  (Z3) is now used to check a larger number of type correctness queries.
  This means that fewer solver instances are invoked, and type checking
  should generally be faster.

* The Cryptol interpreter now builds against `libBF` version 0.6, which
  fixes a few bugs in the evaluation of floating-point operations.

## Bug fixes

* Closed issues #118, #398, #426, #470, #491, #567, #594, #639, #656,
  #698, #743, #810, #858, #870, #905, #915, #917, #962, #973, #975,
  #980, #984, #986, #990, #996, #997, #1002, #1006, #1009, #1012, #1024,
  #1030, #1035, #1036, #1039, #1040, #1044, #1045, #1049, #1050, #1051,
  #1052, #1063, #1092, #1093, #1094, and #1100.

# 2.10.0

## Language changes

* Cryptol now supports primality checking at the type level. The
  type-level predicate `prime` is true when its parameter passes the
  Miller-Rabin probabilistic primality test implemented in the GMP
  library.

* The `Z p` type is now a `Field` when `p` is prime, allowing additional
  operations on `Z p` values.

* The literals `0` and `1` can now be used at type `Bit`, as
  alternatives for `False` and `True`, respectively.

## New features

* The interpreter now includes a number of primitive functions that
  allow faster execution of a number of common cryptographic functions,
  including the core operations of AES and SHA-2, operations on GF(2)
  polynomials (the existing `pmod`, `pdiv`, and `pmult` functions), and
  some operations on prime field elliptic curves. These functions are
  useful for implementing higher-level algorithms, such as many
  post-quantum schemes, with more acceptable performance than possible
  when running a top-to-bottom Cryptol implementation in the
  interpreter.

  For a full list of the new primitives, see the new Cryptol
  [`SuiteB`](https://github.com/GaloisInc/cryptol/blob/master/lib/SuiteB.cry)
  and
  [`PrimeEC`](https://github.com/GaloisInc/cryptol/blob/master/lib/PrimeEC.cry)
  modules.

* The REPL now allows lines containing only comments, making it easier
  to copy and paste examples.

* The interpreter has generally improved performance overall.

* Several error messages are more comprehensible and less verbose.

* Cryptol releases and nightly builds now include an RPC server
  alongside the REPL. This provides an alternative interface to the same
  interpreter and proof engine available from the REPL, but is
  better-suited to programmatic use. Details on the protocol used by the
  server are available
  [here](https://github.com/GaloisInc/argo/blob/master/docs/Protocol.rst).
  A Python client for this protocol is available
  [here](https://github.com/GaloisInc/argo/tree/master/python).

* Windows builds are now distributed as both `.tar.gz` and `.msi` files.

## Bug Fixes

* Closed issues #98, #485, #713, #744, #746, #787, #796, #803, #818,
  #826, #838, #856, #873, #875, #876, #877, #879, #880, #881, #883,
  #886, #887, #888, #892, #894, #901, #910, #913, #924, #926, #931,
  #933, #937, #939, #946, #948, #953, #956, #958, and #969.

# 2.9.1

## Language changes

* The type of `generate` which is used for `a@i` sequence definitions,
   is generalized so that the index type can be any `Integral` type
   large enough to index the entire array being defined.

## Bug Fixes

* Closed issues #848, #850, #851, #859, and #861.

* Fixed Windows installer paths.

# 2.9.0

## Language changes

* Removed the `Arith` class. Replaced it instead with more specialized
  numeric classes: `Ring`, `Integral`, `Field`, and `Round`.  `Ring`
  is the closest analogue to the old `Arith` class; it contains the
  `fromInteger`, `(+)`, `(*)`, `(-)` and `negate` methods.  `Ring`
  contains all the base arithmetic types in Cryptol, and lifts
  pointwise over tuples, sequences and functions, just as `Arith` did.

  The new `Integral` class now contains the integer division and
  modulus methods (`(/)` and `(%)`), and the sequence indexing,
  sequence update and shifting operations are generalized over
  `Integral`.  The `toInteger` operation is also generalized over this
  class.  `Integral` contains the bitvector types and `Integer`.

  The new `Field` class contains types representing mathematical
  fields (or types that are approximately fields). It is currently
  inhabited by the new `Rational` type, and the `Float`
  family of types.  It will eventually also contain the
  `Real` type. It has the operation `recip` for reciprocal
  and `(/.)` for field division (not to be confused for `(/)`,
  which is Euclidean integral division).

  There is also a new `Round` class for types that can sensibly be
  rounded to integers.  This class has the methods `floor`, `ceiling`,
  `trunc`, `roundToEven` and `roundAway` for performing different
  kinds of integer rounding.  `Rational` and `Float` inhabit `Round`.

  The type of `(^^)` is modified to be
  `{a, e} (Ring a, Integral e) => a -> e -> a`. This makes it clear
  that the semantics are iterated multiplication, which makes sense
  in any ring.

  Finally, the `lg2`, `(/$)` and `(%$)` methods of `Arith` have
  had their types specialized so they operate only on bitvectors.

* Added an `Eq` class, and moved the equality operations
  from `Cmp` into `Eq`. The `Z` type becomes a member of `Eq`
  but not `Cmp`.

* Added a base `Rational` type.  It is implemented as a pair of
  integers, quotiented in the usual way.  As such, it reduces to the
  theory of integers and requires no new solver support (beyond
  nonlinear integer arithmetic).  `Rational` inhabits the new
  `Field` and `Round` classes.  Rational values can be
  constructed using the `ratio` function, or via `fromInteger`.

* The `generate` function (and thus `x @ i= e` definitions) has had
  its type specialized so the index type is always `Integer`.

* The new typeclasses are arranged into a class hierarchy, and the
  typechecker will use that information to infer superclass instances
  from subclasses.

* Added a family of base types, `Float e p`, for working with
  floating point numbers.  The parameters control the precision of
  the numbers, with `e` being the number of bits to use in the exponent
  and `p-1` being the number of bits to use in the mantissa.
  The `Float` family of types may be used through the usual overloaded
  functionality in Cryptol, and there is a new built-in module called
  `Float`, which contains functionality specific to floating point numbers.

* Add a way to write fractional literals in base 2,8,10, and 16.
  Fractional literals are overloaded, and may be used for different types
  (currently `Rational` and the `Float` family).  Fractional literal in base
  2,8,and 16 must be precise, and will be rejected statically if they cannot be
  represented exactly.  Fractional literals in base 10 are rounded to the
  nearest even representable number.

* Changes to the defaulting algorithm. The new algorithm only applies
  to constraints arising from literals (i.e., `Literal` and `FLiteral`
  constraints).  The guiding principle is that we now default these
  to one of the infinite precision types `Integer` or `Rational`.
  `Literal` constraints are defaulted to `Integer`, unless the corresponding
  type also has `Field` constraint, in which case we use `Rational`.
  Fractional literal constraints are always defaulted to `Rational.

## New features

* Document the behavior of lifted selectors.

* Added support for symbolic simulation via the `What4` library
  in addition to the previous method based on `SBV`. The What4
  symbolic simulator is used when selecting solvers with the `w4`
  prefix, such as `w4-z3`, `w4-cvc4`, `w4-yices`, etc.
  The `SBV` and `What4` libraries make different tradeoffs in how
  they represent formulae. You may find one works better than another
  for the same problem, even with the same solver.

* More detailed information about the status of various symbols
  in the output of the `:browse` command (issue #688).

* The `:safe` command will attempt to prove that a given Cryptol
  term is safe; in other words, that it will not encounter a run-time
  error for all inputs. Run-time errors arise from things like
  division-by-zero, index-out-of-bounds situations and
  explicit calls to `error` or `assert`.

* The `:prove` and `:sat` commands now incorporate safety predicates
  by default. In a `:sat` call, models will only be found that do not
  cause run-time errors. For `:prove` calls, the safety conditions are
  added as additional proof goals.  The prior behavior
  (which ignored safety conditions) can be restored using
  `:set ignore-safety = on`.

* Improvements to the `any` prover. It will now shut down external
  prover processes correctly when one finds a solution. It will also
  wait for the first _successful_ result to be returned from a prover,
  instead of failing as soon as one prover fails.

* An experimental `parmap` primitive that applies a function to a
  sequence of arguments and computes the results in parallel.  This
  operation should be considered experimental and may significantly
  change or disappear in the future, and could possibly uncover
  unknown race conditions in the interpreter.

## Bug fixes

* Closed issues #346, #444, #614, #617, #636, #660, #662, #663, #664,
  #667, #670, #702, #711, #712, #716, #723, #725, #731, #835, #836,
  #839, #840, and #845

# 2.8.0 (September 4, 2019)

## New features

* Added support for indexing on the left-hand sides of declarations,
  record field constructors, and record updaters (issue #577). This
  builds on a new primitive function called `generate`, where the new
  syntax `x @ i = e` is sugar for `x = generate (\i -> e)`.

* Added support for element type ascriptions on sequence enumerations.
  The syntax `[a,b..c:t]` indicates that the elements should be of type
  `t`.

* Added support for wildcards in sequence enumerations. For example, the
  syntax `[1 .. _] : [3][8]` yields `[0x01, 0x02, 0x03]`. It can also be
  used polymorphically. For example, the most general type of `[1 .. _]`
  is `{n, a} (n >= 1, Literal n a, fin n) => [n]a`

* Changed the syntax of type signatures to allow multiple constraint
  arrows in type schemas (issue #599). The following are now equivalent:

        f : {a} (fin a, a >= 1) => [a] -> [a]

        f : {a} (fin a) => (a >= 1) => [a] -> [a]

* Added a mechanism for user-defined type constraint operators, and use
  this to define the new type constraint synonyms (<) and (>) (issues
  #400, #618).

* Added support for primitive type declarations. The prelude now uses
  this mechanism to declare all of the basic types.

* Added support for Haskell-style "block arguments", reducing the need
  for parentheses in some cases. For example, `generate (\i -> i +1)`
  can now be written `generate \i -> i + 1`.

* Improved shadowing errors (part of the fix for issue #569).

## Bug fixes

* Closed many issues, including #265, #367, #437, #508, #522, #549,
  #557, #559, #569, #578, #590, #595, #596, #601, #607, #608, #610,
  #615, #621, and #636.

# 2.7.0 (April 30, 2019)

## New features

* Added syntax for record updates (see #399 for details of implemented
and planned features).

* Updated the `:browse` command to list module parameters (issue #586).

* Added support for test vector creation (the `:dumptests` command).
This feature computes a list of random inputs and outputs for the
given expression of function type and saves it to a file. This is
useful for generating tests from a trusted Cryptol specification to
apply to an implementation written in another language.

## Breaking changes

* Removed the `[x..]` construct from the language (issue #574). It
was shorthand for `[x..2^^n-1]` for a bit vector of size `n`, which was
often not what the user intended. Users should instead write either
`[x..y]` or `[x...]`, to construct a smaller range or a lazy sequence,
respectively.

* Renamed the value-level `width` function to `length`, and generalized
its type (issue #550). It does not behave identically to the
type-level `width` operator, which led to confusion. The name
`length` matches more closely with similar functions in other
languages.

## Bug fixes

* Improved type checking performance of decimal literals.

* Improved type checking of `/^` and `%^` (issues #581, #582).

* Improved performance of sequence updates with the `update` primitive
(issue #579).

* Fixed elapsed time printed by `:prove` and `:sat` (issue #572).

* Fixed SMT-Lib formulas generated for right shifts (issue #566).

* Fixed crash when importing non-parameterized modules with the
backtick prefix (issue #565).

* Improved performance of symbolic execution for `Z n` (issue #554).

* Fixed interpretation of the `satNum` option so finding multiple
solutions doesn't run forever (issue #553).

* Improved type checking of the `length` function (issue #548).

* Improved error message when trying to prove properties in
parameterized modules (issue #545).

* Stopped warning about defaulting at the REPL when `warnDefaulting` is
set to `false` (issue #543).

* Fixed builds on non-x86 architectures (issue #542).

* Made browsing of interactively-bound identifiers work better (issue #538).

* Fixed a bug that allowed changing the semantics of the `_ # _`
pattern and the `-` and `~` operators by creating local definitions
of functions that they expand to (issue #568).

* Closed issues #498, #547, #551, #562, and #563.

repository: mbenelli/cryptol

repo_name: mbenelli/cryptol


text:
# European-Option-Pricing
Collection of functions for pricing european options

The R functions contained in this repository performs the following tasks:
- Compute the payoff of european call option with short position
- Compute the payoff of a european put option in a single-period binomial tree
- Compute the payoff of a call option using put-call parity
- Verify that the european call option satisfies Merton's constraints
- Compute the payoff of a european put option in a multi-period binomial tree using backward induction
- Compute the payoff of a put option in a multi-period setting using a direct formula
- Examine the behaviour of the payoff functions with respect to the price of the underlying asset

repository: vettorefburana/European-Option-Pricing

repo_name: vettorefburana/European-Option-Pricing


text:
[![Netlify Status](https://api.netlify.com/api/v1/badges/9af15de0-f3f9-4945-8a28-bf41b0330bd1/deploy-status)](https://app.netlify.com/sites/eloquent-gates-1aa469/deploys)
[![Contributors][contributors-shield]][contributors-url]
[![Forks][forks-shield]][forks-url]
[![Stargazers][stars-shield]][stars-url]
[![Issues][issues-shield]][issues-url]
[![MIT License][license-shield]][license-url]
[![LinkedIn][linkedin-shield]][linkedin-url]

µGames platform

    Intuitive and modern platform with a variety of games for all ages.  TABLE OF CONTENTS -->
## Table of Contents

* [About the Project](#about-the-project)
* [Built With](#built-with)
* [Getting Started](#getting-started)
  * [Prerequisites](#prerequisites)
  * [Installation](#installation)
* [Usage](#usage)
* [Roadmap](#roadmap)
* [Contributing](#contributing)
* [License](#license)
* [Contact](#contact)

## About The Project

[![Product Name Screen Shot][product-screenshot]](https://example.com)

On the screenshot above we have the homepage of **µGames platform**. You can see the full catalog of games with some important information of each one such as **title**, **categories**, **brief description** and **start button** which routes us into the game.

The app is also fully responsive for **Desktop**, **Mobile** and **Tablet**.

### Filter by Title

### Filter by description

## Games Catalog

## Hangman

## Memory

### Built With

* [ReactJS]()
* [Bootstrap]()
* [Jest]()
* [TypeScript]()

## Getting Started with µGames platform

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

### Available Scripts

In the project directory, you can run:

#### `npm  run start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

#### `npm run test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

#### `npm run build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).

### Prerequisites

* npm

### Installation

1. Clone the micro-games-platform
```sh
git clone https://github.com/victorgreco/micro-games-platform.git
```
2. Install NPM packages
```sh
npm install
```
3. Build NPM packages
```sh
npm run build
```
4. Start localhost
```sh
npm run start
```

## Roadmap

See the [open issues](https://github.com/victorgreco/micro-games-platform/issues) for a list of proposed features (and known issues).

## Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are **greatly appreciated**.

1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3.  Push to the Branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request

## License

Distributed under the MIT License. See `LICENSE` for more information.

## Contact

Victor Greco - [linkedin](https://www.linkedin.com/in/victor-greco/) -<EMAIL_ADDRESS>
Project Link: [https://github.com/victorgreco/micro-games-platform](https://github.com/victorgreco/micro-games-platform)

[contributors-shield]: https://img.shields.io/github/contributors/victorgreco/micro-games-platform.svg?style=flat-square
[contributors-url]: https://github.com/victorgreco/micro-games-platform/graphs/contributors
[forks-shield]: https://img.shields.io/github/forks/victorgreco/micro-games-platform.svg?style=flat-square
[forks-url]: https://github.com/victorgreco/micro-games-platform/network/members
[stars-shield]: https://img.shields.io/github/stars/victorgreco/micro-games-platform.svg?style=flat-square
[stars-url]: https://github.com/victorgreco/micro-games-platform/stargazers
[issues-shield]: https://img.shields.io/github/issues/victorgreco/micro-games-platform.svg?style=flat-square
[issues-url]: https://github.com/victorgreco/micro-games-platform/issues
[license-shield]: https://img.shields.io/github/license/victorgreco/micro-games-platform.svg?style=flat-square
[license-url]: https://github.com/victorgreco/micro-games-platform/blob/master/LICENSE.txt
[linkedin-shield]: https://img.shields.io/badge/-LinkedIn-black.svg?style=flat-square&logo=linkedin&colorB=555
[linkedin-url]: https://www.linkedin.com/in/victor-greco/
[product-screenshot]: src/resources/docs/home/home_desktop.png

repository: VictorGreco/micro-games-platform

gha_language: TypeScript

repo_name: VictorGreco/micro-games-platform


text:
# SVERE CORE

Adapters for svere core.

English | [简体中文](https://github.com/FE-PIRL/svere/blob/master/packages/core/README_ZH.md)

---

- [Intro](#intro)
- [Install](#install)
- [Usage](#usage)
- [Examples](#examples)
    - [React](#react)
    - [Vue2](#vue2)
    - [Vue3](#vue3)
- [Cli](#cli)
- [Todos](#todos)

# Intro

Managing support for libraries that provide UI components across frameworks is a pain,
especially when [Web Component](https://developer.mozilla.org/en-US/docs/Web/Web_Components) are not an option (e.g. for server side rendering, best performance, etc).

At present, the [svelte](https://svelte.dev/) framework is developing rapidly.
It is a good backward compatibility solution to make svelte components run in the old `react` or `vue` project,
especially when the team's technology stack is not unified, this provides an idea of cross-framework sharing component.

`Svere` contains several `adapters` for `React/Vue2/Vue3` which allows you to pass props and respond to events in a way that makes sense for that library.
Also, it provides a [cli](https://github.com/FE-PIRL/svere/blob/master/packages/cli/README.md) to quickly create svelte components that can be shared across components.

# Install

With [npm](https://www.npmjs.com/):

```bash
npm install @svere/core
```

Or with [yarn](https://yarnpkg.com/lang/en/):

```bash
yarn add @svere/core
```
# Usage

The core of svere exposes several adapter functions, namely `toReact`, `toVue` and `toVue3`.
Each adapter is a simple function that takes a svelte component and a few options and returns a Vue or React component that can be used in Vue templates or JSX as you would expect.

All adapters have the same signature as below, eg:
```ts
toReact(Component: SvelteComponent, wrapperProps?: WrapperProps) : Component
```
- `Component` should be a compiled svelte component, either precompiled or compiled as part of your build step using rollup-plugin-svelte for rollup or svelte-loader from webpack.
- `wrapperProps` (optional) should be an object contains wrapper `element`, `id`, `className` and `styles`.
   - `element` : all component have a base wrapper element, by default this is a `<div>` but you can pass in a string to customise this behaviour (eg: 'span', 'li', etc.)
   - `id` : add an id attribute to the base wrapper element, by default this is `svelte-wrapper`.
   - `className` : add a class attribute to the base wrapper element which you can define styles in your css files.
   - `styles` : add an inline styles attribute to the base wrapper element which can override the `className` attribute.

# Examples

In the examples below, the [svelte component](https://github.com/FE-PIRL/svere/blob/master/examples/src/Component.svelte) we will be using is a simple component that accepts a prop that will be rendered and emits an event upon clicking a button.
Bundle it to a single file with `umd` format, then it will be imported by other framework  conveniently.

```sveltehtml
<script lang="ts">
  import { createEventDispatcher } from 'svelte';
  const dispatch = createEventDispatcher();
  export let name: string;

  let count = 0;

  function handleChangeCount(event) {
    count += 1;
    dispatch('someEvent', count);
  }
  function handleChangeName() {
    name = 'boss';
  }
</script>

<main>
  <h1>Hello {name}, welcome!</h1>
  <button on:click={handleChangeCount}>
    add count: {count}
  </button>
  <button on:click={handleChangeName}>
    update name: {name}
  </button>
</main>

<style>
  main {
    text-align: center;
    padding: 1em;
    max-width: 240px;
    margin: 0 auto;
  }

  h1 {
    color: #ff3e00;
    text-transform: uppercase;
    font-size: 4em;
    font-weight: 100;
  }
</style>
```

## React

```jsx
import React, { useState } from "react";
import SvelteComponent from "./svelte-component";
import toReact from<EMAIL_ADDRESS>
const wrapperProps = {
  element: "section",
  className: "section-css",
  id: "svelte-react",
  styles: {
    border: "1px solid gray",
  },
};
const ReactComponent = toReact(SvelteComponent, wrapperProps);

const App = () => {
  const [name, setName] = useState('ben');
  const changeName = () => setName(n => {
    return name === 'ben' ? 'yasin' : 'ben'
  });

  const handleEventCallback = (e) => {
    console.log(e.detail)
  };

  const handleWatchCallback = (name) => {
    console.log(name)
  };

  return (
    <div>
      <ReactComponent
          name={name}
          onSomeEvent={handleEventCallback}
          watchName={handleWatchCallback}
      />

      <br/>

      <button onClick={changeName}> change inner variable name </button>
    </div>
  );
};
```

## Vue2

```vue
<template>
  <div>
    <VueComponent
      :name="name"
      @someEvent="handleEventCallback"
      @watch:name="handleWatchCallback"
    />
    <button @click="changeName">change inner variable name</button>
  </div>
</template>

<script>
import SvelteComponent from "./svelte-component";
import toVue from<EMAIL_ADDRESS>
export default {
  components: {
    VueComponent: toVue(SvelteComponent)
  },
  data() {
    return {
      name: 'ben'
    };
  },
  methods: {
    changeName() {
       this.name = this.name === 'ben' ? 'yasin' : 'ben'
    },
    handleEventCallback(e){
      console.log(e.detail)
    },
    handleWatchCallback(name){
      console.log(name)
    }
  }
};
</script>
```

## Vue3

```vue
<template>
  <VueComponent
          :name="name"
          @someEvent="handleEventCallback"
          @watch:name="handleWatchCallback"
  />
  <br/>
  <button @click="changeName">change inner variable name</button>
</template>

<script>
import {ref} from 'vue'
import SvelteComponent from "./svelte-component";
import toVue3 from<EMAIL_ADDRESS>const wrapperProps = {
  element: "section",
  className: "section-css",
  id: "svelte-react",
  styles: {
    border: "1px solid gray",
  },
};
export default {
  name: 'App',
  components: {
    VueComponent: toVue3(SvelteComponent,wrapperProps)
  },
  setup() {
    const name = ref('ben')
    const changeName = () => {
      name.value = name.value === 'ben' ? 'yasin' : 'ben'
    }
    const handleEventCallback = (e)=>{
      console.log(e.detail)
    }
    const handleWatchCallback = (name)=>{
      console.log(name)
    }
    return {
      name,
      changeName,
      handleEventCallback,
      handleWatchCallback
    }
  }
}
</script>

<style>
body {
  text-align: center;
}
</style>
```

# Cli
Try svere out locally with our [CLI](https://github.com/FE-PIRL/svere/tree/master/packages/cli)

With [npm](https://www.npmjs.com/):

```bash
npm install @svere/cli
```

Or with [yarn](https://yarnpkg.com/lang/en/):

```bash
yarn add @svere/cli
```

# Todos

- develop core to add more features, eg: sub-component, slots.


text:
# OpenFF QCArchive Dataset Submission

## Dataset Lifecycle

All datasets submitted to QCArchive via this repository conform to the [Dataset Lifecycle](./LIFECYCLE.md).

See [STANDARDS.md](./STANDARDS.md) for submission standards.
Datasets must be submitted as pull requests.

## Dataset Priority

This section contains a relative ranking of dataset priority.

While queueing is still handled manually, *this* is the single place where priority is determined.

New datasets that are added should be included in this list if they are to be submitted.

Do not modify this directly in master -- Always open a PR and get at least one approving review before merging.

* ~Roche hessians~
* ~Coverage hessians~
* ~Chaya's Biphenyl set~
* ~Boron~
* 06-28-19-Nitrogen-grid-optimization
* Everything else

Look into Roche torsion set to investigate/fix failures.

# qca-dataset-submission
Data generation and submission scripts for the QCArchive ecosystem.

## `TorsionDriveDataset`
* `2019-06-03-Torsion-Stability-Benchmark`: source files for `Fragment Stability Benchmark` (`TorsionDriveDataset`) covering molecular fragments of varying size around a central torsion (@ChayaSt)
* `2019-07-25-phenyl-set`: source files for `phenyl set`
* `2019-09-07-Pfizer-discrepancy-torsion-dataset-1`: source files for `Pfizer discrepancy torsion dataset 1`

## `OptimizationDataset`
* `2019-06-25-smirnoff99Frost-coverage`: source files for `smirnoff99Frost parameter coverage` (`OptimizationDataset`) providing minimal coverage of SMIRNOFF valence parameters (@ChayaSt)
* `2019-07-02 VEHICLe optimization dataset`: source files for `Open Force Field VEHICLe optimization dataset 1.0.0` (`OptimizationDataset`) for the VEHICLe dataset (heteraromatic rings of the future) (@jchodera)
* `2019-07-05 OpenFF NCI250K Boron 1`: source files for `OpenMM NCI250K Boron 1` (`OptimizationDataset`) where small boron-containing compounds are extracted from the [NCI250K](https://cactus.nci.nih.gov/download/nci/) (@jchodera)
* `2019-09-07-Pfizer-discrepancy-optimization-dataset-1`: source files for `Pfizer discrepancy optimization dataset 1` (@jchodera)

repository: hyejang/qca-dataset-submission

repo_name: hyejang/qca-dataset-submission


text:
# ***
Dungeons and Dragons Character Creator Express
***

![image of app](public/assets/images/homepage-Img.png)
![image of app](public/assets/images/login-Img.png)

## Visit the Webpage
 [Dungeons and Dragons Character Creator Express](http://dnd-exp.herokuapp.com/login)

## Table of Contents

* [Purpose](#Purpose)

* [Features](#Features)

* [Technologies](#Technologies)

* [Instructions](#Instructions)

* [Contributors](#Contributors)

* [License](#License)

## Purpose
Have you ever needed to make a Dungeons and Dragons character on the fly? Well look no further! Making a new character to play with can take quite a bit of time and who has time to waste when you just want to play. This app allows users to easily create new characters fast with generated stats that would meet all the criteria needed to start or jump into a campaign!

## Features

![image of app](public/images/characterStats.png)
Once you have selected the proper fields to create your character an easy to read and understand stat page is generated. Hovering over a certain stat/trait will generate a small text box describing the individual stat or trait. This makes for easy understanding to even the most beginner player.

![image of app](public/images/characters.png)
Want to create more than one character? Not a problem! An easy to view page allows the user to see all the characters they have created. A simple click will send you right to that characters stats page.

## Technologies
* [Node.js](https://nodejs.org/en/)
* [Express.js](https://expressjs.com/)
* [Axios](https://www.npmjs.com/package/axios)
* [ESlint](https://eslint.org/)
* [Bcrypt](https://www.npmjs.com/package/bcrypt)
* [Dotenv](https://www.npmjs.com/package/dotenv)
* [Multiple.js](https://multiple.js.org/)
* [Handlebars](https://handlebarsjs.com/)
* [BootStrap](https://getbootstrap.com/)
* [Font Awesome](https://fontawesome.com/)
* [PostgresSQL](https://www.postgresql.org/)
* [Sequelize](https://sequelize.org/)

## Instructions
1. Register for an account or sign in to an existing account.
2. Simply click Create Character.
3. Select a race, class and enter in a characters name then click generate.
4. View your characters stats and traits.
5. View previously made characters by clicking "My Characters" located in the navigation bar at the top of the page.
6. Dont leave your account running for everyone to see and make sure to logout.

## Contributors
* [Tim Vigneau](https://github.com/tjvig94)
* [Chad Courtney](https://github.com/chadcourtney9)
* [Tom Fallon](https://github.com/TomFallon9)
* [Patrick DeMarco](https://github.com/pfdemarco)
* [Joe Lyons](https://github.com/Josephjlyons)

## Licencse

MIT License

Copyright (c) [2021]

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

gha_language: JavaScript


text:
---
date: 2014/03/05 00:00:00 +05:30
title: Save The Hacker
layout: post
disqus: true
tags:
  - product reviews
  - sentiment analysis
categories:
  - project
  - hackathon
thumbnail: banner/save-the-hacker.png
---

**Sentiment analysis on product reviews** is our idea for "Save the Hacker" hackathon. Our basic goals were to

* Scrap product reviews across various e-commerce websites and do sentiment analysis classify them under positive, negative and neutral categories.
* Extract various features of the product from the reviews and do sentiment analysis on them.
* Date wise analysis of the product from common data source like Twitter

**Outcome?**

* Goal 1 will help to capture the overall sentiment about the product and the corresponding e-commerce website's performance. For example, one may provide better delivery and the other may provide better customer service etc. This metric will help you to get an idea of where should we buy the product from not considering only the price as a factor.
* Goal 2 will help to know about the product's features from customer provided reviews across these e-commerce sites.
* Goal 3 will help you identify the improvement in products over iterations. For example, PS4 had lot of complaints on the release day but after next set of consoles got released the complaints got reduced. So, this metric will help to get an idea about how the product's quality varies over a period of time.

For the hackathon, we chose to proceed only with

* Flikart and Amazon as the target e-commerce websites
* Mobile as the targeted product
* Twitter tweets as the source for day by day analysis of the product

And **Panda**(we felt that Pandas are cool, so named it Panda) came to life in the next 30 hours

![Main page](http://i.imgur.com/zUbNOSw.png)

The entire first time process of scrapping all the reviews from Amazon and Flipkart, doing sentiment analysis on them was time consuming process. So we chose only two products *Galaxy Note 3* and *Nokia Lumia 1520* for the demo.

![Analysis1](http://i.imgur.com/92wlCJF.png)

This is the comparison of sentiment analysis of customer reviews on Amazon and Flipkart. We also done sentiment analysis on tweets regarding this product. The twitter data only captures the sentiment on products.

![Analysis2](http://i.imgur.com/By5B6j2.png)

We considered battery, display, RAM and storage as static features that will be analyzed. These are based on reviews from Amazon, Flipkart and tweets that spoke about these features.

![Analysis3](http://i.imgur.com/ZNX4Pqt.png)

This is the day by day analysis based on tweets


text:
# Agaricus polygrammus Bull., 1789 SPECIES

#### Status
SYNONYM

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
Herb. Fr. 9: tab. 395 (1789)

#### Original name
Agaricus polygrammus Bull., 1789

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Basidiomycota/Agaricomycetes/Agaricales/Mycenaceae/Mycena/Mycena polygramma/ Syn. Agaricus polygrammus/README.md

repo_name: mdoering/backbone


text:
# FHIR.js
Node.JS library for DSTU1, DSTU2 and STU3, for serializing/deserializing FHIR resources between JS/JSON and XML using various node.js XML libraries, and for basic validation.

[![Build Status](https://ci.appveyor.com/api/projects/status/nt0h6ufvhdvk7obc/branch/master?svg=true)](https://ci.appveyor.com/project/seanmcilvenna/fhir-js)

# Dependencies
* q 1.4.1
* xml2js 0.4.9
* xmlbuilder 2.6.4
* libxmljs 0.18.0
* lodash 3.10.1
* path 0.12.7

# Installation
```
npm install fhir
```

# Test
```
npm test
```

# Documentation
API documentation can be found at http://lantanagroup.github.io/FHIR.js/

# Implementation Notes
* FHIR STU3 is updated with the latest published profiles and schemas
* Feeds and resources are both supported for DSTU1. There is no need to do anything different for converting feeds vs. resources. The library will automatically detect what should be produced based on the resourceType of the JS object passed, or based on the root element of the XML.
* libxmljs is used to validate XML against the FHIR schemas
* xml2js is used to parse XML and create JS
* xmlbuilder is used to create XML from JS
* FHIR profiles (within the "profiles" directory) are used to determine whether properties should be arrays. The profiles are loaded into memory whenever an instance of the FHIR module is created. This could be improved to reduce I/O operations...
  * As part of publishing, all FHIR JSON profiles are merged together into a single array that is used by require() within FHIR.js