Students learn about various crystals, such as kidney stones, within the human body. They also learn about how crystals grow and ways to inhibit their growth. They also learn how researchers such as chemical engineers design drugs with the intent to inhibit crystal growth for medical treatment purposes and the factors they face when attempting to implement their designs. A day before presenting this lesson to students, conduct the associated activity, Rock Candy Your Body.

Students use a tension-compression machine (or an alternative bone-breaking setup) to see how different bones fracture differently and with different amounts of force, depending on their body locations. Teams determine bone mass and volume, calculate bone density, and predict fracture force. Then they each test a small animal bone (chicken, turkey, cat) to failure, examining the break to analyze the fracture type. Groups conduct research about biomedical challenges, materials and repair methods, and design repair treatment plans specific to their bones and fracture types, presenting their design recommendations to the class.

A two-day introduction to modern evidence-based teaching practices, built and maintained by the Carpentry community.

Software Carpentry lección para control de versiones con Git Para ilustrar el poder de Git y GitHub, usaremos la siguiente historia como un ejemplo motivador a través de esta lección. El Hombre Lobo y Drácula han sido contratados por Universal Missions para investigar si es posible enviar su próximo explorador planetario a Marte. Ellos quieren poder trabajar al mismo tiempo en los planes, pero ya han experimentado ciertos problemas anteriormente al hacer algo similar. Si se rotan por turnos entonces cada uno gastará mucho tiempo esperando a que el otro termine, pero si trabajan en sus propias copias e intercambian los cambios por email, las cosas se perderán, se sobreescribirán o se duplicarán. Un colega sugiere utilizar control de versiones para lidiar con el trabajo. El control de versiones es mejor que el intercambio de ficheros por email: Nada se pierde una vez que se incluye bajo control de versiones, a no ser que se haga un esfuerzo sustancial. Como se van guardando todas las versiones precedentes de los ficheros, siempre es posible volver atrás en el tiempo y ver exactamente quién escribió qué en un día en particular, o qué versión de un programa fue utilizada para generar un conjunto de resultados en particular. Como se tienen estos registros de quién hizo qué y en qué momento, es posible saber a quién preguntar si se tiene una pregunta en un momento posterior y, si es necesario, revertir el contenido a una versión anterior, de forma similar a como funciona el comando “deshacer” de los editores de texto. Cuando varias personas colaboran en el mismo proyecto, es posible pasar por alto o sobreescribir de manera accidental los cambios hechos por otra persona. El sistema de control de versiones notifica automáticamente a los usuarios cada vez que hay un conflicto entre el trabajo de una persona y la otra. Los equipos no son los únicos que se benefician del control de versiones: los investigadores independientes se pueden beneficiar en gran medida. Mantener un registro de qué ha cambiado, cuándo y por qué es extremadamente útil para todos los investigadores si alguna vez necesitan retomar el proyecto en un momento posterior (e.g. un año después, cuando se ha desvanecido el recuerdo de los detalles).

Students learn how forces affect the human skeletal system through fractures and why certain bones are more likely to break than others depending on their design and use in the body. They learn how engineers and doctors collaborate to design effective treatments with consideration for the location, fracture severity and patient age, as well as the use of biocompatible materials. Learning the lesson content prepares students for the associated activity in which they test small animal bones to failure and then design treatment repair plans.

Students are challenged to think as biomedical engineers and brainstorm ways to administer medication to a patient who is unable to swallow. They learn about the advantages and disadvantages of current drug delivery methods—oral, injection, topical, inhalation and suppository—and pharmaceutical design considerations, including toxicity, efficacy, size, solubility/bioavailability and drug release duration. They apply their prior knowledge about human anatomy, the circulatory system, polymers, crystals and stoichiometry to real-world biomedical applications. A Microsoft® PowerPoint® presentation and worksheets are provided. This lesson prepares students for the associated activity in which they create and test large-size drug encapsulation prototypes to provide the desired delayed release and duration timing.

Students learn how crystallization and inhibition occur by examining calcium oxalate crystals with and without inhibitors that are capable of altering crystallization. Kidney stones are composed of calcium oxalate crystals, and engineers and doctors experiment with these crystals to determine how growth is affected when a potential drug is introduced. Students play the role of engineers by trying to determine which inhibitor would be the best for blocking crystallization.

