When you want to enter a structure, you politely knock on the door. When the door does not open after that, you knock harder.
 The type of object varies depending on the attacker, from tree trunks barely cleared of branches to metal-capped beams carried and swung on a wheeled carriage. Some can even be fully covered by a protective shield to ward off arrows and oil. Just watch out if the gate opens just as you're about to hit.
This is very common in fiction. After all, it's dramatic, looks cool, and has plenty of basis in Real Life. The Theory of Narrative Causality, however, means that it's only effective half the time. If they are successful, it's Breaching the Wall.
Sometimes, a person has to be substituted as the battering ram, mostly through his head. Other times, a large, powerful animal or monster may be used in this capacity instead.
If you use a vehicle as the ram, then you have found that Ramming Always Works. If the vehicle is an automobile, then you have mastered the art of Car Fu. See also Anti-Structure.
Examples:
- Magic: The Gathering: Battering Ram destroys walls that block it. It's a relatively weak artifact creature in and of itself, but can team up with another attacking creature so that anything that blocks the one also has to fight the other.
- Kajko I Kokosz: Used twice. On one occasion, Clumsy suggests that the brigands simply break down the town's gate (as opposed to coming up with scheme of the week) They agree to the plan but forget to bring the ram and end up using Clumsy's head instead. On the other occasion the one shot villains, the Falcon Band, break down the gate with a ram, only to realize that the heroes had covered it with glue the night before.
- The Smurfs: Used in "The Fake Smurf" (and its Animated Adaptation). Also used in "The Smurfs And The Book That Tells Everything" to pound open Brainy's door, until Brainy opens the door and lets the Smurfs with the ram enter only to crash into a wall.
- Tintin: In Tintin: The Red Sea Sharks Tintin and Haddock use a heavy chest as an improvised battering ram to escape the cabin they have been locked up in.
- Disney Animated Canon:
- Beauty and the Beast: The villagers use a log to force open the Beast's castle door.
- The Hunchback of Notre Dame: Quasimodo drops a long piece of wood onto the rabble attacking Notre Dame and the rabble use it as an improvised battering ram.
- Mulan: When Shan-Yu takes the Emperor hostage inside the Imperial Palace, Shang and the others use one of the guardian dog statues to try to break in.
- Jackboots on Whitehall: Those Wacky Nazis try to break down Hadrian's Wall with a battering ram mounted on the front of a Kettenkrad!
- The Mansions of the Gods: As Astérix and Petiminus are trying to break into the building where Obélix is held, a dimwitted Roman soldier arrives... and joins them in trying to open the door, then is promoted to living battering ram. When that still fails, Dulcina steps in to pick the lock.
- In The Return of Hanuman, the villagers uses a piece of log to break into Maruti's house.
- Toy Story 2: "But I don't wanna use my head!"
- Ben-Hur: There's a Hope Spot when the Roman galley appears to have escaped danger, only for a Greek warship to come baring down on them and ram straight through their hull, causing their own galley to break up and sink. In a further horror, there's a Roman prisoner strapped to the front of the ram.
- In Braveheart, the hero and his man are seen ramming in the gate to York. This gets an added Incendiary Exponent — if the door doesn't fall down it can burn down.
- Captain America: The Winter Soldier: A highly modern one is used to breach Fury's SUV, because the thing's armored like a tank.
- Dawn of the Planet of the Apes. The apes and gorillas are shown using the handheld version, only to leap out of the way when Koba comes riding up on a runaway armoured vehicle. The steel doors come crashing down under the impact, and the human defenses quickly fall once the numerically superior apes swarm inside.
- Dragnet features an LAPD vehicle which is a cross between a battering ram and a tank.
- In Fury (1936), an angry mob uses a large wooden beam to break open the door to the sheriff's quarters.
- The Great Bank Robbery: After numerous unsuccessful assaults, the Mexican bandits successfully smash their way into the fortress-like bank using a giant tree trunk as a ram, only to learn the bank's already been robbed by someone else.
- In Hairspray, at one point they use a hairspray battering ram.
- The Hobbit: The Battle of the Five Armies: Hilariously combined with Use Your Head. When the orc forces begin their attack on Dale, a troll with huge chunk of stones tied to his head rams the wall as a living battering ram and then... promptly flops back after knocking himself out.
- Hot Fuzz: two huge chains of shopping carts were used as this.
- The Hunchback of Notre Dame: In the 1923, 1939, and 1956 adaptations, Quasimodo drops a long piece of wood onto the rabble attacking Notre Dame, and the rabble use it as an improvised battering ram.
- The Lord of the Rings:
- In The Two Towers, the Uruk-hai use a battering ram against Helm's Deep's gates.
- Likewise, the orc army in The Return of the King uses a battering ram to attack the gates of Mines Tirith. Their standard battering ram has absolutely no effect on the gate, so they bring up Grond...
Gothmog: What are you doing, you useless scum?
Murgash: The door won't give! It's too strong!
Gothmog: Get back there, and smash it down!
Murgash: But nothing can breach it!
Gothmog: ...Grond will breach it. Bring up the wolf's head!
- The Man with Two Brains: Some policemen attempt to use one to break into an apartment.
- In The Pirate Movie, the pirates use a battering ram to... ring the doorbell. On their second charge, the butler opens the door and they charge through.
- Siege of the Dead: the protagonist constructs a Rammbock to break through the walls of the apartment building he's trapped in during a Zombie Apocalypse.
- Treasure Island (1934): A bunch of pirates after a treasure map break their way through into an inn with a log acting as a makeshift battering ram.
- In Up the Chastity Belt, Sir Braggart's men use a battering in an attempt to break into Lukalot's workshop, but he defeats them with Door Judo.
- Young Frankenstein: When the angry mob attacks the castle, they use Inspector Kemp (with his artificial arm extended) as their battering ram.
- Able Team: Carl Lyons takes part in a SWAT raid and notes with amusement that their battering ram has the letters L.A.P.D. engraved in reverse on the head, so it would stamp them on any door it's rammed into.
- Animorphs: Jake's rhinoceros morph and Rachel's elephant morph are used as living versions of this on a number of occasions.
- The Infected has a curious incident in which a battering ram, mounted in some kind of IFV, is used to bring down a chain-link fence. Nevermind that an armored vehicle could probably bring down the fence by simply driving through it.
- The Lord of the Rings: The army attacking Minas Tirith uses a battering ram called Grond against its gates.
- Masters of Rome: Julius Caesar is fond of using "battering ram" as an Unusual Euphemism for his... you know what.
- In The Mouse That Roared, the solders of Grand Fenwick need to get past a locked door at the New York Institute of Physics. So they chop down a tree and cover one end with a chain mail shirt. They then batter down the door. Cut to later on as an almost crying historian examines the chain mail shirt and laments over the destruction of a perfect replica of ancient chain mail.
- Pyramids has Alfonse, a pirate covered in highly explicit tattoos who appears to have found employment as a battering ram in the past. He also turns into a shamefaced wreck when the woman in charge of the palace handmaidens' education uses him as a living diagram, his fingers stuck in his ears as hard as he can.
- Agents of S.H.I.E.L.D.: A device similar to the "big red key" is used by "real" S.H.I.E.L.D. to break into a Hulk-proof safehouse in "Afterlife".
- Barbary Coast: The Crusaders use a battering ram to break down the doors of the police station when they drag Diamond Jack Bassiter out and lynch him in the pilot movie.
- The Bill: A smaller version that can be operated by one person, referred to by British Coppers everywhere as "the big red key", has shown up a few times.
- Brainiac: Science Abuse: Brainiac: History Abuse had the Brainiac Battering Ram Squad, whose job was hitting things with a battering ram.
- Dad's Army: In "Museum Piece", the platoon uses a battering ram in an attempt to break down the doors of the museum, only to be defeated by some Door Judo by the museum caretaker.
- Masada features a battering ram with a massive ram-shaped metal head mounted on a siege tower to bring down the walls of the Last Bastion of the Jewish Zealots.
- Monty Python's Flying Circus: In "The Bishop" sketch, the Bishop's acolytes use one of their number as a battering ram at one point.
- Power Rangers Turbo: In the end of the series, the Big Bad's Mooks enter the command center using one of these.
- Red Dwarf: In one episode, the crew needs a battering ram to get through a series of doors. "All we need is something, say, I dunno, six foot long, fairly sturdy, with a flat top." Everyone looks at Kryten. "Fifty-three doors? You can't be serious!" Fifty-three doors later...
Lister: Kryten, are you okay?
Kryten: I'm fine, thank you Susan! - Reno 911!: In the opening theme for the first season, Dept. Jones tries to open a door by ramming into it using his shoulder. He only succeeds in hurting himself.
- The Twilight Zone (1959): In "The Shelter", Dr. Bill Stockton's neighbors fashion one together to break into his bomb shelter. Immediately after they break the shelter's door down, they learn from a CONELRAD broadcast that the unidentified objects were satellites as opposed to missiles.
- Dungeons & Dragons has both the traditional version (check the Dungeon Master's Guide) and smaller man-portable rams similar to the type used by police in Real Life. Dragon magazine has also had at least two articles on siege-warfare that include magical rams.
- Lancer has the Juggernaut Talent, for when you want to use your mecha as a massive ram. Several chassis also have innate abilities that help with this, such as Tortuga's Siege Ram
- Warhammer 40,000 has the Caestus Assault Ram, a spacecraft intended to get close to enemy flagships, fire a magnamelta shot at it, then ram through the now-softened armor to deliver a squad of Space Marines inside. Later someone figured that what can ram a Mile Long Spaceship without damage to itself or passengers will probably work well against ground targets as well.
 So we get a scene where the much-deprived men of Athens grab a big trunk of wood and ram it against the doors of the Acropolis again and again, desperately trying to force their way inside.
- Age of Empires II: Battering rams are one of four siege units you can build in the Siege Workshop. They are slow but are capable of demolishing buildings in seconds. In addition, it's high pierce armor makes them perfect meatshields against archer-focused civilizations.
- Age of Mythology: The Norse get light man-portable rams. The Egyptians and Greeks opt to use siege towers with rams in the base.
- Age of Wonders: In the first game, rams are the most basic way to get past enemy walls. Even small villages can build them. However, their slowness makes them difficult to use.
- All Points Bulletin has these for the Enforcers when the player is to breach a door or car to get to an item.
- Bastion: Near the end , the player character receives one as a weapon... which he carries himself. He can use to smash down doors and clear the room of obstacles and enemies in a single move. However, it slows him down to a crawl, turning him into a Mighty Glacier.
- Civilization: Attila and the Huns have this as a unique Ancient Era unit in the fifth game, where it is extremely effective in the Ancient Era, capable of taking down any city in two hits or less. The battering ram would make a return in the sixth game as an Ancient Era unit for all civilizations, which provided the ability for melee units to bypass the wall health of a city when attacking.
- Dragon Age: Inquisition: During the "Here Lies the Abyss" quest, the eponymous military force assaults an ancient fortress called Adamant. Part of the assault involves swinging a battering ram at the door; it's shaped like a giant arm clutching some kind of weapon in its fist.
- Dynasty Warriors: One of the many siege weapons available. 8 also has the "Siege Spear" wielded by Xiahou Ba: a bizarre fusion of a spear and a rocket-propelled battering ram.
- The Elder Scrolls Online: One of the siege weapons. Beware when using it, however: a player defending the keep may pour flaming oil down on you.
- Empire Earth: In the early ages, the very first siege weapon available is the Samson, an infantry unit carrying a huge log he repeatedly bashes against whatever building he's pointed at. Due to Tactical RockPaperScissors, he's unable to attack anything but buildings. Later eras have wheeled battering rams that can still only attack buildings and are best used in large groups (the AI certainly will).
- Final Fantasy XIV: The end of the Stomrblood story has a unique take on the trope. The huge door leading into the city of Ala Mhigo is sealed shut. How does the Alliance get it open?
- Kingdoms Of Camelot has battering rams as a weapon. They're a higher-level weapon, not unlocked until the player has a level 9 Barracks and several high level researches completed. They also tend to require a lot of food upkeep, so they aren't trained quite as often as foot or horse troops. They are great for attacking other players' cities, though you have to watch out for defensive trebuchets, which specifically target siege weaponry.
- In Stronghold, engineers build rams on the field and must man them to be usable.
- Total War: A reliable way to smash through city or castle gates in many games, assuming enemy archers don't get lucky and set it alight with flaming arrows... or it's not late enough in the game for the enemy settlement to have cannon towers that smash the ram to splinters in one shot. Unlike many video game examples, these rams aren't constructed normally, but built by your armies in the field once they besiege a settlement.
- War elephants can also be used as battering rams.
- Total War: Warhammer includes the ram when besieging, but it becomes redundant for some races who have access to monstrous creatures (such as giants, Dragon Ogres, or Varghulfs) who are more agile and durable than a wooden ram and can smash a gate apart just as easily.
- Warcraft III has the Steam Tank/Siege Engine, which (despite being a steam-powered tank) is functionally a battering ram, as it has very short range and can only target buildings. In the expansion, it gains a Macross Missile Massacre attack against air units.
- Girl Genius: Along with a more traditional example, the comic features something a bit different in the form of a gigantic, flesh-and-blood ram sent to headbutt the gates of Mechanicsburg.
General Zog: At least it ain't vun ov de vuns vot breathe fire. Dose vuns wos alvays hexplodeink ven dey hit.
- In The Senkari, a dragon serves as a makeshift battering ram.
- Fairly OddParents: "Information Stupor Highway" used battering rams in a Running Gag.
- Motorcity: Texas's car, Stronghorn, has one.
- Looney Tunes:
- In "Red Riding Hoodwinked," the Big Bad Wolf uses a log this way to bust down the back door to Grandma's House. But then he encounters Sylvester's own solution: a boulder slingshot from the front door.
- In "Mouse Divided," this is how a horde of cats attempts to access Sylvester's house. He answers with Door Judo.
- The Simpsons: One time when Maggie Simpson is locked inside the bathroom all by herself, Bart uses Homer's head as a battering ram to try to open the door.
- Police forces and fire brigades use smaller versions of battering rams to access locked doors. The former tends to use them on particularly stubborn suspects who refuse to come out of the room they're locked in, making it a real life example of Cutting the Knot. The latter use it to open any door they deem necessary to put out a blaze as quickly as possible while mitigating any potential damage. You might lose a door, but at least you'll get your man or get the flame put out.
- Luftwaffe named a heavily armoured and armed version of Focke-Wulf 190A-8 as Sturmbock ("battering ram"). Why? Because it was intended to bring down the Flying Fortress! Some time in the 1950s, Popular Mechanics ran a front-page article proposing to take this more literally. Machine guns and cannon couldn't reliably bring down a huge multi-engined bomber and reliable guided missiles were some way off, so why not design a fighter that could just smash into them and (hopefully) come through mostly intact? Not surprisingly, the idea was never pursued by the US Air Force or any aircraft designers.


{{content}}
Output Configuration
A copy of the config will appear after all required fields are filled in. Once it appears, click on the "copy output" button to add it to your clipboard. You'll then be taken to a new tab where you can paste that output and commit the change.


Version 4.12¶
Release date: 2019-08-22
This release contains a number of bug fixes and new features since the release of pgAdmin4 4.11.
New features¶
Issue #4144 - Add support of Compound Triggers for EPAS 12+.
Issue #4333 - Add support for planner support functions in PostgreSQL 12+ functions.
Issue #4334 - Add support for generated columns in Postgres 12+.
Issue #4540 - Use the full tab space for CodeMirror instances on dialogues where appropriate.
Issue #4549 - Allow a banner to be displayed on the login and other related pages showing custom text.
Issue #4566 - Allow enhanced cookie protection to be disabled for compatibility with dynamically addressed hosting environments.
Issue #4570 - Add an optimisation to the internal code responsible for searching for treeview nodes.
Issue #4574 - Display the row count in the popup message when counting table rows, not just in the properties list.
Issue #4612 - Add support in query history to show internal queries generated by pgAdmin during save data operations.
Housekeeping¶
Issue #4546 - Add Reverse Engineered SQL tests for Columns.
Issue #4554 - Add Reverse Engineered SQL tests for Trigger Functions.
Issue #4555 - Add Reverse Engineered SQL tests for Exclusion Constraint.
Issue #4560 - Add a –modules option to the RE-SQL test suite to allow testing of specific object types.
Bug fixes¶
Issue #3605 - Fix issue where Deleting N number of rows makes first N number of rows disable.
Issue #4179 - Fix generation of reverse engineered SQL for tables with Greenplum 5.x.
Issue #4229 - Update wcDocker to allow the browser’s context menu to be used except in tab strips and panel headers.
Issue #4401 - Ensure type names are properly encoded in the results grid.
Issue #4414 - Fix generation of reverse engineered SQL for partition table, partitions were shown as a child of indexes.
Issue #4489 - Update wcDocker to prevent window state loading creating blank dialogues.
Issue #4490 - Fix accessibility issue for checkbox in IE11.
Issue #4492 - Ensure the Query Tool doesn’t throw an error when viewing the contents of a table with no columns.
Issue #4496 - Ensure columns can be created when they are IDENTITY fields with the CYCLE option enabled.
Issue #4497 - Ensure purely numeric comments can be saved on new columns.
Issue #4508 - Fix accessibility issue for Datetime cell in backgrid.
Issue #4520 - Ensure the query tool will work with older versions of psycopg2 than we officially support, albeit without updatable resultsets.
Issue #4525 - Ensure command tags are shown in the messages tab of the Query Tool.
Issue #4536 - Fix load on demand in View/Edit data mode.
Issue #4552 - Fix some errors thrown on the JS console when dragging text in the Query Tool.
Issue #4559 - Ensure triggers should be updated properly for EPAS server.
Issue #4565 - Fix the reverse engineered SQL for trigger functions with the WINDOW option selected.
Issue #4578 - Ensure enable trigger menu should be visible when trigger is disabled.
Issue #4581 - Ensure the comment on a Primary Key constraint can be edited under the Table node.
Issue #4582 - Fix console error when changing kind(SQL/BATCH) for pgAgent job step.
Issue #4585 - Fix double click issue to expand the contents of a cell if the resultset was not editable.
Issue #4586 - Fix generation of reverse engineered SQL for Rules.
Issue #4635 - Ensure compound triggers for event should be updated properly.
Issue #4638 - Ensure compound triggers should be displayed under Views.
Issue #4641 - Ensure Truncate option should be available for Compound Triggers.


The Benefits of Control
October 4, 2015
Version control is like living for today and not giving up the past. Version control is when each of us gets our own way, and the group stays happy. Version control is being in two places at once.
As if that wasn't crystal clear, let's add that version control is how developer teams all stay on top of the game, even when people are doing their own thing. It allows individuals to work on a project without slowing down or affecting the work of others. It allows bugs to be quickly identified and isolated. It allows people in different places to work at their speed and in disparate directions, while still pushing toward the same goal. It allows great minds to work at their best, without the technology getting in the way.
Ch-ch-changes
We all want to believe that the longer we work on something, the better it should be. Working on complicated systems like computer programs can show us that's not always true. If I spend all morning writing code to improve something on the right side, I will be crushed to see that my changes also succeeded in breaking something on the left. Ugh. With git, that disappointment should last only as long as it takes me to compare the latest code to my last commit, and isolate the problem.
Any person who has used "track changes" in Word will be blown away by the visual display of changes on Github. It's so clear to see how text was added here, or removed here, as well as to have access to the informative justifications that are often included in each commit. This is especially important when my team members are far away. I don't have to make a long phone call to another time zone to learn what my colleague did and why. Github will show me, instantly. And if I realize that all those changes I did this morning are for naught? Well I can roll back to my previous commit, and pretend none of that ever happened. That's the best part of tracking changes with version control.
Keep it on the 'hub
Contrary to what the song says, some of the best things in life are free. And that's true with Github.* It lets us host our public repo's, make commits, fork, share, download, upload, restore our files, and all for free. If you work alone, use Github to store your repo's and consider it a hosted backup. Super cool. If you're working with a team, you stores your code there because it takes each team member a couple commands to stay up to date with the code base, and to instantly share her code with the rest of the team. No emailing dropbox URL's or putting files up on an ftp server. It's just there. Push, pull, clone, and git does the rest.
*Charges apply on private repo's


states |
array
|
Array of all states. |
currentState |
String
|
The current state of the state machine. |
constructors |
array
|
Array of all constructor functions for all states. |
transitions |
array
|
Array of all transition functions for all states. |
destructors |
array
|
Array of all destructor functions for all states.
|
start(string_state) |
function
|
Starts the StateMachine in the given state. (Calls contructors for that state) |
createState(string_state(s)) |
function
|
Add state or list of states to the StateMachine. Ex: "state1, state2" |
createTransition(string_transition,function_transition) |
function
|
Adds transition between two states or groups of states and a transition function which will be run during the transition (between the destructor and constructor). Ex: "(state1, state2) -> state3", "state1 <-> state2" |
createConstructor(string_state(s),function_constructor) |
function
|
Adds a constructor for a state or list of states which will run when entering the state. |
createDestructor(string_state(s),function_destructor) |
function
|
Adds a destructor for a state or list of states which will run when leaving the state. |
transitionTo(state) |
function
|
Transitions to the provided state. Calls destructor(s) for currentState, transition function(s) to new state, and constructor(s) for new state. |
addParent(stateMachine,state) |
function
|
Adds a parentState (of another stateMachine, parentMachine) for this StateMachine so that the parentMachine will transtion to the given parentState when a transtionTo is called of this stateMachine. |


Manifesto Why Chaplin was created
Chaplin is an architecture for JavaScript applications using the Backbone.js library. The code is derived from moviepilot.com, a large single-page application.
- Motivation
- Building Chaplin
- The Architecture in Detail
- Application
- Mediator and Publish/Subscribe
- Router
- Dispatcher
- Layout
- Controllers
- Models and Collections
- Views
- Event Handling Overview
- Memory Management and Object Disposal
- Handling Asynchronous Dependencies
- The Cast
- The Producers
Motivation
While developing several web applications using Backbone.js, we felt the need for conventions on how to structure such applications. While Backbone is fine at what it’s doing, it’s not a framework for single-page applications. Yet it’s often used for this purpose.
Chaplin is mostly derived and generalized from the codebase of moviepilot.com, a real-world single-page application. Chaplin tries to draw the attention to top-level application architecture. “Application” means everything above simple routing, individual models, views and their binding.
Backbone is an easy starting point, but provides only basic, low-level patterns. Especially, Backbone provides little to structure an actual application. For example, the famous “Todo list example” is not an application in the strict sense nor does it teach best practices how to structure Backbone code.
To be fair, Backbone doesn’t intend to be an all-round framework so it wouldn’t be appropriate to blame Backbone for this deliberate limitations. Nonetheless, most Backbone use cases clearly need a sophisticated application architecture. This is where Chaplin enters the stage.
Building Chaplin
The individual source files of Chaplin are originally written in the CoffeeScript meta-language. The Chaplin library file however is compiled JavaScript file which defines the chaplin
AMD module.
To compile the CoffeeScripts and bundle them into one file, please run the Ruby script build.rb
in the build
directory:
cd build
./build.rb
This creates several files in ./build/:
chaplin.coffee
– The Chaplin library in one CoffeeScript filechaplin.js
– The same as a compiled JavaScript filechaplin-min.js
– Minifiedchaplin-min.js.gz
– Minified and GZip-compressed
The Architecture in Detail
The following chapters will discuss the core objects and classes of our application structure.
Application
The root object of the JavaScript application is just called Application
. In practise, you might choose a more meaningful name. Application
is merely a bootstrapper which starts up three other core modules:
mediator
Router
Dispatcher
Layout
Mediator and Publish/Subscribe
Using the AMD module convention, a script might load other objects it depends upon, like the class (constructor) it inherits from. Since most objects are encapsulated and not publicly accessible, a module normally does not have access to the actual instances of other classes.
Modules communicate and share data using the mediator
. That’s just a simple object which has per default three methods for global Publish/Subscribe: subscribe
, unsubscribe
and publish
.
Publish/Subscribe (Pub/Sub) is a versatile pattern to ensure loose coupling of application modules. To inform other modules that something happened, a module doesn’t send messages directly (i.e. calling methods of specific objects). Instead, it publishes a message to a central channel without having to know who is listening. Other application modules might subscribe to these messages and react upon them.
For simplicity, we borrow the functionality from the Backbone.Events
mixin. The subscribe
, unsubscribe
and publish
methods are simply aliases for trigger
, on
and off
of the Backbone.Events
mixin.
For example, several modules are interested in the user login event and subscribe to the login
message. In practice, they load chaplin
as a dependency and register a callback function for the login
event:
Chaplin.mediator.subscribe 'login', @doSomething
A Publish/Subscribe message consists of a name and optional data. For example, the module in charge of handling the login might publish a message with the identifer login
and the user
object as additional data:
mediator.publish 'login', user
The second and all subsequent arguments are passed through to the handler functions.
Router
The Router is responsible for observing URL changes. If a declared route matches the current URL, an event is triggered.
The Chaplin Router
does not inherit from Backbone’s Router
. It’s a different implementation with several advantages over the standard router.
In Backbone’s concept, there are no controllers. Backbone’s Router
maps routes to its own methods, so it’s serves two purposes. Our Router
is just a router, it maps URLs to separate controllers, in particular controller actions. Just like Backbone’s standard router, we’re using an instance of Backbone.History
in the background.
By convention, all application routes should be declared in a separate file, the routes
module. The Chaplin Router
has a match
method to create routes which is used to register routes:.
match 'likes/:id', 'likes#show'
match
works much like the Ruby on Rails counterpart since it creates a proper params
hash. If a route matches, a matchRoute
event is published passing the route instance and the parameter hash.
Additional fixed parameters and parameter constraints may be specified in the match
call:
match 'likes/:id', 'likes#show', constraints: { id: /^\d+$/ }, params: { foo: 'bar' }
Dispatcher
Between the router and the controllers, there is the Dispatcher
which listens for routing events. On such events, it loads the target controller module, creates a controller instance and calls the target action. The previously active controller is automatically disposed.
A specific controller may also be started programatically. To start a specific controller, an app-wide !startupController
event can be published:
mediator.publish '!startupController', 'controller', 'action', params
The Dispatcher
handles the !startupController
event.
Layout
The Layout is the top-level application view. When a new controller was activated, the Layout
is responsible for changing the main view to the view of the new controller.
In addition, the Layout
handles the activation of internal links. That is, you can use a normal <a href="/foo">
element to link to another application module.
Controllers
In the Chaplin concept, a controller is the place where a model and associated views are instantiated. A controller is also in charge of model and view disposal when another controller takes over. Typically, a controller represents a screen of the application.
There can be one current controller which provides the main view and represents the current URL. In addition, there can be several persistent controllers which govern special views like a header, a navigation sidebar or a footer.
Specific Module Controllers
By convention, there is a controller for each application module. A controller may provide several action methods like index
, show
, edit
and so on. These actions are called by the Dispatcher
when a route matches.
For example, this is the stripped-down LikesController
:
``` define [‘controllers/controller’, ‘models/likes’, ‘models/like’, ‘views/likes_view’, »» ‘views/full_like_view’], (Controller, Likes, Like, LikesView, FullLikeView) ->
‘use strict’
class LikesController extends Controller
historyURL: (params) ->
if params.id then "likes/#{params.id}" else ''
# initialize method is empty here
index: (params) ->
@collection = new Likes()
@view = new LikesView collection: @collection
show: (params) ->
@model = new Like id: params.id
@view = new FullLikeView model: @model ```
A typical controller has one model or collection and one associated view. They should be stored in the model
/collection
and view
instance properties so they are disposed automatically on controller disposal.
Per default, a controller is instantiated afresh with every route match. That means models and views are disposed by default even if the new controller is the same as the old controller. To persist models and views, it is recommended to save them in a central store, not on the controller instances.
Most of the time, a controller is started following a route match. In this case, the URL representing the application state is already given. But a controller can also be started programatically by publishing a !startupController
event. In this case, the URL has to be determined. This is the purpose of the historyURL
method.
Models and Collections
Chaplin extends the standard Backbone models and collections with some new methods. dispose
is the destructor for cleaning up. The Chaplin Collection
also has addAtomic
for adding several items while fireing a reset
event, and update
for updating a collection while fireing several add
/remove
events instead of a single reset
event.
Using these Model
and Collection
classes, we create a hierarchy of CoffeeScript classes. Many child classes override methods while calling super
.
Models and collections are Publish/Subscribe event subscribers by using the Subscriber
mixin. Please do not register their methods directly as Pub/Sub listeners, use subscribeEvent
instead. This forces the handler context so the handler might be removed again on model/collection disposal. It’s crucial to remove all references to model/collection methods to allow them to be garbage collected.
Views
Chaplin’s View
class is a highly extended and adapted Backbone View
. All views should inherit from this class to avoid repetition.
Views may subscribe to Publish/Subscribe and model/collection events in a manner which allows proper disposal. They have a standard render
method which renders a template into the view’s root element (@el
).
The templating function is provided by getTemplateFunction
. The input data for the template is provided by getTemplateData
. By default, this method just returns an object which delegates to the model attributes. Views might override the method to process the raw model data for the view.
In addition to Backbone’s events
hash and the delegateEvents
method, Chaplin has the delegate
method to register user input handlers. The declarative events
hash doesn’t work well for class hierarchies when several initialize
methods register their own handlers. The programatic approach of delegate
solves these problems.
Also, @model.bind()
should not be used directly. Chaplin has @modelBind()
which forces the handler context so the handler can be removed automatically on view disposal. When using Backbone’s naked bind
, you have to deregister the handler manually to clear the reference from the model to the view.
CollectionView
The CollectionView
is responsible for displaying collections. For every item in a collection, it instantiates a given item view and inserts it into the DOM. It reacts to collection change events (add
, remove
and reset
) and provides basic filtering, caching of views, fallback content and loading indicators.
Event Handling Overview
For models and views, there are several wrapper methods for event handler registration. In contrast to the direct methods they will save memory because the handlers will be removed correctly once the model or view is disposed.
Global Publish/Subscribe Events
In models and views, there is a shortcut for subscribing to global events:
@subscribeEvent 'login', @doSomething
This method has the advantage of removing the subscription on model or view disposal.
The subscribeEvent
method has a counterpart unsubscribeEvent
. These mehods are defined in the Subscriber
mixin, which also provides the unsubscribeAllEvents
method.
Model Events
In views, the standard @model.bind
way to register a handler for a model event should not be used. Use the memory-saving wrapper modelBind
instead:
@modelBind 'add', @doSomething
In a model, it’s fine to use bind
directly as long as the handler is a method of the model itself.
A view also provides modelUnbind
and modelUnbindAll
for deregistering. The latter is called automatically on view disposal.
@modelUnbind 'add', @doSomething
User Input Events
Most views handle user input by listening to DOM events. Backbone provides the events
property to register event handlers declaratively. But this does not work nicely when views inherit from each other and a specific view needs to handle additional events.
Chaplin’s View
class provides the delegate
method as a shortcut for @$el.on
. It has the same signature as the jQuery 1.7 on
method. Some examples:
@delegate 'click', '.like-button', @like
@delegate 'click', '.close-button', @skip
delegate
registers the handler at the topmost DOM element of the view (@el
) and catches events from nested elements using event bubbling. You can specify an optional selector to target nested elements.
In addition, delegate
automatically binds the handler to the view object, so @
/this
points to the view. This means delegate
creates a wrapper function which acts as the handler. As a consequence, it’s currently not possible to unbind a specific handler. Please use @$el.off
directly to unbind all handlers for an event type for a selector:
@$el.off 'click', '.like-button'
@$el.off 'click', '.close'
Memory Management and Object Disposal
One of the core concerns of the Chaplin architecture is a proper memory management. There isn’t a broad discussion about garbage collection in JavaScript applications, but in fact it’s an important topic. Backbone provides little out of the box so Chaplin ensures that every controller, model, collection and view cleans up after itself.
Event handling creates references between objects. If a view listens for model changes, the model has a reference to a view method in its internal _callbacks
list. View methods are often bound to the view instance using Function.prototype.bind
, _.bind()
, CoffeeScript’s fat arrow =>
or alike. When a change
handler is bound to the view, the view will remain in memory even if it was already detached from the DOM. The garbage collector can’t free its memory because of this reference.
Before a new controller takes over and the user interface changes, the dispose
method of the current controller is invoked. The controller calls dispose
on its models/collections and then removes references to them. On disposal, a model clears all its attributes and disposes all associated views. A view removes all DOM elements and unsubscribes from DOM or model/collection events. Models/collections and views unsubscribe from global Publish/Subscribe events.
This disposal process is quite complex and many objects needs a custom dispose
method. But this is just the least Chaplin can do.
Handling Asynchronous Dependencies
Most processes in a client-side JavaScript application run asynchronously. It is quite common that an applications is communicating with different external APIs. API bridges are established on demand and of course all API calls are asynchronous. Lazy-loading code and content is a key to perfomance. Therefore, handling asynchronous dependencies is a big challenges for JavaScript web applications. We’re using the following techniques to handle dependencies, from bottom-level to top-level.
Backbone Events
Of course, model-view-binding, Backbone’s key feature, is still a building block in Chaplin: A view can listen to model changes by subscribing to change
event or other custom model events. In addition, collection and collection views are able to listen for events which occur on their items. This works because model events bubble up to the collection.
State Machines for Synchronization: Deferreds and SyncMachine
Models, collections and third-party scripts typically have a loaded state. At the beginning, they aren’t ready to use. The data is fetched from the server, they need to wait for the user login or rely upon other asynchronous input.
For these purpose, jQuery Deferreds can be mixed into appliation objects. They allow to register load handlers using the done method. The handlers will be called once the Deferred is resolved.
Deferreds are a versatile pattern which can be used on different levels in an application, but they are rather simple because they only have three states (pending, resolved, rejected) and two transitions (resolve, reject). For more complex synchronization tasks, Chaplin offers the SyncMachine
which is a state machine
Wrapping Methods to Wait for a Deferred
On moviepilot.com, methods of several Deferreds are called everywhere throughout the application. It would not be feasible for every caller to check the resolved state and register a callback if necessary. Instead, these methods are wrapped so they can be called safely before the Deferred is resolved. In this case, the calls are automatically saved as done
callbacks, from later on they are passed through immediately. Of course this wrapping is only possible for asynchronous methods which don’t have a return value but expect a callback function.
The helper method utils.deferMethods
in the Facebook example repository wraps methods so calls are postponed until a given Deferred object is resolved. The method is quite flexible and we’re using it in several situations.
Publish/Subscribe
The Publish/Subscribe pattern is the most important glue in Chaplin applications because it’s used for most of the cross-module interaction. It’s a powerful pattern to promote loose coupling of application modules. Chaplin’s implementation using Backbone.Events
is simply but highly beneficial.


This sample demonstrates how to write driver for a generic PCI device using Windows Driver Framework. The target hardware for this driver is AMCC PCI Matchmaker Developer’s kit (S5935DK1) board. The product kit and the hardware specification are available at https://www.amcc.com.
The kit contains a PCI development board and an ISA card that connects to the development board via a ribbon cable. The ISA card allows you to access the development board to provide the software side simulation of add-on device.
Following table gives a typical device and driver scenario and also lists the driver framework interfaces demonstrated in this sample:
|
Scenario |
Features Demonstrated |
|
The device is a PCI device with port, memory, interrupt and DMA resources. Device can be stopped and started at run-time and also supports low power state.
The driver is capable of doing concurrent single read and write operations at any time. |
· Handling PnP & Power Events · Registering Device Interface · Hardware resource mapping: Port, Memory & Interrupt · DMA Interfaces · Serialized Default Queue for Write requests · Serialized custom Queue for Read requests · Handling Interrupt & DPC · Event Tracing |
This sample also demonstrates how to use a single driver binary to control two different types (PCI & ISA) of devices.
This sample works on Windows® 2000 and later operating systems.
This sample driver is a minimal driver meant to demonstrate the usage of the Windows Driver Framework. It is not intended for use in a production environment.
To build the sample drivers, you must first set up the DDK environment on your host machine. The “Installation and Release Notes” in the Windows 2000/XP/Server 2003/Vista/Server 2008/Windows 7 DDK has a complete description on how to do this.
Change to the directory containing the device source code, such as CD src\general\AMCC5953.
Run build -ceZ, or use the macro BLD. This command invokes the Microsoft make routines to build the components. If the build succeeds, you will find the driver, binaries under the respective subdirectories of the source file depending on the build environment. If it fails you can find errors and warnings in the buildxxx.err and buildxxx.err respectively, where xxx is either chk or fre depending on the build environment. Copy the KMDF coinstaller (wdfcoinstallerMMmmm.dll), sys, INF and test binaries to a floppy or to a directory of a test machine.
Plug in the PCI development board and the ISA card and start your system. When you login into Administrator account, the system will welcome you with a ‘Found New Hardware Dialog’ for “Other Bridge Devices”. Follow the instruction given below to install the driver for the PCI device.
On Windows 7 and later operating systems:
1. Launch “Device Manager” by executing command devmgmt.msc in a command window, or from “Hardware and Sound” program group in Control Panel.
2. Select “PCI Device” device from “Other Devices” category and click “Update Driver Software…” from right-click menu.
3. Select Browse my computer for software and provide the location of the driver files.
4. Select “Install this driver software anyway” when the “Windows Security” dialog box appears.
5. The system will complete the installation, load the driver and start the device.
On Windows Vista and Windows Server 2008:
1. In the “Found New Hardware” dialog box, select “Locate and install driver software (recommended)”.
2. Select “Don't search online”.
3. Select “I don't have the disc. Show me other options”.
4. Select “Browse my computer for driver software (advanced)”.
5. Enter the location of the driver files, and select “Install this driver software anyway” when the “Windows Security” dialog box appears.
6. The system will complete the installation, load the driver and start the device.
On Windows XP and Windows Server 2003:
1. Select 'Install from a list or specific location (Advanced)”, then click Next.
2. Select ‘Add a new hardware device’ from the list, then click Next.
3. Select ‘Select for the best drivers in these locations' and then select, “Include this location in the search path” check box and specify the media or the directory that contains the driver package and then click Next.
4. You will get a Security Alert about installing unsigned driver. Ignore that and continue the installation by clicking on “Yes”.
5. The system will complete the installation, load the driver and start the device.
On Windows 2000:
1. Select “Display list of known devices so that I can a specific device”, and then click Next.
2. Select the “Other Class” in the Hardware type, and click Next.
3. Click on the ‘Have Disk’ and specify the media or the directory that contains the driver files, and then click Next.
4. You will get a warning message about installing unsigned driver. Ignore that and continue the installation.
The Driver for ISA device has to be installed manually because it is a non plug & play ISA device.
On Windows 7 and later operating systems:
1. Run “hdwwiz.exe” in a command window or in the “Search programs and files” of the “Start” menu.
2. At the "Welcome..." click on "Next".
3. At the "The wizard can help..." panel, select "Install...manually..." and then click "Next".
4. At the "From the list below..." panel, select "Show All Devices" and then click "Next".
5. At the "Select the device driver..." panel, just click on the "Have Disk..." button.
6. At the "Install From Disk" panel, click the "Browse..." button. From the Locate File panel specify the directory location where the AMCC install files can be found: AMCC5933.INF and AMCC5933.SYS. Click "OK" to return to the "Select the device driver..." panel.
7. In the "Model" list box, you should see a listing for "AMCC S5993 Development Kit ISA Adapter". Select this entry and then click "Next".
8. At the "The wizard is ready..." panel, click "Next".
9. At the final "Completing the Add Hardware Wizard" panel, click "Finish".
On Windows Vista and Windows 2008:
1. Start the control panel and bring up the "Add Hardware" wizard.
2. At the "Welcome..." click on "Next"
3. At the "The wizard can help..." panel, select "Install...manually..." and then click "Next".
4. At the "From the list below..." panel, select "Show All Devices" and then click "Next".
5. At the "Select the device driver..." panel, just click on the "Have Disk..." button.
6. At the "Install From Disk" panel, click the "Browse..." button. From the Locate File panel specify the directory location where the AMCC install files can be found: AMCC5933.INF and AMCC5933.SYS. Click "OK" to return to the "Select the device driver..." panel.
7. In the "Model" list box, you should see a listing for "AMCC S5993 Development Kit ISA Adapter". Select this entry and then click "Next".
8. At the "The wizard is ready..." panel, click "Next".
9. At the final "Completing the Add Hardware Wizard" panel, click "Finish".
On Windows XP and Windows 2003:
1. Start the control panel and bring up the "Add Hardware" wizard.
2. At the "Welcome..." click on "Next" (this will cause scan of device)
3. At the "Is the Hardware connected" panel, select "Yes,..." and then click "Next".
4. At the "The following hardware is already installed..." panel, select "Add a new hardware device" and click "Next"
5. At the "The wizard can help..." panel, select "Install...manually..." and then click "Next".
6. At the "From the list below..." panel, select "Show All Devices" and then click "Next".
7. At the "Select the device driver..." panel, just click on the "Have Disk..." button.
8. At the "Install From Disk" panel, click the "Browse..." button. From the Locate File panel specify the directory location where the AMCC install files can be found: AMCC5933.INF and AMCC5933.SYS. Click "OK" to return to the "Select the device driver..." panel.
9. In the "Model" list box, you should see a listing for "AMCC S5993 Development Kit ISA Adapter". Select this entry and then click "Next".
10. At the "The wizard is ready..." panel, click "Next".
11. At the final "Completing the Add Hardware Wizard" panel, click "Finish".
To install the ISA driver on Windows 2000:
1. Double-click the Add New Hardware Wizard applet in Control Panel.
2. Click Next.
3. Select Add a new device.
4. Select No, I Want to Select the Hardware from a list.
5. Select Other Devices and then click Next.
6. Click Have Disk and point to the directory that contains sys and INF file.
NOTE: Please do not load the PCI driver on a checked build Windows 2000 because WdfInterruptAcquireLock causes a benign assert in the kernel. Only way to avoid the assert would be to use KeSynchronizeExecution function instead of WdfInterruptAcquire/ReleaseLock to synchronize execution with the ISR().
To test the driver, run the TxTest.exe and RxTest.exe. Please make sure both ISA and PCI devices are installed and started before you run the application.
File Description
Driver:
Driver.c Entry points for AMCC5933 driver.
AMCC5933.h Prototype file for AMCC5933 PCI driver.
common.h Prototype file common to both the ISA and the PCI driver.
S5933DK1.h Prototype file for AMCC5933 ISA driver.
S5933DK1.c File for AMCC5933 ISA driver.
AMCC5933.c File for AMCC5933 PCI driver.
Reg5933.h Prototype file for AMCC5933 driver.
trace.h Header file for the debug tracing related function defintions and macros for AMCC5933 driver.
Transfer.c File for AMCC5933 driver which deals with transfer releated DDI(ISR's, DPC's, DMA).
amcc5933.inx
Installation file for installing the driver.
This file is used to generate amcc5933.inf.
makefile Standard DDK build environment makefile.
makefile.inc Makefile extensions to handle inx/inf files.
sources Generic file for building the code sample
Application:
RxTest:
RxTest.c Receieve Test file for the AMCC5933 driver.
makefile Standard DDK build environment makefile.
sources Generic file for building the code sample.
TxTest:
TxTest.c Transmit Test file for the AMCC5933 driver.
makefile Standard DDK build environment makefile.
sources Generic file for building the code sample.
|
|
© 2002 Microsoft Corporation


Metropolitan Electricity Authority.
Advanced Info Service Public Company Limited
bergamot shop
Metropolitan Waterworks Authority.
True Corporation Public Company Limited (TRUE)
Cool gadget & mobile accessories
CAT Telecom Public Company Limited.
Total Access Communication Public Company Limited.
For people who love a unique story.


Bill to establish North Central Development Commission scales first reading in Senate
by https://www.facebook.com/CheerfulpraiseSanni Onogu, Abuja
A Bill to establish the North Central Development Commission (NCDC) on Tuesday scaled first reading in Senate.
The Bill titled: “North Central Development Commission (Est, etc) Bill 2019” was sponsored by the Senator representing Niger East Senatorial District, Mohammed Sani Musa.
The NCDC bill represents the third bill seeking to create a development commission in some geopolitical zones of the country in the last one week.
Others include the South East Development Commission Bill and the South West Development Commission Bill.
Read Also: Senate swears-in Senator Dambaba
The Niger Delta Development Commission (NDDC) and the North East Development Commission was established in year 2000 and 2017 respectively through the Acts of the National Assembly.
With the presentation of the NCDC Bill by the Senate on Tuesday, only the North West region is yet to present such Bill.


Bluetooth Devices
| UUID | Seen | Vers | Address | RSSI | Name | ManuF | Type |
|---|---|---|---|---|---|---|---|
| Loading... |
Device Properties ( No Device )
Device Details
| Detail Name | Detail Property |
|---|---|
| Please select device from list |
| UUID | Seen | Vers | Address | RSSI | Name | ManuF | Type |
|---|---|---|---|---|---|---|---|
| Loading... |
| Detail Name | Detail Property |
|---|---|
| Please select device from list |


! ! Twin dice roller script DiceRoller div Screen div Dice div Dot variable NDice variable M variable N variable D variable Index variable Row variable Dots variable Patterns variable Left variable Top put 2 into NDice set style `.ec-dice` to `{width:100px;height:100px;margin:20px;` cat `background:yellow;border:1px solid black;display:inline-block;` cat `border-radius:10%;position:relative}` set style `.ec-dot` to `{width:20px;height:20;position:absolute;` cat `background:black;border-radius:50%}` set Patterns to 40 40 0 0 0 0 0 0 0 0 0 0 10 40 70 40 0 0 0 0 0 0 0 0 10 40 40 40 70 40 0 0 0 0 0 0 10 10 70 10 10 70 70 70 0 0 0 0 10 10 70 10 10 70 70 70 40 40 0 0 10 10 10 70 40 10 40 70 70 10 70 70 create Screen set the style of Screen to `padding:1em` set the elements of Dice to NDice Redraw: put 0 into M while M is less than 10 begin put 0 into N while N is less than NDice begin index Dice to N remove element Dice create Dice in Screen set the class of Dice to `ec-dice` gosub to RandomiseDots add 1 to N end wait 10 ticks add 1 to M end on click Dice go to Redraw stop RandomiseDots: put random 6 into Dots multiply Dots by 12 giving Row put 0 into D while D is less than 12 begin add D to Row giving Index index Patterns to Index put Patterns into Top add 1 to D if Top is not 0 begin add 1 to Index index Patterns to Index put Patterns into Left create Dot in Dice set the class of Dot to `ec-dot` set style `top` of Dot to Top set style `left` of Dot to Left on click Dot go to Redraw end add 1 to D end return


You don't need JavaScript to use Friendly Tree View. If you build HTML and apply the right CSS classes, it just works!


Create an account
Username:
Required. 150 characters or fewer. Letters, digits and @/./+/-/_ only.
Email:
Required. A valid email address
First name:
Optional. Max # of characters: 30
Last name:
Optional. Max # of characters: 30
Password:
Simple Rules:
Password Confirmation:
Enter the same password as before, for verification.
Permisson Code:
Enter the permission code given to you by the system administrator
Back to the Main Page
Contact Us
|
About Us


Holi
Holi is a popular ancient Hindu festival, also known as the "festival of love", the "festival of colours", and the "festival of spring". The festival celebrates the eternal and divine love of Radha and Krishna. It also signifies the triumph of good over evil. It originated and is predominantly celebrated in India, but has also spread to other regions of Asia and parts of the Western world through the diaspora from the Indian subcontinent.


SimplyE is The New York Public Library's free e-reader app, giving library cardholders the ability to browse, borrow and read over 120,000 e-book titles in just a few easy steps. The app was developed with the Library's overall mission in mind - to ensure that its collections and information in all formats is accessible to all.
T he New York Public Library is a free provider of education and information for the people of New York and beyond. With 92 locations—including research and branch libraries—throughout the Bronx, Manhattan, and Staten Island, the Library offers free materials, computer access, classes, exhibitions, programming and more to everyone from toddlers to scholars, and has seen record numbers of attendance and circulation in recent years. The New York Public Library serves more than 18 million patrons who come through its doors annually and millions more around the globe who use its resources at www.nypl.org. To offer this wide array of free programming, The New York Public Library relies on both public and private funding. Learn more about how to support the Library at nypl.org/support.


Home
About
Products
Blog
Contact
Contact Us
First name:
Last name:
E-mail:
Message
Enter text here...
We'll get back to you ASAP.


Program Version:EnergyPlus, Version 9.0.1-bb7ca4f0da, YMD=2021.02.21 23:23
Tabular Output Report in Format: HTML
Building: Building
Environment: LAB_PART1 (01-01:31-12) ** TORINO - ITA IWEC Data WMO#=160590
Simulation Timestamp: 2021-02-21 23:23:14
Report: Annual Building Utility Performance Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Values gathered over 8760.00 hours| Total Energy [kWh] | Energy Per Total Building Area [kWh/m2] | Energy Per Conditioned Building Area [kWh/m2] | |
| Total Site Energy | 99368.75 | 96.39 | 96.39 |
| Net Site Energy | 99368.75 | 96.39 | 96.39 |
| Total Source Energy | 306574.97 | 297.39 | 297.39 |
| Net Source Energy | 306574.97 | 297.39 | 297.39 |
| Site=>Source Conversion Factor | |
| Electricity | 3.167 |
| Natural Gas | 1.084 |
| District Cooling | 1.056 |
| District Heating | 3.613 |
| Steam | 0.250 |
| Gasoline | 1.050 |
| Diesel | 1.050 |
| Coal | 1.050 |
| Fuel Oil #1 | 1.050 |
| Fuel Oil #2 | 1.050 |
| Propane | 1.050 |
| Other Fuel 1 | 1.000 |
| Other Fuel 2 | 1.000 |
| Area [m2] | |
| Total Building Area | 1030.89 |
| Net Conditioned Building Area | 1030.89 |
| Unconditioned Building Area | 0.00 |
| Electricity [kWh] | Natural Gas [kWh] | Additional Fuel [kWh] | District Cooling [kWh] | District Heating [kWh] | Water [m3] | |
| Heating | 0.00 | 0.00 | 0.00 | 0.00 | 30897.37 | 0.00 |
| Cooling | 0.00 | 0.00 | 0.00 | 11762.73 | 0.00 | 0.00 |
| Interior Lighting | 24979.35 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Exterior Lighting | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Interior Equipment | 25190.09 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Exterior Equipment | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Fans | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Pumps | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Heat Rejection | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Humidification | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Heat Recovery | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Water Systems | 0.00 | 0.00 | 0.00 | 0.00 | 6539.22 | 102.40 |
| Refrigeration | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Generators | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Total End Uses | 50169.43 | 0.00 | 0.00 | 11762.73 | 37436.58 | 102.40 |
| Subcategory | Electricity [kWh] | Natural Gas [kWh] | Additional Fuel [kWh] | District Cooling [kWh] | District Heating [kWh] | Water [m3] | |
| Heating | General | 0.00 | 0.00 | 0.00 | 0.00 | 30897.37 | 0.00 |
| Cooling | General | 0.00 | 0.00 | 0.00 | 11762.73 | 0.00 | 0.00 |
| Interior Lighting | General | 24979.35 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Exterior Lighting | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Interior Equipment | ELECTRIC EQUIPMENT#Block1:Zone3#05 | 2081.05 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| ELECTRIC EQUIPMENT#Block1:Zone1#05 | 15161.05 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| ELECTRIC EQUIPMENT#Block1:Zone4#05 | 5008.57 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| ELECTRIC EQUIPMENT#Block1:Zone2#05 | 2939.42 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| Exterior Equipment | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Fans | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Pumps | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Heat Rejection | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Humidification | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Heat Recovery | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Water Systems | DHW Block1:Zone1 | 0.00 | 0.00 | 0.00 | 0.00 | 6539.22 | 102.40 |
| Refrigeration | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Generators | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Electricity Intensity [kWh/m2] | Natural Gas Intensity [kWh/m2] | Additional Fuel Intensity [kWh/m2] | District Cooling Intensity [kWh/m2] | District Heating Intensity [kWh/m2] | Water Intensity [m3/m2] | |
| Lighting | 24.23 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| HVAC | 0.00 | 0.00 | 0.00 | 11.41 | 36.31 | 0.10 |
| Other | 24.44 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Total | 48.67 | 0.00 | 0.00 | 11.41 | 36.31 | 0.10 |
| Electricity Intensity [kWh/m2] | Natural Gas Intensity [kWh/m2] | Additional Fuel Intensity [kWh/m2] | District Cooling Intensity [kWh/m2] | District Heating Intensity [kWh/m2] | Water Intensity [m3/m2] | |
| Lighting | 24.23 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| HVAC | 0.00 | 0.00 | 0.00 | 11.41 | 36.31 | 0.10 |
| Other | 24.44 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Total | 48.67 | 0.00 | 0.00 | 11.41 | 36.31 | 0.10 |
| Electricity [kWh] | Percent Electricity [%] | |
| Fuel-Fired Power Generation | 0.000 | 0.00 |
| High Temperature Geothermal* | 0.000 | 0.00 |
| Photovoltaic Power | 0.000 | 0.00 |
| Wind Power | 0.000 | 0.00 |
| Power Conversion | 0.000 | 0.00 |
| Net Decrease in On-Site Storage | 0.000 | 0.00 |
| Total On-Site Electric Sources | 0.000 | 0.00 |
| Electricity Coming From Utility | 50169.434 | 100.00 |
| Surplus Electricity Going To Utility | 0.000 | 0.00 |
| Net Electricity From Utility | 50169.434 | 100.00 |
| Total On-Site and Utility Electric Sources | 50169.434 | 100.00 |
| Total Electricity End Uses | 50169.434 | 100.00 |
| Heat [kWh] | Percent Heat [%] | |
| Water-Side Heat Recovery | 0.00 | |
| Air to Air Heat Recovery for Cooling | 0.00 | |
| Air to Air Heat Recovery for Heating | 0.00 | |
| High-Temperature Geothermal* | 0.00 | |
| Solar Water Thermal | 0.00 | |
| Solar Air Thermal | 0.00 | |
| Total On-Site Thermal Sources | 0.00 |
| Water [m3] | Percent Water [%] | |
| Rainwater Collection | 0.00 | 0.00 |
| Condensate Collection | 0.00 | 0.00 |
| Groundwater Well | 0.00 | 0.00 |
| Total On Site Water Sources | 0.00 | 0.00 |
| - | - | - |
| Initial Storage | 0.00 | 0.00 |
| Final Storage | 0.00 | 0.00 |
| Change in Storage | 0.00 | 0.00 |
| - | - | - |
| Water Supplied by Utility | 102.40 | 100.00 |
| - | - | - |
| Total On Site, Change in Storage, and Utility Water Sources | 102.40 | 100.00 |
| Total Water End Uses | 102.40 | 100.00 |
| Degrees [deltaC] | |
| Tolerance for Zone Heating Setpoint Not Met Time | 1.11 |
| Tolerance for Zone Cooling Setpoint Not Met Time | 1.11 |
| Facility [Hours] | |
| Time Setpoint Not Met During Occupied Heating | 0.00 |
| Time Setpoint Not Met During Occupied Cooling | 1.50 |
| Time Not Comfortable Based on Simple ASHRAE 55-2004 | 3178.50 |
Table of Contents
TopReport: Input Verification and Results Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
General| Value | |
| Program Version and Build | EnergyPlus, Version 9.0.1-bb7ca4f0da, YMD=2021.02.21 23:23 |
| RunPeriod | LAB_PART1 (01-01:31-12) |
| Weather File | TORINO - ITA IWEC Data WMO#=160590 |
| Latitude [deg] | 45.22 |
| Longitude [deg] | 7.65 |
| Elevation [m] | 287.00 |
| Time Zone | 1.00 |
| North Axis Angle [deg] | 270.00 |
| Rotation for Appendix G [deg] | 0.00 |
| Hours Simulated [hrs] | 8760.00 |
| Total | North (315 to 45 deg) | East (45 to 135 deg) | South (135 to 225 deg) | West (225 to 315 deg) | |
| Gross Wall Area [m2] | 483.83 | 84.28 | 157.64 | 84.28 | 157.64 |
| Above Ground Wall Area [m2] | 483.83 | 84.28 | 157.64 | 84.28 | 157.64 |
| Window Opening Area [m2] | 10.00 | 2.14 | 4.17 | 2.14 | 1.56 |
| Gross Window-Wall Ratio [%] | 2.07 | 2.54 | 2.64 | 2.54 | 0.99 |
| Above Ground Window-Wall Ratio [%] | 2.07 | 2.54 | 2.64 | 2.54 | 0.99 |
| Total | North (315 to 45 deg) | East (45 to 135 deg) | South (135 to 225 deg) | West (225 to 315 deg) | |
| Gross Wall Area [m2] | 483.83 | 84.28 | 157.64 | 84.28 | 157.64 |
| Above Ground Wall Area [m2] | 483.83 | 84.28 | 157.64 | 84.28 | 157.64 |
| Window Opening Area [m2] | 10.00 | 2.14 | 4.17 | 2.14 | 1.56 |
| Gross Window-Wall Ratio [%] | 2.07 | 2.54 | 2.64 | 2.54 | 0.99 |
| Above Ground Window-Wall Ratio [%] | 2.07 | 2.54 | 2.64 | 2.54 | 0.99 |
| Total | |
| Gross Roof Area [m2] | 1084.53 |
| Skylight Area [m2] | 0.00 |
| Skylight-Roof Ratio [%] | 0.00 |
| Area [m2] | Conditioned (Y/N) | Part of Total Floor Area (Y/N) | Volume [m3] | Multipliers | Above Ground Gross Wall Area [m2] | Underground Gross Wall Area [m2] | Window Glass Area [m2] | Opening Area [m2] | Lighting [W/m2] | People [m2 per person] | Plug and Process [W/m2] | |
| BLOCK1:ZONE3 | 158.47 | Yes | Yes | 554.65 | 1.00 | 94.08 | 0.00 | 1.94 | 2.44 | 5.0000 | 50.90 | 2.1600 |
| BLOCK1:ZONE1 | 267.18 | Yes | Yes | 935.14 | 1.00 | 133.64 | 0.00 | 0.74 | 0.89 | 15.0000 | 42.19 | 30.2800 |
| BLOCK1:ZONE4 | 381.40 | Yes | Yes | 1334.91 | 1.00 | 148.22 | 0.00 | 3.05 | 3.90 | 5.0000 | 50.90 | 2.1600 |
| BLOCK1:ZONE2 | 223.84 | Yes | Yes | 783.43 | 1.00 | 107.90 | 0.00 | 2.17 | 2.78 | 5.0000 | 50.90 | 2.1600 |
| Total | 1030.89 | 3608.12 | 483.83 | 0.00 | 7.90 | 10.00 | 7.5918 | 48.31 | 9.4480 | |||
| Conditioned Total | 1030.89 | 3608.12 | 483.83 | 0.00 | 7.90 | 10.00 | 7.5918 | 48.31 | 9.4480 | |||
| Unconditioned Total | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||||||
| Not Part of Total | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
Report: Demand End Use Components Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
End Uses| Electricity [W] | Natural Gas [W] | Propane [W] | District Cooling [W] | District Heating [W] | Water [m3/s] | |
| Time of Peak | 01-JAN-09:30 | - | - | 22-JUL-16:30 | 05-JAN-05:30 | 15-JAN-07:30 |
| Heating | 0.00 | 0.00 | 0.00 | 0.00 | 35777.26 | 0.00 |
| Cooling | 0.00 | 0.00 | 0.00 | 32182.12 | 0.00 | 0.00 |
| Interior Lighting | 7826.28 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Exterior Lighting | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Interior Equipment | 9739.88 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Exterior Equipment | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Fans | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Pumps | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Heat Rejection | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Humidification | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Heat Recovery | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Water Systems | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Refrigeration | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Generators | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Total End Uses | 17566.16 | 0.00 | 0.00 | 32182.12 | 35777.26 | 0.00 |
| Subcategory | Electricity [W] | Natural Gas [W] | Propane [W] | District Cooling [W] | District Heating [W] | Water [m3/s] | |
| Heating | General | 0.00 | 0.00 | 0.00 | 0.00 | 35777.26 | 0.00 |
| Cooling | General | 0.00 | 0.00 | 0.00 | 32182.12 | 0.00 | 0.00 |
| Interior Lighting | General | 7826.28 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Exterior Lighting | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Interior Equipment | ELECTRIC EQUIPMENT#Block1:Zone3#05 | 342.30 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| ELECTRIC EQUIPMENT#Block1:Zone1#05 | 8090.26 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| ELECTRIC EQUIPMENT#Block1:Zone4#05 | 823.83 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| ELECTRIC EQUIPMENT#Block1:Zone2#05 | 483.49 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| Exterior Equipment | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Fans | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Pumps | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Heat Rejection | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Humidification | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Heat Recovery | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Water Systems | DHW Block1:Zone1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Refrigeration | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Generators | General | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
Report: Component Sizing Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
ZoneHVAC:IdealLoadsAirSystem| Design Size Maximum Heating Air Flow Rate [m3/s] | Design Size Maximum Sensible Heating Capacity [W] | Design Size Maximum Cooling Air Flow Rate [m3/s] | Design Size Maximum Total Cooling Capacity [W] | |
| BLOCK1:ZONE3 IDEAL LOADS AIR | 0.276929 | 5672.92 | 0.182022 | 4805.34 |
| BLOCK1:ZONE1 IDEAL LOADS AIR | 0.466099 | 9548.44 | 0.767639 | 16689.97 |
| BLOCK1:ZONE4 IDEAL LOADS AIR | 0.625382 | 12812.16 | 0.413625 | 11663.33 |
| BLOCK1:ZONE2 IDEAL LOADS AIR | 0.378000 | 7743.74 | 0.244129 | 6546.68 |
Report: Adaptive Comfort Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Time Not Meeting the Adaptive Comfort Models during Occupied Hours| ASHRAE55 90% Acceptability Limits [Hours] | ASHRAE55 80% Acceptability Limits [Hours] | CEN15251 Category I Acceptability Limits [Hours] | CEN15251 Category II Acceptability Limits [Hours] | CEN15251 Category III Acceptability Limits [Hours] |
Report: Climatic Data Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
SizingPeriod:DesignDay| Maximum Dry Bulb [C] | Daily Temperature Range [deltaC] | Humidity Value | Humidity Type | Wind Speed [m/s] | Wind Direction | |
| SUMMER DESIGN DAY IN LAB_PART1 (01-01:31-12) JUL | 32.10 | 11.00 | 22.80 | Wetbulb [C] | 0.00 | 0.00 |
| SUMMER DESIGN DAY IN LAB_PART1 (01-01:31-12) AUG | 32.80 | 11.50 | 23.50 | Wetbulb [C] | 0.00 | 0.00 |
| SUMMER DESIGN DAY IN LAB_PART1 (01-01:31-12) SEP | 29.00 | 11.50 | 20.20 | Wetbulb [C] | 0.00 | 0.00 |
| WINTER DESIGN DAY IN LAB_PART1 (01-01:31-12) | -5.90 | 0.00 | -5.90 | Wetbulb [C] | 8.50 | 0.00 |
| Value | |
| None |
Report: Envelope Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Opaque Exterior| Construction | Reflectance | U-Factor with Film [W/m2-K] | U-Factor no Film [W/m2-K] | Gross Area [m2] | Net Area [m2] | Azimuth [deg] | Tilt [deg] | Cardinal Direction | |
| BLOCK1:ZONE3_WALL_3_0_0 | PROJECT WALL | 0.30 | 0.353 | 0.372 | 59.04 | 57.48 | 270.00 | 90.00 | W |
| BLOCK1:ZONE3_WALL_4_0_0 | PROJECT WALL | 0.30 | 0.353 | 0.372 | 35.04 | 34.15 | 180.00 | 90.00 | S |
| BLOCK1:ZONE3_GROUNDFLOOR_0_0_0 | PROJECT GROUND FLOOR | 0.40 | 0.356 | 0.378 | 168.87 | 168.87 | 270.00 | 180.00 | |
| BLOCK1:ZONE3_ROOF_1_0_0 | PROJECT FLAT ROOF | 0.15 | 0.109 | 0.111 | 168.87 | 168.87 | 90.00 | 0.00 | |
| BLOCK1:ZONE1_WALL_2_0_0 | PROJECT WALL | 0.30 | 0.353 | 0.372 | 35.04 | 34.15 | 0.00 | 90.00 | N |
| BLOCK1:ZONE1_WALL_3_0_0 | PROJECT WALL | 0.30 | 0.353 | 0.372 | 98.60 | 92.76 | 270.00 | 90.00 | W |
| BLOCK1:ZONE1_GROUNDFLOOR_0_0_0 | PROJECT GROUND FLOOR | 0.40 | 0.356 | 0.378 | 282.01 | 282.01 | 270.00 | 180.00 | |
| BLOCK1:ZONE1_ROOF_1_0_0 | PROJECT FLAT ROOF | 0.15 | 0.109 | 0.111 | 282.01 | 282.01 | 90.00 | 0.00 | |
| BLOCK1:ZONE4_WALL_5_0_0 | PROJECT WALL | 0.30 | 0.353 | 0.372 | 49.24 | 47.99 | 180.00 | 90.00 | S |
| BLOCK1:ZONE4_WALL_6_0_0 | PROJECT WALL | 0.30 | 0.353 | 0.372 | 98.98 | 96.34 | 90.00 | 90.00 | E |
| BLOCK1:ZONE4_GROUNDFLOOR_0_0_0 | PROJECT GROUND FLOOR | 0.40 | 0.356 | 0.378 | 397.87 | 397.87 | 270.00 | 180.00 | |
| BLOCK1:ZONE4_ROOF_1_0_0 | PROJECT FLAT ROOF | 0.15 | 0.109 | 0.111 | 397.87 | 397.87 | 90.00 | 0.00 | |
| BLOCK1:ZONE2_WALL_2_0_0 | PROJECT WALL | 0.30 | 0.353 | 0.372 | 49.24 | 47.99 | 0.00 | 90.00 | N |
| BLOCK1:ZONE2_WALL_5_0_0 | PROJECT WALL | 0.30 | 0.353 | 0.372 | 58.66 | 57.13 | 90.00 | 90.00 | E |
| BLOCK1:ZONE2_GROUNDFLOOR_0_0_0 | PROJECT GROUND FLOOR | 0.40 | 0.356 | 0.378 | 235.78 | 235.78 | 270.00 | 180.00 | |
| BLOCK1:ZONE2_ROOF_1_0_0 | PROJECT FLAT ROOF | 0.15 | 0.109 | 0.111 | 235.78 | 235.78 | 90.00 | 0.00 |
| Construction | Glass Area [m2] | Frame Area [m2] | Divider Area [m2] | Area of One Opening [m2] | Area of Multiplied Openings [m2] | Glass U-Factor [W/m2-K] | Glass SHGC | Glass Visible Transmittance | Frame Conductance [W/m2-K] | Divider Conductance [W/m2-K] | Shade Control | Parent Surface | Azimuth [deg] | Tilt [deg] | Cardinal Direction | |
| BLOCK1:ZONE3_WALL_3_0_0_0_0_0_WIN | 1001 | 0.37 | 0.12 | 0.03 | 0.52 | 1.56 | 2.132 | 0.609 | 0.696 | 9.500 | 9.500 | No | BLOCK1:ZONE3_WALL_3_0_0 | 270.00 | 90.00 | W |
| BLOCK1:ZONE3_WALL_4_0_0_0_0_0_WIN | 1001 | 0.71 | 0.15 | 0.03 | 0.89 | 0.89 | 2.132 | 0.609 | 0.696 | 9.500 | 9.500 | No | BLOCK1:ZONE3_WALL_4_0_0 | 180.00 | 90.00 | S |
| BLOCK1:ZONE1_WALL_2_0_0_0_0_0_WIN | 1001 | 0.71 | 0.15 | 0.03 | 0.89 | 0.89 | 2.132 | 0.609 | 0.696 | 9.500 | 9.500 | No | BLOCK1:ZONE1_WALL_2_0_0 | 0.00 | 90.00 | N |
| BLOCK1:ZONE4_WALL_5_0_0_0_0_0_WIN | 1001 | 0.47 | 0.13 | 0.03 | 0.63 | 1.25 | 2.132 | 0.609 | 0.696 | 9.500 | 9.500 | No | BLOCK1:ZONE4_WALL_5_0_0 | 180.00 | 90.00 | S |
| BLOCK1:ZONE4_WALL_6_0_0_0_0_0_WIN | 1001 | 0.38 | 0.12 | 0.03 | 0.53 | 2.65 | 2.132 | 0.609 | 0.696 | 9.500 | 9.500 | No | BLOCK1:ZONE4_WALL_6_0_0 | 90.00 | 90.00 | E |
| BLOCK1:ZONE2_WALL_2_0_0_0_0_0_WIN | 1001 | 0.47 | 0.13 | 0.03 | 0.63 | 1.25 | 2.132 | 0.609 | 0.696 | 9.500 | 9.500 | No | BLOCK1:ZONE2_WALL_2_0_0 | 0.00 | 90.00 | N |
| BLOCK1:ZONE2_WALL_5_0_0_0_0_0_WIN | 1001 | 0.36 | 0.12 | 0.03 | 0.51 | 1.52 | 2.132 | 0.609 | 0.696 | 9.500 | 9.500 | No | BLOCK1:ZONE2_WALL_5_0_0 | 90.00 | 90.00 | E |
| Total or Average | 10.00 | 2.132 | 0.609 | 0.696 | ||||||||||||
| North Total or Average | 2.14 | 2.132 | 0.609 | 0.696 | ||||||||||||
| Non-North Total or Average | 7.86 | 2.132 | 0.609 | 0.696 |
| Construction | Area of One Opening [m2] | Area of Openings [m2] | Glass U-Factor [W/m2-K] | Glass SHGC | Glass Visible Transmittance | Parent Surface | |
| Total or Average | 0.00 | - | - | - |
| Construction | U-Factor with Film [W/m2-K] | U-Factor no Film [W/m2-K] | Gross Area [m2] | Parent Surface | |
| BLOCK1:ZONE1_WALL_3_0_0_0_0_0_DOOR | PROJECT EXTERNAL DOOR | 2.995 | 5.429 | 5.84 | BLOCK1:ZONE1_WALL_3_0_0 |
Report: Lighting Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Interior Lighting| Zone | Lighting Power Density [W/m2] | Zone Area [m2] | Total Power [W] | End Use Subcategory | Schedule Name | Scheduled Hours/Week [hr] | Hours/Week > 1% [hr] | Full Load Hours/Week [hr] | Return Air Fraction | Conditioned (Y/N) | Consumption [kWh] | |
| BLOCK1:ZONE3 | BLOCK1:ZONE3 | 5.0000 | 158.47 | 792.36 | General | DWELL_DOMCOMMONAREAS_LIGHT | 74.03 | 74.03 | 74.03 | 0.0000 | Y | 3058.50 |
| BLOCK1:ZONE1 | BLOCK1:ZONE1 | 15.0000 | 267.18 | 4007.73 | General | DWELL_DOMKITCHEN_LIGHT | 49.00 | 49.00 | 49.00 | 0.0000 | Y | 10239.75 |
| BLOCK1:ZONE4 | BLOCK1:ZONE4 | 5.0000 | 381.40 | 1907.01 | General | DWELL_DOMCOMMONAREAS_LIGHT | 74.03 | 74.03 | 74.03 | 0.0000 | Y | 7361.07 |
| BLOCK1:ZONE2 | BLOCK1:ZONE2 | 5.0000 | 223.84 | 1119.18 | General | DWELL_DOMCOMMONAREAS_LIGHT | 74.03 | 74.03 | 74.03 | 0.0000 | Y | 4320.04 |
| Interior Lighting Total | 7.5918 | 1030.89 | 7826.28 | 24979.37 |
| Zone | Control Name | Daylighting Method | Control Type | Fraction Controlled | Lighting Installed in Zone [W] | Lighting Controlled [W] | |
| None |
| Total Watts | Astronomical Clock/Schedule | Schedule Name | Scheduled Hours/Week [hr] | Hours/Week > 1% [hr] | Full Load Hours/Week [hr] | Consumption [kWh] | |
| Exterior Lighting Total | 0.00 | 0.00 |
Report: Equipment Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Central Plant| Type | Nominal Capacity [W] | Nominal Efficiency [W/W] | IPLV in SI Units [W/W] | IPLV in IP Units [Btu/W-h] | |
| None |
| Type | Design Coil Load [W] | Nominal Total Capacity [W] | Nominal Sensible Capacity [W] | Nominal Latent Capacity [W] | Nominal Sensible Heat Ratio | Nominal Efficiency [W/W] | Nominal Coil UA Value [W/C] | Nominal Coil Surface Area [m2] | |
| None |
| DX Cooling Coil Type | Standard Rated Net Cooling Capacity [W] | Standard Rated Net COP [W/W] | EER [Btu/W-h] | SEER [Btu/W-h] | IEER [Btu/W-h] | |
| None |
| DX Cooling Coil Type | Rated Net Cooling Capacity Test A [W] | Rated Electric Power Test A [W] | Rated Net Cooling Capacity Test B [W] | Rated Electric Power Test B [W] | Rated Net Cooling Capacity Test C [W] | Rated Electric Power Test C [W] | Rated Net Cooling Capacity Test D [W] | Rated Electric Power Test D [W] | |
| None |
| DX Heating Coil Type | High Temperature Heating (net) Rating Capacity [W] | Low Temperature Heating (net) Rating Capacity [W] | HSPF [Btu/W-h] | Region Number | |
| None |
| Type | Design Coil Load [W] | Nominal Total Capacity [W] | Nominal Efficiency [W/W] | |
| None |
| Type | Total Efficiency [W/W] | Delta Pressure [pa] | Max Air Flow Rate [m3/s] | Rated Electric Power [W] | Rated Power Per Max Air Flow Rate [W-s/m3] | Motor Heat In Air Fraction | Fan Energy Index | End Use | Design Day Name for Fan Sizing Peak | Date/Time for Fan Sizing Peak | |
| None |
| Type | Control | Head [pa] | Water Flow [m3/s] | Electric Power [W] | Power Per Water Flow Rate [W-s/m3] | Motor Efficiency [W/W] | |
| None |
| Type | Storage Volume [m3] | Input [W] | Thermal Efficiency [W/W] | Recovery Efficiency [W/W] | Energy Factor | |
| None |
Report: HVAC Sizing Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Zone Sensible Cooling| Calculated Design Load [W] | User Design Load [W] | User Design Load per Area [W/m2] | Calculated Design Air Flow [m3/s] | User Design Air Flow [m3/s] | Design Day Name | Date/Time Of Peak {TIMESTAMP} | Thermostat Setpoint Temperature at Peak Load [C] | Indoor Temperature at Peak Load [C] | Indoor Humidity Ratio at Peak Load [kgWater/kgAir] | Outdoor Temperature at Peak Load [C] | Outdoor Humidity Ratio at Peak Load [kgWater/kgAir] | Minimum Outdoor Air Flow Rate [m3/s] | Heat Gain Rate from DOAS [W] | |
| BLOCK1:ZONE3 | 2440.41 | 2806.47 | 17.71 | 0.158 | 0.182 | SUMMER DESIGN DAY IN LAB_PART1 (01-01:31-12) JUL | 7/15 17:00:00 | 25.00 | 25.00 | 0.01035 | 30.56 | 0.01425 | 0.031 | 0.00 |
| BLOCK1:ZONE1 | 10283.06 | 11825.52 | 44.26 | 0.668 | 0.768 | SUMMER DESIGN DAY IN LAB_PART1 (01-01:31-12) JUL | 7/15 09:00:00 | 25.00 | 24.99 | 0.00931 | 26.05 | 0.01425 | 0.076 | 0.00 |
| BLOCK1:ZONE4 | 5545.46 | 6377.28 | 16.72 | 0.360 | 0.414 | SUMMER DESIGN DAY IN LAB_PART1 (01-01:31-12) AUG | 8/15 17:00:00 | 25.00 | 25.00 | 0.01079 | 31.19 | 0.01505 | 0.075 | 0.00 |
| BLOCK1:ZONE2 | 3273.10 | 3764.06 | 16.82 | 0.212 | 0.244 | SUMMER DESIGN DAY IN LAB_PART1 (01-01:31-12) JUL | 7/15 17:00:00 | 25.00 | 25.00 | 0.01046 | 30.56 | 0.01425 | 0.044 | 0.00 |
| Calculated Design Load [W] | User Design Load [W] | User Design Load per Area [W/m2] | Calculated Design Air Flow [m3/s] | User Design Air Flow [m3/s] | Design Day Name | Date/Time Of Peak {TIMESTAMP} | Thermostat Setpoint Temperature at Peak Load [C] | Indoor Temperature at Peak Load [C] | Indoor Humidity Ratio at Peak Load [kgWater/kgAir] | Outdoor Temperature at Peak Load [C] | Outdoor Humidity Ratio at Peak Load [kgWater/kgAir] | Minimum Outdoor Air Flow Rate [m3/s] | Heat Gain Rate from DOAS [W] | |
| BLOCK1:ZONE3 | 4538.33 | 5672.92 | 35.80 | 0.222 | 0.277 | WINTER DESIGN DAY IN LAB_PART1 (01-01:31-12) | 1/15 24:00:00 | 18.00 | 17.98 | 0.01101 | -5.90 | 0.00237 | 0.031 | 0.00 |
| BLOCK1:ZONE1 | 7638.75 | 9548.44 | 35.74 | 0.373 | 0.466 | WINTER DESIGN DAY IN LAB_PART1 (01-01:31-12) | 1/15 24:00:00 | 18.00 | 17.97 | 0.01100 | -5.90 | 0.00237 | 0.076 | 0.00 |
| BLOCK1:ZONE4 | 10249.73 | 12812.16 | 33.59 | 0.500 | 0.625 | WINTER DESIGN DAY IN LAB_PART1 (01-01:31-12) | 1/15 24:00:00 | 18.00 | 17.97 | 0.01081 | -5.90 | 0.00237 | 0.075 | 0.00 |
| BLOCK1:ZONE2 | 6194.99 | 7743.74 | 34.60 | 0.302 | 0.378 | WINTER DESIGN DAY IN LAB_PART1 (01-01:31-12) | 1/15 24:00:00 | 18.00 | 17.97 | 0.01090 | -5.90 | 0.00237 | 0.044 | 0.00 |
| Calculated cooling [m3/s] | User cooling [m3/s] | Calculated heating [m3/s] | User heating [m3/s] | Adjusted cooling [m3/s] | Adjusted heating [m3/s] | Adjusted main [m3/s] | Calculated Heating Air Flow Ratio [] | User Heating Air Flow Ratio [] | |
| None |
| Previous Design Volume Flow Rate [m3/s] | Algorithm Volume Flow Rate [m3/s] | Coincident Design Volume Flow Rate [m3/s] | Coincident Size Adjusted | Peak Sizing Period Name | Peak Day into Period {TIMESTAMP}[day] | Peak Hour Of Day {TIMESTAMP}[hr] | Peak Step Start Minute {TIMESTAMP}[min] | |
| None |
| Coil Type | HVAC Type | HVAC Name | Coil Final Gross Total Capacity [W] | Coil Final Gross Sensible Capacity [W] | Coil Final Reference Air Volume Flow Rate [m3/s] | Coil Final Reference Plant Fluid Volume Flow Rate [m3/s] | Coil U-value Times Area Value [W/K] | Design Day Name at Sensible Ideal Loads Peak | Date/Time at Sensible Ideal Loads Peak | Design Day Name at Air Flow Ideal Loads Peak | Date/Time at Air Flow Ideal Loads Peak | Coil Total Capacity at Ideal Loads Peak [W] | Coil Sensible Capacity at Ideal Loads Peak [W] | Coil Air Volume Flow Rate at Ideal Loads Peak [m3/s] | Coil Entering Air Drybulb at Ideal Loads Peak [C] | Coil Entering Air Wetbulb at Ideal Loads Peak [C] | Coil Entering Air Humidity Ratio at Ideal Loads Peak [KGWATER/KGDRYAIR] | Coil Leaving Air Drybulb at Ideal Loads Peak [C] | Coil Leaving Air Wetbulb at Ideal Loads Peak [C] | Coil Leaving Air Humidity Ratio at Ideal Loads Peak [C] | Outdoor Air Drybulb at Ideal Loads Peak [C] | Outdoor Air Humidity Ratio at Ideal Loads Peak [KGWATER/KGDRYAIR] | Outdoor Air Wetbulb at Ideal Loads Peak [C] | Outdoor Air Flow Percentage at Ideal Loads Peak [%] | Zone Air Drybulb at Ideal Loads Peak [C] | Zone Air Humidity Ratio at Ideal Loads Peak [KGWATER/KGDRYAIR] | Zone Air Relative Humidity at Ideal Loads Peak [%] | Zone Sensible Heat Gain at Ideal Loads Peak [W] | Zone Latent Heat Gain at Ideal Loads Peak [W] | Coil Total Capacity at Rating Conditions [W] | Coil Sensible Capacity at Rating Conditions [W] | |
| None |
Report: System Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Economizer| High Limit Shutoff Control | Minimum Outdoor Air [m3/s] | Maximum Outdoor Air [m3/s] | Return Air Temp Limit | Return Air Enthalpy Limit | Outdoor Air Temperature Limit [C] | Outdoor Air Enthalpy Limit [C] | |
| None |
| Controller:MechanicalVentilation Name | Outdoor Air Per Person [m3/s-person] | Outdoor Air Per Area [m3/s-m2] | Outdoor Air Per Zone [m3/s] | Outdoor Air ACH [ach] | Outdoor Air Method | Outdoor Air Schedule Name | Air Distribution Effectiveness in Cooling Mode | Air Distribution Effectiveness in Heating Mode | Air Distribution Effectiveness Schedule Name | |
| None |
| Winter Clothes [hr] | Summer Clothes [hr] | Summer or Winter Clothes [hr] | |
| BLOCK1:ZONE3 | 3221.00 | 3533.50 | 2951.50 |
| BLOCK1:ZONE1 | 1923.50 | 1804.00 | 1270.00 |
| BLOCK1:ZONE4 | 3211.00 | 3555.50 | 2960.50 |
| BLOCK1:ZONE2 | 3205.50 | 3561.00 | 2957.50 |
| Facility | 3701.00 | 3866.00 | 3178.50 |
| During Heating [hr] | During Cooling [hr] | During Occupied Heating [hr] | During Occupied Cooling [hr] | |
| BLOCK1:ZONE3 | 69.50 | 1.50 | 0.00 | 0.00 |
| BLOCK1:ZONE1 | 62.00 | 5.00 | 0.00 | 1.50 |
| BLOCK1:ZONE4 | 83.00 | 1.50 | 0.00 | 0.00 |
| BLOCK1:ZONE2 | 81.00 | 1.50 | 0.00 | 0.00 |
| Facility | 112.00 | 6.50 | 0.00 | 1.50 |
Report: Outdoor Air Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Average Outdoor Air During Occupied Hours| Average Number of Occupants | Nominal Number of Occupants | Zone Volume [m3] | Mechanical Ventilation [ach] | Infiltration [ach] | AFN Infiltration [ach] | Simple Ventilation [ach] | |
| BLOCK1:ZONE3 | 2.38 | 3.11 | 554.65 | 0.156 | 0.718 | 0.000 | 0.000 |
| BLOCK1:ZONE1 | 3.44 | 6.33 | 935.14 | 0.161 | 0.724 | 0.000 | 0.000 |
| BLOCK1:ZONE4 | 5.72 | 7.49 | 1334.91 | 0.156 | 0.718 | 0.000 | 0.000 |
| BLOCK1:ZONE2 | 3.36 | 4.40 | 783.43 | 0.156 | 0.718 | 0.000 | 0.000 |
| Average Number of Occupants | Nominal Number of Occupants | Zone Volume [m3] | Mechanical Ventilation [ach] | Infiltration [ach] | AFN Infiltration [ach] | Simple Ventilation [ach] | |
| BLOCK1:ZONE3 | 2.38 | 3.11 | 554.65 | 0.049 | 0.029 | 0.000 | 0.000 |
| BLOCK1:ZONE1 | 3.44 | 6.33 | 935.14 | 0.057 | 0.029 | 0.000 | 0.000 |
| BLOCK1:ZONE4 | 5.72 | 7.49 | 1334.91 | 0.049 | 0.029 | 0.000 | 0.000 |
| BLOCK1:ZONE2 | 3.36 | 4.40 | 783.43 | 0.049 | 0.029 | 0.000 | 0.000 |
Report: Object Count Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Surfaces by Class| Total | Outdoors | |
| Wall | 18 | 8 |
| Floor | 4 | 4 |
| Roof | 4 | 4 |
| Internal Mass | 0 | 0 |
| Building Detached Shading | 0 | 0 |
| Fixed Detached Shading | 0 | 0 |
| Window | 7 | 7 |
| Door | 9 | 1 |
| Glass Door | 0 | 0 |
| Shading | 0 | 0 |
| Overhang | 0 | 0 |
| Fin | 0 | 0 |
| Tubular Daylighting Device Dome | 0 | 0 |
| Tubular Daylighting Device Diffuser | 0 | 0 |
| Count | |
| HVAC Air Loops | 0 |
| Conditioned Zones | 4 |
| Unconditioned Zones | 0 |
| Supply Plenums | 0 |
| Return Plenums | 0 |
| Count | |
| IDF Objects | 0 |
| Defaulted Fields | 0 |
| Fields with Defaults | 0 |
| Autosized Fields | 0 |
| Autosizable Fields | 0 |
| Autocalculated Fields | 0 |
| Autocalculatable Fields | 0 |
Report: Sensible Heat Gain Summary
For: Entire Facility
Timestamp: 2021-02-21 23:23:14
Annual Building Sensible Heat Gain Components| HVAC Zone Eq & Other Sensible Air Heating [kWh] | HVAC Zone Eq & Other Sensible Air Cooling [kWh] | HVAC Terminal Unit Sensible Air Heating [kWh] | HVAC Terminal Unit Sensible Air Cooling [kWh] | HVAC Input Heated Surface Heating [kWh] | HVAC Input Cooled Surface Cooling [kWh] | People Sensible Heat Addition [kWh] | Lights Sensible Heat Addition [kWh] | Equipment Sensible Heat Addition [kWh] | Window Heat Addition [kWh] | Interzone Air Transfer Heat Addition [kWh] | Infiltration Heat Addition [kWh] | Opaque Surface Conduction and Other Heat Addition [kWh] | Equipment Sensible Heat Removal [kWh] | Window Heat Removal [kWh] | Interzone Air Transfer Heat Removal [kWh] | Infiltration Heat Removal [kWh] | Opaque Surface Conduction and Other Heat Removal [kWh] | |
| BLOCK1:ZONE3 | 5038.358 | -897.90 | 0.000 | 0.000 | 0.000 | 0.000 | 857.578 | 3058.504 | 2081.050 | 263.317 | 0.000 | 130.326 | 0.073 | 0.000 | -183.12 | 0.000 | -8776.37 | -1571.75 |
| BLOCK1:ZONE1 | 3899.441 | -5690.58 | 0.000 | 0.000 | 0.000 | 0.000 | 722.727 | 10239.751 | 15161.061 | 75.524 | 0.000 | 143.798 | 0.122 | 0.000 | -74.15 | 0.000 | -16415.24 | -8062.34 |
| BLOCK1:ZONE4 | 11369.948 | -1990.20 | 0.000 | 0.000 | 0.000 | 0.000 | 2067.380 | 7361.070 | 5008.576 | 365.358 | 0.000 | 317.099 | 0.088 | 0.000 | -286.14 | 0.000 | -20796.47 | -3416.62 |
| BLOCK1:ZONE2 | 7006.687 | -1178.01 | 0.000 | 0.000 | 0.000 | 0.000 | 1213.065 | 4320.044 | 2939.419 | 240.639 | 0.000 | 186.240 | 0.045 | 0.000 | -204.81 | 0.000 | -12257.10 | -2266.17 |
| Total Facility | 27314.434 | -9756.69 | 0.000 | 0.000 | 0.000 | 0.000 | 4860.751 | 24979.369 | 25190.105 | 944.838 | 0.000 | 777.464 | 0.329 | 0.000 | -748.22 | 0.000 | -58245.18 | -15316.87 |
| Time of Peak {TIMESTAMP} | HVAC Zone Eq & Other Sensible Air Heating [W] | HVAC Zone Eq & Other Sensible Air Cooling [W] | HVAC Terminal Unit Sensible Air Heating [W] | HVAC Terminal Unit Sensible Air Cooling [W] | HVAC Input Heated Surface Heating [W] | HVAC Input Cooled Surface Cooling [W] | People Sensible Heat Addition [W] | Lights Sensible Heat Addition [W] | Equipment Sensible Heat Addition [W] | Window Heat Addition [W] | Interzone Air Transfer Heat Addition [W] | Infiltration Heat Addition [W] | Opaque Surface Conduction and Other Heat Addition [W] | Equipment Sensible Heat Removal [W] | Window Heat Removal [W] | Interzone Air Transfer Heat Removal [W] | Infiltration Heat Removal [W] | Opaque Surface Conduction and Other Heat Removal [W] | |
| BLOCK1:ZONE3 | 25-JUL-14:06 | 0.00 | -3006.75 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 342.30 | 215.32 | 0.00 | 337.23 | 2111.89 | 0.00 | -0.00 | 0.00 | 0.00 | 0.00 |
| BLOCK1:ZONE1 | 30-JUL-16:04 | 0.00 | -11378.34 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 534.36 | 35.66 | 0.00 | 524.63 | 10283.69 | 0.00 | -0.00 | 0.00 | 0.00 | 0.00 |
| BLOCK1:ZONE4 | 25-JUL-14:06 | 0.00 | -6863.14 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 823.83 | 280.42 | 0.00 | 793.26 | 4965.63 | 0.00 | -0.00 | 0.00 | 0.00 | 0.00 |
| BLOCK1:ZONE2 | 25-JUL-14:06 | 0.00 | -4045.37 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 483.49 | 185.90 | 0.00 | 468.77 | 2907.22 | 0.00 | -0.00 | 0.00 | 0.00 | 0.00 |
| Total Facility | 30-JUL-16:04 | 0.00 | -20591.08 | 0.00 | 0.00 | 0.00 | 0.00 | 1049.17 | 3818.55 | 2183.98 | 427.24 | 0.00 | 2949.36 | 10162.78 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| Time of Peak {TIMESTAMP} | HVAC Zone Eq & Other Sensible Air Heating [W] | HVAC Zone Eq & Other Sensible Air Cooling [W] | HVAC Terminal Unit Sensible Air Heating [W] | HVAC Terminal Unit Sensible Air Cooling [W] | HVAC Input Heated Surface Heating [W] | HVAC Input Cooled Surface Cooling [W] | People Sensible Heat Addition [W] | Lights Sensible Heat Addition [W] | Equipment Sensible Heat Addition [W] | Window Heat Addition [W] | Interzone Air Transfer Heat Addition [W] | Infiltration Heat Addition [W] | Opaque Surface Conduction and Other Heat Addition [W] | Equipment Sensible Heat Removal [W] | Window Heat Removal [W] | Interzone Air Transfer Heat Removal [W] | Infiltration Heat Removal [W] | Opaque Surface Conduction and Other Heat Removal [W] | |
| BLOCK1:ZONE3 | 18-JAN-06:15 | 5702.58 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 15.85 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | -68.31 | 0.00 | -2748.22 | -2901.90 |
| BLOCK1:ZONE1 | 18-JAN-06:15 | 9559.65 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 534.36 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | -25.29 | 0.00 | -4700.82 | -5367.90 |
| BLOCK1:ZONE4 | 07-FEB-06:15 | 12917.21 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 38.14 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | -115.33 | 0.00 | -7006.56 | -5833.46 |
| BLOCK1:ZONE2 | 07-FEB-06:15 | 7809.36 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 22.39 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | -82.06 | 0.00 | -4115.97 | -3633.71 |
| Total Facility | 18-JAN-06:15 | 35917.63 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 610.74 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | -277.15 | 0.00 | -17801.29 | -18449.93 |


This week, we will be talking about Class in Ruby.
Classes in Ruby are first-class objects---each is an instance of class Class.
Typically, you create a new class by using:
class Name
some class describing the class behavior
end
When a new class is created, an object of type Class is initialized and assigned to a global constant (Name in this case).
When Name.new is called to create a new object, the new method in Class is run by default.
Classes, modules, and objects are interrelated. In the diagram that follows, the vertical arrows represent inheritance, and the parentheses meta-classes. All metaclasses are instances of the class `Class'.
Below is another very simple example of class:
class Class
alias oldNew new
def new(*args)
print "Creating a new ", self.name, "\n"
oldNew(*args)
end
end
class Name
end
n = Name.new
What do you think? Not too hard to learn, right?


{% extends "layout.html" %} {% block title %}Ridr | New Ride{% endblock %} {% block body_class %}new_ride{% endblock %} {% block content %}
Awesome! Let's add a ride. First, where are you coming from and where are you going?
From:
To:
When:
Time:
Continue
Tell us about the ride:
Pet friendly? Kid friendly? 420 friendly?
How many open seats do you have?
Let's Go!


Contact Us
We are always to help you. If You have Any Query or Complaint , feel free to Contact Any of Following . Here is the List:-
NAME : Jyoti Meena
SKILL : Back end Developer
Email<EMAIL_ADDRESS>Mobile No :<PHONE_NUMBER>
NAME : Shivam Gupta
SKILL : Full Stack Developer
Email<EMAIL_ADDRESS>Mobile No. :<PHONE_NUMBER>
NAME : Rishabh Sethi
SKILL : Front end Developer
Email<EMAIL_ADDRESS>Mobile No:<PHONE_NUMBER>