Giter VIP home page Giter VIP logo

paleosoc_phylo_short_course_2019's People

Contributors

daveyfwright avatar dwbapst avatar laurasoul avatar peterjwagner3 avatar rachelwarnock avatar wrightaprilm avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

paleosoc_phylo_short_course_2019's Issues

Need to add material on setting path, general RB setup

A good portion of the issues that came up in the workshop could have been solved with a more uniform approach to setting paths and how materials would be obtained by learners. We all had different ideas of how that would work, but we also all wanted to have the discussion at different times. What happened was a bit of mismatch / chaos. Much of the feedback as relates to workshop materials were on this:

@wrightaprilm has tried to approach those issues with a new rb module:

Deployed a new tutorial on setting up data and script directories and using built-in functions to view and set working directories in #RevBayes (https://revbayes.github.io/tutorials/tutorial_structure/). Feedback/edits/improvements very welcome on GitHub (https://github.com/revbayes/revbayes.github.io/tree/source/tutorials/tutorial_structure)!

https://revbayes.github.io/tutorials/tutorial_structure/

https://github.com/revbayes/revbayes.github.io/tree/source/tutorials/tutorial_structure

These materials should be evaluated and integrated as new module into the PS short course 2019 workshop structure for any future use of this workshop as an indep resource.

Need maybe more unified discussion of time issues - clock module, fbd module, new module?

Based on an older draft of @daveyfwright 's clock section, it seems that it might be a good idea, if dated trees get introduced there, to maybe have more focus on the uniform-interval versus point-occurrence issues there, FAD vs midpoint vs LAD, the placing of prior uncertainties on ages, and priors placed on node ages, particularly the root (and the importance, or not, of placing such root priors appropriately).

Alternatively, with range-FBD in the mix, maybe decide whether to discuss that as its own fourth 'piece' (a piece on the complexities of time data for OTUs, and assumptions put on roots).

As its own piece, this could get integrated with some @PeterJWagner3 thoughts on stratigraphic uncertainty and availability of material across their record.

Add who/where/how to report incidents to Expectations statement

Following off what @bomeara said here, on twitter:

https://twitter.com/omearabrian/status/1176840584423563265

Clear expectations, including info on an overall code of conduct, etc. good. The link to the paleontological society code is great, and has reporting info; might also include reporting info on your page so less digging is required.

Sounds like we just need to carry over reporting information as given in PS code - and then probably run it by PS again (if we imagine such a statement being used in later PS-sponsored events).

This probably sounds weird to put as an issue post-event, but I do kind of see our statement as the model of what a PS-sponsored event should have in terms of expectations statement.

Need to fix / add to / finalize FBD tutorial

Current FBD tutorial is pretty much an incomplete thing from @wrightaprilm and it's all my fault, since I decided to procrastinate and work on the main website, despite it really being my assigned module. The participants didn't notice, and my ability to lecture without slides during an exaggerated IT disaster helped hide my consistent inattention to my own responsibilities.

  • Need to add stuff (lots of context stuff)
  • Make sure it works (currently doesn't work, apparently)
  • Finalize materials

It's all kinda semi-urgent, in that way things that should have been done already but aren't done, and the time for them being done has passed, are, while also simultaneously not being urgent because its something no one is actually getting paid for.

Need to get more collaborators to add themselves to this repo

Currently, only April has accepted my invite to be able to commit to this repo. I wonder if annoyingly tagging them here with a copy/paste from the README will get them to accept my github invite...

(cough cough)

This hands-on computational workshop is organized by Sandra Carlson and Peter Wagner (@PeterJWagner3), instructors April Wright (@wrightaprilm), Laura Soul (@laurasoul), David "Davey" F. Wright (@daveyfwright), and David Bapst (@dwbapst), with instructional material development from Rachel Warnock (@rachelwarnock). Additionally, this course will utilize a number of 'roving' teaching assistants (tentative list, as follows: William Gearty (@willgearty), Lucy Chang (@lucymchang), ...).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.