Students are introduced to prosthetics history, purpose and benefits, main components, main types, materials, control methods, modern examples including modern materials used to make replacement body parts and the engineering design considerations to develop prostheses. They learn how engineers and medical doctors work together to improve the lives of people with amputations and the challenges faced when designing new prostheses with functional and cosmetic criteria and constraints. A PowerPoint(TM) presentation and two worksheets are provided.

This lesson is part of Software Carpentry workshops and teach an introduction to plotting and programming using python. This lesson is an introduction to programming in Python for people with little or no previous programming experience. It uses plotting as its motivating example, and is designed to be used in both Data Carpentry and Software Carpentry workshops. This lesson references JupyterLab, but can be taught using a regular Python interpreter as well. Please note that this lesson uses Python 3 rather than Python 2.

This lesson in part of Software Carpentry workshop and teach novice programmers to write modular code and best practices for using R for data analysis. an introduction to R for non-programmers using gapminder data The goal of this lesson is to teach novice programmers to write modular code and best practices for using R for data analysis. R is commonly used in many scientific disciplines for statistical analysis and its array of third-party packages. We find that many scientists who come to Software Carpentry workshops use R and want to learn more. The emphasis of these materials is to give attendees a strong foundation in the fundamentals of R, and to teach best practices for scientific computing: breaking down analyses into modular units, task automation, and encapsulation. Note that this workshop will focus on teaching the fundamentals of the programming language R, and will not teach statistical analysis. The lesson contains more material than can be taught in a day. The instructor notes page has some suggested lesson plans suitable for a one or half day workshop. A variety of third party packages are used throughout this workshop. These are not necessarily the best, nor are they comprehensive, but they are packages we find useful, and have been chosen primarily for their usability.

Students see and learn how crystallization and inhibition occur by making sugar crystals with and without additives in a supersaturation solution, testing to see how the additives may alter crystallization, such as by improving crystal growth by more or larger crystals. After three days, students analyze the differences between the control crystals and those grown with additives, researching and attempting to deduce why certain additives blocked crystallization, showed no change or improved growth. Students relate what they learn from the rock candy experimentation to engineering drug researchers who design medicines for targeted purposes in the human body. Conduct the first half of this activity one day before presenting the associated lesson, Body Full of Crystals. Then conduct the second half of the activity.

Students experience the engineering design process as they design, fabricate, test and redesign their own methods for encapsulation of a (hypothetical) new miracle drug. As if they are engineers, teams make large-size prototypes to test proof of concept. They use household materials (tape, paper towels, plastic wrap, weed-barrier fabric, glues, etc.) to attach a coating to a porous "shell" (a perforated plastic Wiffle® ball) containing the medicine (colored drink mix powder). The objective is to delay the drug release by a certain time and have a long release duration—patterned after the timed release requirements of many real-world pharmaceuticals that are released from a polymer shell via diffusion in the body. Guided by a worksheet, teams go through at least three design/test iterations, aiming to achieve a solution close to the target time release constraints.

Software Carpentry lesson on how to use the shell to navigate the filesystem and write simple loops and scripts. The Unix shell has been around longer than most of its users have been alive. It has survived so long because it’s a power tool that allows people to do complex things with just a few keystrokes. More importantly, it helps them combine existing programs in new ways and automate repetitive tasks so they aren’t typing the same things over and over again. Use of the shell is fundamental to using a wide range of other powerful tools and computing resources (including “high-performance computing” supercomputers). These lessons will start you on a path towards using these resources effectively.

Students experience the engineering design process as they design and construct lower-leg prostheses in response to a hypothetical zombie apocalypse scenario. Like the well-known Apollo 13 story during which engineers were challenged to fix the crippled spacecraft with limited supplies in order to save astronauts' lives, in this activity, students act as engineers during an imaginary disaster in which a group member's leg was amputated in order to survive a zombie attack. Building on what they learned and researched in the associated lesson, they design and fabricate a replacement prosthetic limb using given specific starting material and limited additional supplies, similar to how engineers design for individuals while working within constraints. A more-advanced scenario challenges students to design a prosthesis that is able to provide a more-specific movement function.