We found 3 results that contain "html"

Triglycerides

Triglycerides are fats and oils
Fatty acid and glycerol molecules are the components that make up triglycerides
Fats and oils have a number of important functions in organisms: energy storage, insulation, buoyancy, and protection

 
 






 
Energy storage

The long hydrocarbon chains in triglycerides contain many carbon-hydrogen bonds with little oxygen (triglycerides are highly reduced)

So when triglycerides are oxidised during cellular respiration this causes these bonds to break releasing energy used to produce ATP

 

Triglycerides, therefore, store more energy per gram than carbohydrates and proteins (37kJ compared to 17kJ)
As triglycerides are hydrophobic they do not cause osmotic water uptake in cells so more can be stored

Plants store triglycerides, in the form of oils, in their seeds and fruits. If extracted from seeds and fruits these are generally liquid at room temperature due to the presence of double bonds which add kinks to the fatty acid chains altering their properties
Mammals store triglycerides as oil droplets in adipose tissue to help them survive when food is scarce (e.g. hibernating bears)

 

The oxidation of the carbon-hydrogen bonds releases large numbers of water molecules (metabolic water) during cellular respiration

Desert animals retain this water if there is no liquid water to drink
Bird and reptile embryos in their shells also use this water

 Teaching Commons: “an emergent conceptual space for exchange and community among faculty, students, and all others committed to learning as an essential activity of life in contemporary democratic society” (Huber and Hutchings, 2005, p.1) What Is the #iteachmsu Commons?    You teach MSU. We, the Academic Advancement Network, The Graduate School, and The Hub for Innovation in Learning and Technology, believe that a wide educator community (faculty, TAs, ULAs, instructional designers, academic advisors, et al.) makes learning happen across MSU. But, on such a large campus, it can be difficult to fully recognize and leverage this community’s teaching and learning innovations. To address this challenge, the #iteachmsu Commons provides an educator-driven space for sharing teaching resources, connecting across educator networks, and growing teaching practice. #iteachmsu Commons content may be discipline-specific or transdisciplinary, but will always be anchored in teaching competency areas. You will find blog posts, curated playlists, educator learning module pathways, and a campus-wide teaching and learning events calendar. We cultivate this commons across spaces. And through your engagement, we will continue to nurture a culture of teaching and learning across MSU and beyond. How Do I Contribute to the #iteachmsu Commons? Content is organized by posts, playlists and pathways.

Posts: Posts are shorter or longer-form blog postings about teaching practice(s), questions for the educator community, and/or upcoming teaching and learning events. With an MSU email address and free account signup, educators can immediately contribute blog posts and connected media (e.g. handouts, slide decks, class activity prompts, promotional materials). All educators at MSU are welcome to use and contribute to #iteachmsu. And there are no traditional editorial calendars. Suggested models of posts can be found here.
Playlists: Playlists are groupings of posts curated by individual educators and the #iteachmsu community. Playlists allow individual educators to tailor their development and community experiences based on teaching competency area, interest, and/or discipline.
Pathways: Pathways are groupings of educator learning modules curated by academic and support units for badges and other credentialing.

There are two ways to add your contribution to the space:

Contribute existing local resources for posts and pathways: Your unit, college, and/or department might already have educator development resources that could be of use to the wider MSU teaching and learning community. These could be existing blog posts on teaching practice, teaching webinars, and/or open educational resources (e.g classroom assessments, activities). This content will make up part of the posts, playlists, and pathways on this site. Educators can then curate these posts into playlists based on their individual interests. Please make sure to have permission to share this content on a central MSU web space.
Contribute new content for posts: A strength of the #iteachmsu Commons is that it immediately allows educators to share teaching resources, questions and events through posts to the entire community. Posts can take a variety of forms and are organized by teaching competency area categories, content tags, date, and popularity. Posts can be submitted by both individual educators and central units for immediate posting but must adhere to #iteachmsu Commons community guidelines. Posts could be:




About your teaching practice(s): You discuss and/or reflect on the practices you’re using in your teaching. In addition to talking about your ideas, successes, and challenges, we hope you also provide the teaching materials you used (sharing the assignment, slidedeck, rubric, etc.)
Responses to teaching ideas across the web or social media: You share your thoughts about teaching ideas they engage with from other media across the web (e.g. blog posts, social media posts, etc.).
Cross-posts from other teaching-related blogs that might be useful for the #iteachmsu community: You cross-post content from other teaching-related blogs they feel might be useful to the #iteachmsu community.
About teaching-related events: You share upcoming teaching related events as well as their thoughts about ideas they engage with events at MSU and beyond (e.g. workshops, conferences, etc.). If these events help you think in new ways about your practice, share them with the #iteachmsu community.
Questions for our community: You pose questions via posts to the larger community to get ideas for their practice and connect with others considering similar questions.



What Are the #iteachmsu Commons Policies?Part of the mission of the #iteachmsu Commons is to provide space for sharing, reflecting, and learning for all educators on our campus wherever they are in their teaching development. The commons is designed to encourage these types of interactions and reflect policies outlined by the MSU Faculty Senate.  We maintain the right to remove any post that violates guidelines as outlined here and by MSU. To maintain a useful and safer commons, we ask that you:

Follow the MSU Guidelines for Social Media.
Engage across the #iteachmsu commons in a civil and respectful manner. Content may be moderated in accordance with the MSU Guidelines for Social Media.
Do not share private or confidential information via shared content on the #iteachmsu Commons.

Content posted on the #iteachmsu Commons is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license. Learn more about this licensing here. Posted comments, images, etc. on the #iteachmsu Commons do not necessarily represent the views of Michigan State University or the #iteachmsu Commons Team. Links to external, non-#iteachmsu Commons content do not constitute official endorsement by, or necessarily represent the views of, the #iteachmsu Commons or Michigan State University. What if I Have #iteachmsu Commons Questions and/or Feedback?If you have any concerns about #iteachmsu Commons content, please email us at iteach@msu.edu. We welcome all feedback and thank you for your help in promoting a safer, vibrant and respectful community.  

JMeter is an open-source software designed for load testing and application performance measurement. It supports API testing in Java but was originally designed to test web applications.
Features:




This software supports HTTP/HTTPS, FTP, SOAP, REST, and other protocols to perform detailed testing across different application layers.
Command-line mode loads API tests from any OS.
Scripting is supported using Groovy and BeanShell languages to implement complex test logic and workflows in API performance tests.
Continuous integration is supported through third-party open-source libraries to catch API performance issues early.
Caching and replaying of API test results are supported.