Student teams are asked to design an autonomous and sustainable live-work environment for 3-5 people in one of Australia's three major climate zones as part of the Domus project. Over 9 weeks, students will analyze the climate zone, develop concepts, and design their proposal. Their final presentation will include orthographic projections, sections, a wall section, physical model, and documentation of their design process. Peer and self-evaluations will also be used to assess individual contributions to the team project.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
"Impact of front-end architecture on development cost", Viktor Turskyi
Domus brief
1. 2009 SRD 264
A+B: Deakin University School of Architecture and Building
Architecture 2B
SRD 264
Project 2: Domus (40%)
The second major 2B project is an exercise in collaborative architectural design and
requires team-work and representation at the level of orthographic architectural
projection and model making. In this project, student teams apply the knowledge and
learning of Minima to enhance design synthesis in Domus.
Domus: Design teams of three students (there will also be one team of four in each
tutorial group) are asked to demonstrate a new concept for a sustainable live-work
environment in one of the major climate zones of Australia. The three major climate
zones are hot-humid (tropical, Northern Australia), hot-dry (desert, Central Australia)
and temperate (Southern Australia). In Domus, students extend their Minima project to
design a shared live-work environment that can accommodate the three to four people
of their design team, plus one guest, in one of the three climate zones. Each house
must be fully autonomous – i.e. it cannot rely on power or water from the national grid,
for it may be that for lengthy periods there is no grid power or water. The project should
be approached through an understanding of the relationships between individual
(private) and collective (shared) spaces within a living environment. This understanding
is arrived at through the exploration of: the relationships between buildings and their
environment (landscape, climate and culture); the impact of energy (passive),
materiality and external site constraints (shadow, breeze, topography) from the
environment on making architectural space; and how notions of ordering,
organisational principles, repetition and composition shape architectural form making.
Task
Domus: Extend your minima project to design an autonomous and environmentally
sustainable shared live-work environment that can accommodate three to five people
in a specific climate zone.
Objectives
Understand the relationships between individual (private) and collective (shared)
spaces within a living environment;
Explore the relationships between buildings and their environment (landscape,
climate and culture);
2. Explore the impact of energy use (using passive systems), materiality and external
site constraints (shadow, breeze, topography) from the environment on making
architectural space;
Introduce the notions of ordering, organisational principles, repetition and composition
in architectural form making;
Requirements
Your client wishes to demonstrate a new concept for an autonomous environmentally
sustainable live-work environment in a major climate zone of Australia. Domus
requires that you respond to the climate zone assigned to your group.
Site Allocation
During Minima reviews, a sign-up sheet will be pinned up to allocate climate zones to
student teams.
Your project must address the local climate with an emphasis on environmental
sustainability and passive low-energy architecture. You are required to develop a
prototype for your climate zone. Specifically, your prototype must show how the
external physical environment (temperature, humidity, breeze, heating, cooling, light
and precipitation) can be addressed through architecture.
The live-work envelope must cater for two types of spaces, individual private spaces,
and shared collective spaces. Within these, you can define how a sleeping space,
study or work space, a living and dining space, and services (wet areas, food
preparation, storage) are allocated.
Process
Lectures each week will touch upon and/or clarify the objectives outlined above.
Articulate your concept of Domus following the weekly tutorial guidelines. Each week,
design teams must present thumbnails representing every weekly stage of their
design. The tutorial guidelines are as follows.
Week 5, Analysis of Climate and Site design
You will not be involved in tutorials this week because of teamwork workshops. But
outside of these workshops you should achieve the following prior to Week 8 tutorials.
Analyse your climate zone. What are the major environmental factors (sun, wind,
light, heating, cooling, materials, vegetation, precipitation, humidity)? How can you
respond to the challenges, constraints and opportunities presented by these
parameters? How can you expand your concept for one person to include five people
as well as the possibility of sharing functional spaces?
The site is a real one. It is located in a natural setting within the climate zone
allocated to your group. There are two constraints: First, the site is a rectangle, 12
metres wide x 36 meters long. Second, the long section of the site (36 metres) faces
North. Create a measured drawing (hard-line) of the site at 1:50 (plan and 2 sections)
for your climate zone. Make copies of the site drawings and distribute to all team
members.
Week 6, Concept development: The building envelope as a bio-climatic skin
Each team member must develop the abstraction, idea or concept of their minima into
a concept for a Domus plan & building envelope. The building envelope (floor, walls,
and roof) must respond to the specific climatic requirements of the site (designed
above). Explore your building envelope concept through sketches, drawings and
discussions with your tutorial groups and in consultation with your tutors. At the end
of this week, the team must be able to articulate their concepts for Domus as a plan
and bio-climatic skin.
Investigate dissection or sectioning as a tool for representing architectural ideas.
Cutting and slicing through space allows you to see "inside" and "in-between" objects.
Explore your concept of the Domus by creating massing models, dissections of the
model and drawings that reveal the spatial qualities of your concept in horizontal
3. section (plan) and vertical sections. By the Friday pin-up the team must be able to
visually present their 3 individual concepts using horizontal and vertical dissections.
Week 7, Concept development
The team should use their three design ideas to generate a set of design principles
that will inform one design. To do this, the team should record the design principles
revealed in each team member’s design idea as thumbnails and phrases. Record the
principles that are common to all your designs and alongside these record other
principles that all team members agree should inform your team-design. From these
defining team design principles each team member should propose a new team
design. At the beginning of your tutorial pin-up these three alternative team designs.
Week 8, Detailed design and Representation of Domus
Repeat the idea selection exercise of week 7 to arrive at a new set of design
principles. Use these principles to generate one team design. Present this as a
sketch/thumbnail in your tutorial. This design idea will be further developed in the
remaining two weeks of the project. The major component of this phase is the
development of a wall-section through Domus. The wall section is a section that runs
from the ground up, through your building envelope showing how your internal
environment is related to the external environment.
Week 9, Presentation
The representation of your team design for Domus must comprise orthographic
projections of your scheme in 6 A2 (594mm x 420mm) sheets in portrait format
and a physical model of Domus and its site at 1:50. A well-presented and
thoughtfully composed presentation is required, addressing the following:
Site plan @ 1:50 showing major features (landscape, vegetation,
contours) and the scheme (floor plan, openings, level changes etc.)
The site being 12 x 36 meters, 2 A2 sheets in portrait format can clearly express this
requirement @ 1:50 scale (bottom half of sheets). North orientation must be shown
facing vertically up the sheet. Circulation, ordering principles and spatial organization
must be clear from reading the plan. Text is to be used sparingly. Colour is
recommended. Digital prints, in colour may be made in the Resource Centre (contact
Marj Timberlake, for details : marj@deakin.edu.au, ph.: 52278338).
Long Section @ 1:50, Short section and/or Elevations
In the top half of the two sheets described above, draw a detailed long section
through the site. Clearly show the distinction between ground and your scheme. Pay
particular attention to the details that are necessary to bring out your section. Use
photomontage and other techniques, to develop the section. All drawings must have
elements of the site present.
Wall Section @ 1:20
Incorporate a 1:20 Wall Section through the external envelope of your Domus,
indicating the scale, size and composition of material usage, openings, connections.
The wall section need not indicate how your Domus will be constructed, so
construction details are not necessary.
Physical Model @ 1:50
Card and balsawood are examples of materials you may wish to use. The model
must clearly show the site as well as your scheme. You may use the sectional model
technique or any other means of model presentation. The only requirement for the
model is that it be made of to a high quality. Des Walters is the Technical Officer in
charge of the model workshop. (dwalt@deakin.edu.au). He will be available as a
resource for SRD263 for help with model-making queries and advise during
workshop hours.
Design Process
4. On 1 A2 sheet present your thumbnails from every week. There should be 3 from
Week 7, 3 from Week 1, and 1 from each of the remaining Weeks 9, 10 and 11. So
you should present 9 thumb-nails in total. These thumbnails will provide a ‘storey-
board’ of the team’s design process. This may not be a linear storey-board for it may
have dead-ends and about-turns. Do not merely mount old thumbnails if they are not
now of a quality appropriate for presentation - in which case they may need
redrawing.
Submission process
On the morning of the Week 9 studio, submit your work between 10:00 and 10:45 am in
studio where either Marj Timberlake or a Studio tutor will note that you have completed
your project, and add a submission stamp on the back of each of your A2 sheets. You
must have pinned up your submission in Studio by 11:30 am. If your work is not
stamped on time, pinned up by 11:30 or you are late for your review you will be
penalised for late submission. Any student who does not present for review will be
penalised 30% of the project marks.
Review Programme
Details of review programme will be posted on DSO. The broad outline of Review is
as follows on the next page:
Time Location: A+B Studio Location A+B Studio Location: A+B Studio Location A+B Studio Location A+B Studio
Tute Group 1
Taliesen
Matt Baird
Tute Group 2
Copacabana
Lana van Galen
Tute Group 3
Sangath
Ron Golany
Tute Group 4
Battersea
Guenter Lehmann
Tute Group 5
Mosman
Richard Tucker
1100--1155 Teams T1 & T8 Teams C1 & C8 Teams S1 & S8 Teams S1 & S8 Teams M1 & M8
1200--1255 Teams T2 & T7 Teams C2 & C7 Teams S2 & S7 Teams S2 & S7 Teams M2 & M7
1300--1355 Teams T3 & T6 Teams C3 & C6 Teams S3 & S6 Teams S3 & S6 Teams M3 & M6
1400--1505 Teams T4 & T5 Teams C4 & C5 Teams S4 & S5 Teams S4 & S5 Teams M4 & M5
Contact Richard Tucker via the DSO Domus discussion thread if you need further
clarifications.
Fair Assessment of Team-members Contribution
Team/Individual assessment - In order to make sure that each individual within a
team receives a grade that reflects their contribution to the project we will be using an
on-line self-and-peer-assessment (SAPA) tool that has been developed over the
course of the last three years. Every week, each team-member must log in to the
SAPA to rate the contribution of themselves and their teammates. This register uses
two quantitative measures and one qualitative measure. The first measure asks you
to award yourself and your peers a percentage of a team grade. This first measure is
backed up by a second that asks you to rate one another on a five-point multiple-
response Likert scale. Self-assessment in this process has been shown to encourage
learners to take responsibility for their own learning through the making of reflective
judgments. The further purpose of the third qualitative measure, which asks you to
comment on your own performance and that of your peers, is to elucidate anomalies
or unexpected final evaluations.
At the end of the project, an assessment matrix will be generated that awards each
team member a multiplier of a final team grade that had been assessed by the unit
coordinator, tutors and moderators. As the SAPA is an integral part of team-working
process, for each week that you log in to the register and satisfactorily fill in each of
the three measures (the process takes only about 5-10 minutes), 2 marks (2%) will be
added to your individualised project grade. When you fail to complete the register, it
defaults to award everyone in the team an equal share of the marks. The register will
5. be open each week from Thursday morning to midnight on Monday. Eighty-five
percent of students in 2006 were awarded multipliers within the range of 0.85 – 1.15,
for the only students heavily penalised were those who were consistently rated by all
their team-mates as under-performing. The assessment register will be demonstrated
in the lecture introducing the Into Energy Efficient Design project. Full instructions for
its use can be found on the SRD264 contents page of DSO.