t
Posted on February 5, 2017
The Third Blog Post!
What did you do this past week?
This week the majority of the time I spent doing work for this class was in the lab doing the collatz conjecture lab. With github and Travis CI being already in place, this was significantly less frustrating than the process last week. Aside from some terrible segfaults, the process went smoothly, though my initial idea for a solution (using dynamic programming to build cycle lengths) needed additional work to be the hackerrank goal time of 2.00 seconds. With the small addition of a second cache to keep track of overarching solutions rather than individial cycle lengths, the hackerrank tests were passed with flying colors.
What will you do next week?
The next lab has been published, an implementation of a voting algorithm. I've actually done this excercise once before, though it was in clingo (a declarative logic programming language). I don't expect this experience to help me in any way, declarative and imperative programming are exactly opposite approaches to programming problems, but it will be interesting to see how the solutions differ. I pray that I have no other problems with the technology tools, because the last lab would have been both less frustrating and less time consuming if they had cooperated.
What's in the way?
It's too early in the labe to tell what will be the biggest problem yet, though again I'm going to do everything I can to make the tech itself helpful rather than an obstacle. As always, I've got to keep up with my other classes as well as this one, and I need to be more prepared for the quizzes. Missing a question or two really brings down your average, and I'd rather not miss out on an A in this class because I screw up the daily quizzes.
What's my experience in the class?
Again, the quizzes have been fair. There's only been one question so far (out of 10-15?) that I felt that was not clear or I did not deserve to miss. With the technology toos now firmly in place and not requireing any additional setup aside from cloning a repository and flipping a switch, this upcoming lab will hopefully be a much smoother experience. Also this will be the first lab I do with an unknown partner in a few years, so I'm interested to see how it goes.
What's the tip of the week?
Don't forget the C++ syntax before your quizzes. I understood a problem this week but missed it because I could not remember if the ampersand meant "address" or "reference." Know your C++, know your definitions!


where everything comes together in amfphp.
The class used for the entry point of a remoting call
| package | Amfphp_Core |
|---|---|
| author | Ariel Sommeria-klein |
__construct(array $getData, array $postData, String $rawInputData, String $contentType, \Amfphp_Core_Config $config)
array
typically the $_GET array.
array
typically the $_POST array.
String
String
getResponseHeaders() : array
Creates an associative array of headers, then filters them, then returns an array of strings
array
output()
service() : \<String>
It deserializes the raw data passed into the constructor as an Amfphp_Core_Amf_Packet, handles the headers, handles the messages as requests to services, and returns the responses from the services It does not however handle output headers, gzip compression, etc. that is the job of the calling script
\<String>
the serialized amf packet containg the service responses$config : \Amfphp_Core_Config
$contentType : String
For example for amf, application/x-amf
$getData : array
$postData : array
$rawInputData : String
$rawOutputData : String
FILTER_DESERIALIZED_REQUEST
The callee can modify the data and return it.
| param |
|---|
FILTER_DESERIALIZED_REQUEST_HANDLER
Plugin should return a Amfphp_Core_Common_IDeserializedRequestHandler if it recognizes the request
| param | null at call in gateway. |
|---|---|
| param |
FILTER_DESERIALIZED_RESPONSE
The callee can modify the data and return it.
| param |
|---|
FILTER_DESERIALIZER
Plugin should return a Amfphp_Core_Common_IDeserializer if it recognizes the content type
| param | the deserializer. null at call in gateway. |
|---|---|
| param |
FILTER_EXCEPTION_HANDLER
If the plugin takes over the handling of the request message, it must set this to a proper Amfphp_Core_Common_IExceptionHandler
| param | null at call in gateway. |
|---|---|
| param |
FILTER_HEADERS
| param | an associative array of headers. For example array('Content-Type' => 'application/x-amf') |
|---|---|
| param |
FILTER_SERIALIZED_REQUEST
| todo | this filter only allows manipulation of raw post data, and is as such a bit misleading. Maybe rename and do filters for GET and POST |
|---|---|
| param | the raw http data |
FILTER_SERIALIZED_RESPONSE
| param | the raw http data |
|---|
FILTER_SERIALIZER
| param | the serializer. null at call in gateway. |
|---|---|
| param | Plugin sets to a Amfphp_Core_Common_ISerializer if it recognizes the content type |
FILTER_SERVICE_FOLDER_PATHS
Use this to add a service folder for a plugin
| param | serviceFolderPaths array of absolute paths |
|---|
FILTER_SERVICE_NAMES_2_CLASS_FIND_INFO
Use this to add a service for a plugin when a service folder isn't enough
| param | serviceNames2ClassFindInfo array of ClassFindInfo. Key is the service nane |
|---|


Instructions: Draw a box around a Stop on the map to view the delay over 24 hours
Zurich
sanFrancisco
Geneva


Thumbnails will link to a larger image in a new page.
For further information, please contact jane.doe@noone.com


--- layout: default title: VIF Program --- {% include JB/setup %}
lorem ipsum...
Curriculum, Lesson plans, Tools and Community


HTML5 Geolocation
Click the button to get your coordinates.
Click the button to get your position.
Click the button to get your coordinates.
HTML5 Drag and Drop
HTML5 Web Storage
HTML5 Web Workers
Count numbers:
HTML5 SSE(Server-Sent Events-One Way Messaging))
Getting server updates


Formats a number adding commas.
formatNumber(val, [groupSymbol], [decimalSymbol])
| val |
string or number, a number to format |
| groupSymbol |
string, a group delimiter (default is comma) |
| decimalSymbol |
string, a group delimiter (default is dot) |
The val argument can be an integer, float on in money format. The method will add commas (or
whatever groupSymbol you defined) after each there digits. This method will also format number
with a specified decimalSymbol.
Both groupSymbol and decimalSymbol are defined in
w2utils.settings


"ITHAMAR "palm isle, the fourth and youngest son of Aaron (1 Chronicles 6:3). He was consecrated to the priesthood along with his brothers(Exodus 6:23); and after the death of Nadab and Abihu, he and Eleazar alone discharged the functions of that office (Leviticus 10:6, 12; Numbers 3:4). He and his family occupied the position of common priest till the high priesthood passed into his family in the person of Eli (1 Kings 2:27), the reasons for which are not recorded. (See ZADOK.)
"ITHAMAR "palm isle, the fourth and youngest son of Aaron (1 Chronicles 6:3). He was consecrated to the priesthood along with his brothers(Exodus 6:23); and after the death of Nadab and Abihu, he and Eleazar alone discharged the functions of that office (Leviticus 10:6, 12; Numbers 3:4). He and his family occupied the position of common priest till the high priesthood passed into his family in the person of Eli (1 Kings 2:27), the reasons for which are not recorded. (See ZADOK.)


If I understand this correctly, x1=(3*a^2)/(8*a^2)+c/a;
x2=b^3/(8*a^3)-(b*c)/(2*a^2)+d/a;
x3=(-3*b^4)/(256*a^4)+(c*b^2)/(16*a^3)-(b*d)/(4*a^2)+e/a;
//"(+-)" means "plus or minus"
if !x2 then
x4=-b/(4*a)(+-)((-x1(+-)(x1^2-4*x3)^.5)/2)^.5
else
//Too long. You get the general idea.
Alternatively there are a variety of root-finding algorithms for n-th order polynomials -- bisection method, secant method, newton-rhapson method, etc, all of which are explained in detail in Wikipedia.
Do you want to approximate the roots (numerically) or do you want to solve the equation (algebraically)? (The latter is still possible, since the degree isn't 5 or above, in which case you'd be out of luck...)
I am sorry, I did not check the forum for a month due to examinations! I still have this work pending.
I need to implement a program which is very fast to solve this equation. So I guess an approximated value would also do! I cannot afford to use programs which runs iterations 1000 times to get the corrrect value. Speed of calculation is of utmost importance.
I found the solution for this. There is a perfect code for it in Google-codes and it runs splendidly. If anybody wants to use a function which analytically solves 4th order equations, use this :-
I found the solution for this. There is a perfect code for it in Google-codes and it runs splendidly. If anybody wants to use a function which analytically solves 4th order equations, use this :-


Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
destacando esse texto
| # | Nome | Sobrenome | Idade |
|---|---|---|---|
| 1 | Douglas | Poma | 27 |
| 2 | Elaine | Poma | 19 |
| 3 | Marisa | Smekatz | 47 |
Algum Resumo da noíticia do título
Algum Resumo da noíticia do título
Algum Resumo da noíticia do título


External Ephemeris file to STK/MTO Tracks
This utility will create an MTO and populate it with all the external ephemeris files in the specified directory. Directory:


data class StateEvent
GameController state change event.
StateEvent(state: String, turn: Int?)
New state title
val state: String
Current turn
val turn: Int?


{% extends "layout.html" %}
{% block JavaScript %}
{% endblock JavaScript %}
{% block content %}
For each input sequence, PhANNs run 10 ANNs predictions. Each of those 10 ANNs outputs
the soft-max scores for every class (a number between 0 and 1, such that the score of each class adds to 1).
PhANNs outputs the per class sum of the ANNs scores (a number between 0 and 10).
The input sequence is classified as the class with the highest score (highlighted in yellow).
Furthermore the "Confidence" score shows which percentage of sequences in the test set, classified as that class with that score or better, were correctly classified.
{% endblock content %}


Syllabus
Propositional logic: Syntax, semantics, valid, satisfiable and unsatisfiable formulas, encoding and examining the validity of some logical arguments; Recurrences, summations, generating functions, asymptotic; Sets, relations and functions: Operations on sets, relations and functions, binary relations, partial ordering relations, equivalence relations, principles of mathematical induction, Finite and infinite sets, countable and uncountable sets, Cantor’s diagonal argument and the power set theorem; Introduction to counting: Basic counting techniques - inclusion and exclusion, pigeon-hole principle, permutation, combination, generating function; Algebraic structures and morphisms: semigroups, groups, subgroups, homomorphisms, rings, integral domains, fields; Introduction to graphs: paths, connectivity, subgraphs, isomorphic and homeomorphic graphs, trees, complete graphs, bipartite graphs, matchings, colourability, planarity, digraphs;
Texts
- J. P. Tremblay and R. P. Manohar, Discrete Mathematics with Applications to Computer Science, Tata McGraw-Hill, 1999.
- C. L. Liu, Elements of Discrete Mathematics, 2nd Ed, Tata McGraw-Hill, 2000.
- R. L. Graham, D. E. Knuth, and O. Patashnik, Concrete Mathematics, 2nd Ed, Addison-Wesley, 1994.
- N. Deo, Graph Theory with Applications to Engineering and Computer Science, Prentice Hall of India, 1974.
- S. Lipschutz and M. L. Lipson, Schaums Outline of Theory and Problems of Discrete Mathematics, 2ndEd, Tata McGraw-Hill, 1999.


Module ldtk
LDtk level importer for Lua and drawing using LÖVE.
Support most LDtk features, and allow easy usage in LÖVE projects. In particular, this mainly focus only on features and values that are useful for showing the final level – this does not try, for example, to expose every internal identfiers or intermediates values that are only relevant for editing.
Currently up-to-date with LDtk 1.1.3.
Every unit is in pixel in the API unless written otherwise.
Colors are reprsented as a table {r,g,b}
where r
,b
,g
in [0-1].
This modules returns a single function, LDtk(path).
This modules requires json.lua; a copy of it is included with ubiquitousse in the lib
directory for simplicity.
This module will first try to load a global module named json
– so if you use the same json module in your project ubiquitousse will reuse it.
If it doesn’t find it, it will then try to load the copy included with ubiquitousse.
Optionally requires LÖVE love.graphics
(drawing Image, SpriteBatch, Quad), for drawing only.
Usage:
local ldtk = require("ubiquitousse.ldtk") -- load ldtk project file local project = ldtk("example.ldtk") -- can define callbacks when loading: for example to setup entities defined in LDtk local callbacks = { onAddEntity = function(entity) -- handle entity... end } -- load every level, with callbacks for _, lvl in ipairs(project.levels) do lvl:load(callbacks) end function love.draw() -- draw every level for _, lvl in ipairs(project.levels) do lvl:draw() end end
Functions
| LDtk (path) | Load a LDtk project. |
Entity objects
| Entity.layer | Layer this entity belongs to. |
| Entity.iid | Unique instance identifier for this entity. |
| Entity.identifier | The entity name. |
| Entity.x | X position of the entity relative to the layer, in pixels. |
| Entity.y | Y position of the entity relative to the layer, in pixels. |
| Entity.width | The entity width, in pixels. |
| Entity.height | The entity height, in pixels. |
| Entity.sx | Scale factor on x axis relative to original entity size. |
| Entity.sy | Scale factor on y axis relative to original entity size. |
| Entity.pivotX | The entity pivot point x position relative to the entity, in pixels.. |
| Entity.pivotY | The entity pivot point x position relative to the entity, in pixels.. |
| Entity.color | Entity color. |
| Entity.tile | Tile associated with the entity, if any. |
| Entity.tags | Tags associated with the entity: can be used either as a list of tags or a map of activated tags tags[name] == true. |
| Entity.fields | Map of CustomFields of the entity. |
| Entity:draw () | Called for the entity when drawing the associated entity layer (you will likely want to redefine it). |
Tileset objects
| Tileset.image | The tileset LÖVE image object. |
| Tileset.tags | Tags associated with the tileset: can be used either as a list of tags or a map of activated tags tags[name] == true. |
Layer objects
| Layer:draw ([x=0[, y=0]]) | Draw the current layer. |
| Layer.level | Level this layer belongs to. |
| Layer.iid | Unique instance identifier for this layer. |
| Layer.identifier | The layer name. |
| Layer.type | Type of layer: IntGrid, Entities, Tiles or AutoLayer. |
| Layer.visible | Whether the layer is visible or not. |
| Layer.opacity | The layer opacity (0-1). |
| Layer.order | The layer order: smaller order means it is on top. |
| Layer.x | X position of the layer relative to the level. |
| Layer.y | Y position of the layer relative to the level. |
| Layer.gridSize | Size of the grid on this layer. |
| Layer.gridWidth | Width of the layer, in grid units. |
| Layer.gridHeight | Height of the layer, in grid units. |
| Layer.parallaxFactorX | Parallax horizontal factor (from -1 to 1, defaults to 0) which affects the scrolling speed of this layer, creating a fake 3D (parallax) effect. |
| Layer.parallaxFactorY | Parallax vertical factor (from -1 to 1, defaults to 0) which affects the scrolling speed of this layer, creating a fake 3D (parallax) effect. |
| Layer.parallaxScaling | If true, a layer with a parallax factor will also be scaled up/down accordingly. |
| Layer.entities | (Entities layer only) List of Entity in the layer. |
| Layer.tiles | (Tiles, AutoLayer, or IntGrid with AutoLayer rules layers only) List of Tiles in the layer. |
| Layer.tileset | (Tiles, AutoLayer, or IntGrid with AutoLayer rules layers only) Tileset object associated with the layer. |
| Layer.spritebatch | (Tiles, AutoLayer, or IntGrid with AutoLayer rules layers only) LÖVE SpriteBatch containing the layer. |
| Layer.intTiles | (IntGrid without AutoLayer rules layer only) list of IntTiles in the layer. |
Tile objects
| Tile.layer | Layer the tile belongs to. |
| Tile.x | X position of the tile relative to the layer, in pixels. |
| Tile.y | Y position of the tile relative to the layer, in pixels. |
| Tile.flipX | Whether the tile is flipped horizontally. |
| Tile.flipY | Whether the tile is flipped vertically. |
| Tile.tags | Tags associated with the tile: can be used either as a list of tags or a map of activated tags tags[name] == true. |
| Tile.data | Custom data associated with the tile, if any. |
| Tile.quad | Quad associated with the tile (relative to the layer’s tileset). |
IntTile objects
| IntTile.layer | Layer the IntTile belongs to. |
| IntTile.x | X position of the IntTile relative to the layer, in pixels. |
| IntTile.y | Y position of the IntTile relative to the layer, in pixels. |
| IntTile.identifier | Name of the IntTile. |
| IntTile.value | Integer value of the IntTile. |
| IntTile.color | Color of the IntTile. |
Level objects
| Level:draw ([x=0[, y=0]]) | Draw this level. |
| Level:drawBackground ([x=0[, y=0]]) | Draw this level background. |
| Level:load ([callbacks]) | Load the level. |
| Level:unload ([callbacks]) | Unload the level. |
| Level.project | Project this level belongs to. |
| Level.loaded | Whether this level is currently loaded or not. |
| Level.iid | Unique instance identifier for this level. |
| Level.identifier | The level name. |
| Level.depth | Depth of the level in the world, to properly stack overlapping levels when drawing. |
| Level.x | The level x position in pixels. |
| Level.y | The level y position in pixels. |
| Level.width | The level width. |
| Level.height | The level height. |
| Level.fields | Map of CustomFields of the level (table). |
| Level.layers | List of Layers in the level (table). |
| Level.background | Level background. |
Project objects
| Project.levels | List of Levels in this project. |
CustomFields objects
Type conversion.
Functions
- LDtk (path)
-
Load a LDtk project.
Parameters:
- path string to LDtk project file (.ldtk)
Returns:
-
Project
the loaded LDtk project
Entity objects
System
s.
The idea is that entities should only contain data and no code; it’s the systems that are responsible for the actual processing (but it’s your game, do as you want).
This data is referred to, and organized in, “components”.
- Entity.layer
-
Layer this entity belongs to.
Type:
Layer
- Entity.iid
-
Unique instance identifier for this entity.
Type:
string
- Entity.identifier
-
The entity name.
Type:
string
- Entity.x
-
X position of the entity relative to the layer, in pixels.
Type:
number
- Entity.y
-
Y position of the entity relative to the layer, in pixels.
Type:
number
- Entity.width
-
The entity width, in pixels.
Type:
number
- Entity.height
-
The entity height, in pixels.
Type:
number
- Entity.sx
-
Scale factor on x axis relative to original entity size.
Type:
number
- Entity.sy
-
Scale factor on y axis relative to original entity size.
Type:
number
- Entity.pivotX
-
The entity pivot point x position relative to the entity, in pixels..
Type:
number
- Entity.pivotY
-
The entity pivot point x position relative to the entity, in pixels..
Type:
number
- Entity.color
-
Entity color.
Type:
table
{r,g,b} with r,g,b in [0-1] - Entity.tile
-
Tile associated with the entity, if any. Is a table { tileset = associated tileset object, quad = associated quad }.
quad is a LÖVE Quad if LÖVE is available, otherwise a table
{ x, y, width, height }
.Type:
table
- Entity.tags
-
Tags associated with the entity: can be used either as a list of tags or a map of activated tags tags[name] == true.
Type:
{"tag",["tag"]=true,...}
- Entity.fields
-
Map of CustomFields of the entity.
Type:
CustomFields
- Entity:draw ()
-
Called for the entity when drawing the associated entity layer (you will likely want to redefine it).
By default, this draws the tile associated with the entity if there is one, or a rectangle around the entity position otherwise, assuming we are currently in layer coordinates (i.e. layer top-left is at 0,0).
Requires:
-
love
Tileset objects
- Tileset.image
- The tileset LÖVE image object. If LÖVE is not available, this is the path to the image (string).
- Tileset.tags
-
Tags associated with the tileset: can be used either as a list of tags or a map of activated tags tags[name] == true.
Type:
{"tag",["tag"]=true,...}
Layer objects
Part of a Level.
- Layer:draw ([x=0[, y=0]])
-
Draw the current layer.
Assumes we are currently in level coordinates (i.e. level top-left is at 0,0). You can specify an offset if your level top-left coordinate is not at 0,0 (or to produce other effects).
Requires:
-
love
Parameters:
- x number offset X position to draw the layer at (default 0)
- y number offset Y position to draw the layer at (default 0)
- Layer.level
-
Level this layer belongs to.
Type:
Level
- Layer.iid
-
Unique instance identifier for this layer.
Type:
string
- Layer.identifier
-
The layer name.
Type:
string
- Layer.type
-
Type of layer: IntGrid, Entities, Tiles or AutoLayer.
Type:
string
- Layer.visible
-
Whether the layer is visible or not.
Type:
boolean
- Layer.opacity
-
The layer opacity (0-1).
Type:
number
- Layer.order
-
The layer order: smaller order means it is on top.
Type:
number
- Layer.x
-
X position of the layer relative to the level.
Type:
number
- Layer.y
-
Y position of the layer relative to the level.
Type:
number
- Layer.gridSize
-
Size of the grid on this layer.
Type:
number
- Layer.gridWidth
-
Width of the layer, in grid units.
Type:
number
- Layer.gridHeight
-
Height of the layer, in grid units.
Type:
number
- Layer.parallaxFactorX
-
Parallax horizontal factor (from -1 to 1, defaults to 0) which affects the scrolling speed of this layer, creating a fake 3D (parallax) effect.
Type:
number
- Layer.parallaxFactorY
-
Parallax vertical factor (from -1 to 1, defaults to 0) which affects the scrolling speed of this layer, creating a fake 3D (parallax) effect.
Type:
number
- Layer.parallaxScaling
-
If true, a layer with a parallax factor will also be scaled up/down accordingly.
Type:
boolean
- Layer.entities
-
(Entities layer only) List of Entity in the layer.
Each entity in the list is also bound to its IID in this table, so if
ent = entities[1]
, you can also find it atentities[ent.iid]
.Type:
{Entity,...}
- Layer.tiles
-
(Tiles, AutoLayer, or IntGrid with AutoLayer rules layers only) List of Tiles in the layer.
Type:
{Tile,...}
nil
if not applicable
- Layer.tileset
-
(Tiles, AutoLayer, or IntGrid with AutoLayer rules layers only) Tileset object associated with the layer.
Type:
Tileset
nil
if not applicable
- Layer.spritebatch
-
(Tiles, AutoLayer, or IntGrid with AutoLayer rules layers only) LÖVE SpriteBatch containing the layer.
Requires:
-
love
Type:
SpriteBatch
nil
if LÖVE not available.
- Layer.intTiles
-
(IntGrid without AutoLayer rules layer only) list of IntTiles in the layer.
Type:
{IntTile,...}
nil
if not applicable
Tile objects
This represent the tiles from a Tiles, AutoLayer or IntGrid with AutoLayer rules layer.
Can be retrived from the Layer.tiles list or onAddTile
level load callback.
- Tile.layer
-
Layer the tile belongs to.
Type:
Layer
- Tile.x
-
X position of the tile relative to the layer, in pixels.
Type:
number
- Tile.y
-
Y position of the tile relative to the layer, in pixels.
Type:
number
- Tile.flipX
-
Whether the tile is flipped horizontally.
Type:
boolean
- Tile.flipY
-
Whether the tile is flipped vertically.
Type:
boolean
- Tile.tags
-
Tags associated with the tile: can be used either as a list of tags or a map of activated tags tags[name] == true.
Type:
{"tag",["tag"]=true,...}
- Tile.data
-
Custom data associated with the tile, if any.
Type:
string
- Tile.quad
-
Quad associated with the tile (relative to the layer’s tileset).
Type:
LÖVE
Quad if LÖVE is availabletable
{ x, y, width, height } if LÖVE not available
IntTile objects
This represent the tiles from a IntGrid without AutoLayer rules layer.
Can be retrived from the intTiles list or onAddIntTile
level load callback.
- IntTile.layer
-
Layer the IntTile belongs to.
Type:
Layer
- IntTile.x
-
X position of the IntTile relative to the layer, in pixels.
Type:
number
- IntTile.y
-
Y position of the IntTile relative to the layer, in pixels.
Type:
number
- IntTile.identifier
-
Name of the IntTile.
Type:
string
- IntTile.value
-
Integer value of the IntTile.
Type:
number
- IntTile.color
-
Color of the IntTile.
Type:
table
{r,g,b} with r,g,b in [0-1]
Level objects
Levels are not automatically loaded in order to not waste ressources if your project is large; so before drawing or operating on a level, you will need to call its Level:load method.
Part of a Project.
- Level:draw ([x=0[, y=0]])
-
Draw this level.
Will draw the eventual backgrounds and all the layers in the level.
Assumes we are currently in world coordinates (i.e. world top-left is at 0,0). You can specify an offset if your world top-left coordinate is not at 0,0 (or to produce other effects).
The level must be loaded.
Requires:
-
love
Parameters:
- x number offset X position to draw the level at (default 0)
- y number offset Y position to draw the level at (default 0)
- Level:drawBackground ([x=0[, y=0]])
-
Draw this level background.
Assumes we are currently in level coordinates (i.e. level top-left is at 0,0). You can specify an offset if your level top-left coordinate is not at 0,0 (or to produce other effects).
The level must be loaded.
Requires:
-
love
Parameters:
- x number offset X position to draw the background at (default 0)
- y number offset Y position to draw the backgroud at (default 0)
- Level:load ([callbacks])
-
Load the level.
Will load every layer in the level and the associated images.
You can optionally specify some callbacks for the loading process:
onAddLayer(layer)
will be called for every new layer loaded, with the Layer as sole argumentonAddTile(tile)
will be called for every new tile loaded, with the Tile as sole argumentonAddIntTile(tile)
will be called for every new IntGrid tile loaded, with the IntTile as sole argumentonAddEntity(entity)
will be called for every new entity loaded, with the Entity as sole argument
These callbacks should allow you to capture all the important elements needed to use the level, so you can hopefully integrate it into your current game engine easily.
Parameters:
- callbacks table (optional)
- Level:unload ([callbacks])
-
Unload the level. Images loaded by the level will be freed on the next garbage collection cycle.
You can optionally specify some callbacks for the unloading process:
onAddLayer(layer)
will be called for every new layer unloaded, with the Layer as sole argumentonAddTile(tile)
will be called for every new tile unloaded, with the Tile as sole argumentonAddIntTile(tile)
will be called for every new IntGrid tile unloaded, with the IntTile as sole argumentonAddEntity(entity)
will be called for every new entity unloaded, with the Entity as sole argument
Parameters:
- callbacks table (optional)
- Level.project
-
Project this level belongs to.
Type:
Project
- Level.loaded
-
Whether this level is currently loaded or not.
Type:
boolean
- Level.iid
-
Unique instance identifier for this level.
Type:
string
- Level.identifier
-
The level name.
Type:
string
- Level.depth
-
Depth of the level in the world, to properly stack overlapping levels when drawing. Default is 0, greater means above, lower means below.
Type:
number
- Level.x
-
The level x position in pixels.
For Horizontal and Vertical layouts, is always -1.
Type:
number
- Level.y
-
The level y position in pixels.
For Horizontal and Vertical layouts, is always -1.
Type:
number
- Level.width
-
The level width.
Type:
number
- Level.height
-
The level height.
Type:
number
- Level.fields
-
Map of CustomFields of the level (table).
Type:
CustomFields
- Level.layers
-
List of Layers in the level (table).
Each layer in the list is also bound to its IID in this table, so if
lay = layers[1]
, you can also find it atlayers[lay.iid]
.Type:
{Layer,...}
- Level.background
-
Level background.
If there is a background image,
background.image
contains a table{image=image, x=number, y=number, sx=number, sy=number}
where image is the LÖVE image (or image filepath if LÖVE not available) x and y are the top-left position, and sx and sy the horizontal and vertical scale factors.Fields:
- color backrgound color {r,g,b} with r,g,b in [0-1]
- image backrgound image information, if any
Project objects
Returned by LDtk.
- Project.levels
-
List of Levels in this project.
Each level in the list is also bound to its IID in this table, so if
lvl = levels[1]
, you can also find it atlevels[lvl.iid]
.Type:
{Level,...}
CustomFields objects
LDtk allows to defined custom fields in some places (Entity.fields, Level.fields). This library allows you to access them in a table that
map each field name to its value {["fieldName"]=value,…}
.
Type conversion.
Here is how the values are converted to Lua values:
- Integers, Floats are converted into a Lua number.
- Booleans are converted into a Lua boolean.
- Strings, Multilines are converted in a Lua string.
- Enum are converted into a Lua string giving the currently selected enum value.
- Filepath are converted into a Lua string giving the file path.
- Arrays are converted into a Lua table with the elements in it as a list.
- Points are converted into a Lua table with the fields x and y, in pixels:
{ x=number, y=number }
. - Colors are converted into a Lua table with the red, green and blue components in [0-1] as a list:
{r,g,b}
. - Tiles are converted into a Lua table { tileset = associated tileset object, quad = associated quad } where quad is a LÖVE Quad if LÖVE is available, otherwise a table
{ x, y, width, height }
. - EntityRef are converted into a Lua table { level = level, layerIid = layer IID, entityIid = entity IID, entity = see explanation }. If the entity being refernced belongs to another level and this level is not loaded,
entity
will be nil; otherwise (same level or the other level is also loaded), it will contain the entity.


Space
Simple block element for creating space in the page. Use the debug-space
class in the document
to reveal space blocks, as in the above example.
evo-space

Place a

tag in the page where you want negative space between floating elements, and apply the evo-space
class.
evo-margin

Place a

tag on the element for which you want negative space at the bottom on the outside, and apply the evo-margin
class.
evo-padding

Place a

tag on the element for which you want negative space at the bottom inside portion, and apply the evo-padding
class.


# Types r.route :: String r.as_path :: [Integer] r.bgp_community :: [String] asdb :: [String] -- where the key is ASN # Example Queries /* Show route of 2001:470::/32 */ r.route == '2001:470::/32' /* Show route w/ 6939 in AS Path */ r.as_path.includes(6939) /* show route w/ community 65443:4134 */ if(r.bgp_community) r.bgp_community.includes('65443:4134') /* show route to address <IP_ADDRESS> */ r.route.netOf('<IP_ADDRESS>') /* Show route with community *:58453 or *:4134 */ if(r.bgp_community) r.bgp_community.some(c => { return c.match(/:58453/) || c.match(/:4134/) }) /* Show route with a prefix less than /9 */ Number.parseInt(r.route.split('/')[1]) < 9 /* "real" as_path (as_path w/o prepend) > 10 */ (r.as_path.filter((i, p, s) => s.indexOf(i) == p)).length > 10 /* Show path to prefixes with "carnegie mellon" in it's AS descr */ r.as_path.some(a => { if(asdb[a]) return asdb[a].toLowerCase().includes('carnegie mellon'); })


Log into Exambazaar
Log into Exambazaar
Reset Password
Reset Password
Create an account
Create an account
Log in
Sign up
with Facebook
Log in with Facebook
or
{{loginErrorMessage}}
Forgot Password?
Log in
Sign up
Verify by OTP
{{userResetExistMessage}}
{{ResetOTPmessage}}
Did not receive OTP?
Resend it
Password should be at least 6 characters long
Log in
Sign up
Reset Password
Back to Log in
Verify by OTP
{{userExistMessage}}
{{OTPmessage}}
Did not receive OTP?
Resend it
Password should be at least 6 characters long
Sign up
Log in
We want to help!
You’ll love our discounts on the best-selling exam prep material*
*Limited coupons only
Review your coaching
Receive exclusive Exambazaar coupon
Get upto 50% OFF on courses from
(hover to find out discounts for each provider)
(tap to find out discounts for each provider)
{{offer.tooltip}}
{{item}}
{{item.name}}
Review
{{partnerOffer.displayname}}
{{partnerOffer}}
{{activeExamEligibility.exam.briefDescription}}
Review
Review your coaching institute
|
Avail upto
50% discount
on the best exam resources
Review
Review your coaching | Avail upto
50% off
Go
EXAMBAZAAR
Top Rankers
NEET 2017
JEE 2017
Blog
Welcome {{sessionuser.basic.name}}!
Your Reviews
Your Shortlisted Institutes
Log in
Logout
Tweets by @exambazaar


{# 1. Extend the relevant layout #} {# --------------------------------------- #} {% extends 'sidebar.html' %} {# --------------------------------------- #} {# 2. Assign Settings and variables #} {# --------------------------------------- #} {% set id = "events-single" %} {% set section = "events" %} {% set title = "Members’ Assembly meeting, 3-5 October 2017, Rome" %} {% set hero_image = "hero-news-article.jpg" %} {# --------------------------------------- #} {# 3. Add models and macros #} {# --------------------------------------- #} {% model 'events', as="events" %} {% import 'macros/button.html' as buttons %} {% import 'macros/icon.html' as icons %} {# --------------------------------------- #} {# 4. Add page content into relevant areas Add/Delete blocks as necessary #} {# --------------------------------------- #} {% block hero %} {% include 'heroes/hero-past-event.html' %} {% endblock %} {% block aside %}
The Members’ Assembly 2017 will be held on 3-5 October in Rome and we are grateful to the International Fund for Agricultural Development (IFAD) who have kindly offered their headquarters for IATI’s first meeting in Italy.
Members of IATI meet once a year at IATI’s Members’ Assembly meeting. IATI’s Members’ Assembly has final approval on strategic decisions, including recommendations relating to the budget and work plan received from the Governing Board. The Members’ Assembly is chaired by the Chair of IATI, who is elected by representatives of the Governing Board.
Many thanks to the European Commission’s Directorate-General for International Cooperation and Development (DG DEVCO) for providing funding for the event.
Minutes
Paper 1
Paper 2A
Paper 2B
Paper 2C
Paper 2D
Paper 2E
Paper 2F
Paper 4
Paper 5
Paper 7
Paper 8
Paper 10
Welcome breakfast:
IATI Introduction MA 2017 presentation
Workplan implementation 2016-17:
IATI Workplan update MA 2017 presentation
Data Use strategy:
IATI Data Use MA 2017 presentation
Update on Grand Bargain:
IATI Grand Bargain update MA 2017 presentation
Institutional Review:
IATI hosting MA 2017 presentation
Standard updates:
IATI Standard update MA 2017 presentation
Communications:
IATI Communications MA 2017 presentation
Community showcases:
AICS: OPENAID 2.0 – Improving transparency and access of public aid information
Community showcases:
FAO Proposal - Addressing Gaps in OECD-DAC CRS Classification System
Community showcases:
IFAD Progress in the transparency agenda and steps ahead
Community showcases:
Initiatives to strengthen country-level use of IATI data
Community showcases:
Open Ag Presents “Cashew Nuts: A Data Use Story”
You are required to make your own accommodation arrangements and we have provided a list of hotel recommendations for the time of your stay.For directions to the Members’ Assembly and parking arrangements, please see:
For queries related to travel and logistics email<EMAIL_ADDRESS>or for other matters on the agenda, email annelise.parr@undp.org.


|
Visit our paradise in the mountains and have a relaxing
stay at Lelen Cabins. We look forward to sharing this peace
of heaven with you. |
|
|
|
|
|
Enjoy your stay as never you've done in San Martin de los
Andes. Lelen offer you the best relationship betwen cabins
quality, services and prices, in the heart of this beatifull
mountain city. |
|
|
Cabins for
seven people |
· |
|
|
|
Comfortable rooms |
· |
|
|
|
Friendly services |
· |
|
|
|
Room services |
· |
|
|
|
One fully
equipped Bathroom |
· |
|
|
|
Toilette |
· |
|
|
|
|
|
|
|
· |
Phone with DDI and fax service |
| |
|
|
· |
Closed Garage & Ski guard |
| |
|
|
· |
Carpeted bedrooms & lounge |
|
|
|
Fully
equipped kitchen |
· |
| |
|
|
Microwave |
· |
| |
|
|
Personal Safe
Box |
· |
| |
|
|
BBQ room & Tv |
· |
| |
|
|
Central hot
water |
· |
|
|
|
|
|
|
|
|
Optional
Services: |
|
|
|
|
· |
Guide to: |
|
|
-
Fishing
- Trekking
- Skiing
- Mountain Bikeing
- Rafting, etc. |
|
|
|


AMAZING NEW HACKS !
26-C,Vidhyut Nagar Swaminarayan Marg,Ajmer Road,Jaipur,Rajasthan,India.
"Any great idea is inspired by new and crazy innovators". If you have any suggestions/feedback regarding the work done.Please feel free to send me a mail.


vignettes/compromise_power.Rmd
compromise_power.Rmd
We have recently, August 2020, added 5 new functions to
Superpower
to expand the package’s capabilities. In this
vignette, we will introduce these new functions and how they can help
with study planning.
These new functions include: power.ftest
,
optimal_alpha
, ANOVA_compromise
,
alpha_standardized
, and p_standardized
The overall goal is to provide ways for researchers to justify their alpha level when designing studies, and provide greater flexibility.
Within the new optimal_alpha
function, there are two
options within the error
argument: minimal
or
balanced
.
First, we have an equation for how a weighted combined error rate is
calculated when error = minimal
.
(costT1T2 * x + priorH1H0 * y)/(priorH1H0 + costT1T2)
\(WCER = \frac{\frac{cost_\alpha}{cost_\beta} \cdot \alpha + \frac{Pr(H_1)}{Pr(H_0)}\cdot\beta}{\frac{Pr(H_1)}{Pr(H_0)}+\frac{cost_\alpha}{cost_\beta}}\)
Second, we have an equation for how a weighted combined error rate is
calculated when error = balanced
.
max((costT1T2 * x - priorH1H0 * y)/(priorH1H0 + costT1T2), (priorH1H0 * y - costT1T2 * x)/(priorH1H0 + costT1T2))
\(WCER = max(\frac{\frac{cost_\alpha}{cost_\beta} \cdot \alpha - \frac{Pr(H_1)}{Pr(H_0)}\cdot\beta}{\frac{Pr(H_1)}{Pr(H_0)}+\frac{cost_\alpha}{cost_\beta}} | \frac{ \frac{Pr(H_1)}{Pr(H_0)}\cdot\beta - \frac{cost_\alpha}{cost_\beta} \cdot \alpha }{\frac{Pr(H_1)}{Pr(H_0)}+\frac{cost_\alpha}{cost_\beta}})\)
Assume we plan to perform an independent samples t-test, where our smallest effect size of interest is d = 0.5, and we are planning to collect 64 participants in each condition. We would normally calculate power as follows:
power.t.test(delta = .5, sd = 1, n = 64, sig.level = 0.05, type = 'two.sample', alternative = 'two.sided')$power
This analysis tells us that we have 80% power with a 5% alpha level for our smallest effect size of interest, d = 0.5, when we collect 64 participants in each condition.
If we design 2000 studies like this, the number of Type 1 and Type 2 errors we make depend on how often the null hypothesis is true, and how often the alternative hypothesis is true. Let’s assume both are equally likely for now. This means that in 1000 studies the null hypothesis is true, and we will make 50 Type 1 errors. In 1000 studies the alternative hypothesis is true, and we will make 100-80 = 20% Type 2 errors, so in 200 studies we will not observe a significant result even if there is a true effect. Combining Type 1 and Type 2 errors, in the long run, we should expect 250 of our 2000 studies to yield an error.
The goal in Neyman-Pearson hypothesis testing is to control the number of errors we make, as we perform hypothesis tests. Researchers often rely on convention when setting error rates, and there is no special reason to set the Type 1 error rate at 5% and the Type 2 error rate at 20%, and there might be better choices when designing studies. For example, when collecting 64 participants per condition, it is also not optimally efficient to use these norms.
res <- optimal_alpha(power_function = "power.t.test(delta = .5, sd = 1, n=64,
sig.level = x, type='two.sample',
alternative='two.sided')$power")
print(res)
##
## Optimal Alpha
## Alpha Beta Weighted.Combined.Error.Rate
## 1 0.09967232 0.1216627 0.1106675
##
## From power function:
## [1] "power.t.test(delta = .5, sd = 1, n=64, \n sig.level = x, type='two.sample', \n alternative='two.sided')$power"
If a researcher is interested in effects of d = 0.5, and plans to collect 64 participants in each condition, setting the Type 1 error rate to 10% will increase the power to 88%. If we would perform 2000 studies designed with these error rates, we would observe 100 Type 1 errors and 120 Type 2 errors. The combined error rate across 2000 studies is 220 instead of 250. In other words, by choosing a more optimal alpha level, we can design lines of research more efficiently, because we are less likely to make errors in our statistical inferences.
You can choose to minimize the combined error rates, but you can also
decide that it makes most sense to balance the error rates. For example,
you might think a Type 1 error is just as problematic as a Type 2 error,
and therefore, you want to design a study that has balanced error rates
for a smallest effect size of interest (e.g., a 5% Type 1 error rate and
a 95% Type 2 error rate). The optimal_alpha
function can
either minimize errors, or balance them, by specifying an additional
argument in the function. The default is to minimize error rates, but by
adding error = "balance"
an alpha level is calculated so
that the Type 1 error rate equals the Type 2 error rate.
res2 <- optimal_alpha(power_function = "power.t.test(delta = .5, sd = 1, n=64,
sig.level = x, type='two.sample',
alternative='two.sided')$power", error = "balance")
print(res2)
##
## Optimal Alpha
## Alpha Beta Weighted.Combined.Error.Rate
## 1 0.1110855 0.111082 1.763508e-06
##
## From power function:
## [1] "power.t.test(delta = .5, sd = 1, n=64, \n sig.level = x, type='two.sample', \n alternative='two.sided')$power"
Repeating our earlier example, the alpha level is 11%, and the power is 89% (or the Type 2 error rate is 11%). Choosing to balance error rates is only slightly less efficient (22.22%) compared to minimizing error rates (22.13%). Power analysis is always a messy business due to the uncertainty in the true effect size, and I would not worry about the rather trivial difference between minimal error rates and balanced error rates, and the latter seems slightly more intuitive to explain, which might give this approach some practical benefits when we try to teach or explain the idea to others.
So far we have assumed a Type 1 error and Type 2 error are equally problematic. But you might believe Cohen (1988) was right, and Type 1 errors are exactly 4 times as bad as Type 2 errors. Or you might think they are twice as problematic, or 10 times as problematic. However you weigh them, as explained by Mudge et al., 2012, and Ulrich & Miller, 2019, you should incorporate those weights into your decisions.
The function has another optional argument, costT1T2
,
that allows you to specify the relative cost of Type1:Type2 errors. By
default this is set to 1, but you can set it to 4 (or any other value)
such that Type 1 errors are 4 times as costly as Type 2 errors. This
will change the weight of Type 1 errors compared to Type 2 errors, and
thus also the choice of the best alpha level.
res3 <- optimal_alpha(power_function = "power.t.test(delta = .5, sd = 1, n=100,
sig.level = x, type='two.sample',
alternative='two.sided')$power",
error = "minimal", costT1T2 = 4)
print(res3)
##
## Optimal Alpha
## Alpha Beta Weighted.Combined.Error.Rate
## 1 0.01918734 0.1211773 0.03958533
##
## From power function:
## [1] "power.t.test(delta = .5, sd = 1, n=100, \n sig.level = x, type='two.sample', \n alternative='two.sided')$power"
Now, the alpha level that minimized the weighted Type 1 and Type 2 error rates is 2%.
Similarly, you can take into account prior probabilities that either
the null is true (and you will observe a Type 1 error), or that the
alternative hypothesis is true (and you will observe a Type 2 error). By
incorporating these expectations, you can minimize or balance error
rates in the long run (assuming your priors are correct). Priors can be
specified using the priorH1H0
argument, which by default is
1 (H1 and H0 are equally likely). Setting it to 4 means you think the
alternative hypothesis (and hence, Type 2 errors) are 4 times more
likely than that the null hypothesis is true (and hence, Type 1
errors).
res4 <- optimal_alpha(power_function = "power.t.test(delta = .5, sd = 1, n=100,
sig.level = x, type='two.sample',
alternative='two.sided')$power",
error = "minimal", priorH1H0 = 2)
print(res4)
##
## Optimal Alpha
## Alpha Beta Weighted.Combined.Error.Rate
## 1 0.07901659 0.03875692 0.05217681
##
## From power function:
## [1] "power.t.test(delta = .5, sd = 1, n=100, \n sig.level = x, type='two.sample', \n alternative='two.sided')$power"
If you think H1 is four times more likely to be true than H0, you need to worry less about Type 1 errors, and now the alpha that minimizes the weighted error rates is 8%.
Now that the basics of finding an optimal alpha are out of the way we can move on to how these methods can be used for an ANOVA, and F-tests in general.
This is accomplished by the replacing the power.t.test
function with the power.ftest
function. As you can see
below it operates very similar to the power.t.test
; the
main differences are that power.ftest
requires arguments
for the degrees of freedom rather than sample size. Further, rather than
allow for input of the power as an argument, power_ftest
allows the user to input the beta_level.
power.ftest(
num_df = NULL,
den_df = NULL,
cohen_f = NULL,
alpha_level = Superpower_options("alpha_level"),
beta_level = NULL,
liberal_lambda = Superpower_options("liberal_lambda")
)
The use of the function on its own is simple, but not very intuitive for power analysis on its own.
For example, let us suppose we have known degrees of freedom of 1 and
128 respectively, and an effect size of interest of
cohen_f = .22
. Now we simple want to find what the power
would be given an alpha_level
of .07.
power.ftest(
num_df = 1,
den_df = 128,
cohen_f = .22,
alpha_level = .045,
beta_level = NULL,
liberal_lambda = FALSE
)
##
## Power Calculation for F-test
##
## num_df = 1
## den_df = 128
## cohen_f = 0.22
## alpha_level = 0.045
## beta_level = 0.3210373
## power = 67.89627
The process is simple for using power.ftest; now we can see where it is actually useful.
Let us use an example from another vignette.  In the example below, we can setup a 2*2
mixed design in ANOVA_design
(first factor, voice, is
manipulated between participants, the second factor, emotion, is
manipulated within participants). The sample size is fixed at 40
(meaning the researchers are unable to collect more than this amount) in
each between subject condition (so 80 participants in total), the
assumed population standard deviation is 1.03, the correlation for the
within factors is 0.8, and the means are 1.03, 1.21, 0.98, 1.01. We will
start by using the default alpha_level
. The outcome of
interest in this case is the interaction effect; this means we want this
particular ANOVA-level effect to be detected if it were to exist (more
so than other possible outcomes).
design_result <- ANOVA_design(design = "2b*2w",
n = 40,
mu = c(1.03, 1.41, 0.98, 1.01),
sd = 1.03,
r = 0.8,
labelnames = c("voice", "human", "robot",
"emotion", "cheerful", "sad"),
plot = TRUE)
We can then pass this design onto to the ANOVA_exact2
function to estimate the effect sizes for the this particular
design.
exact2_res = ANOVA_exact2(design_result, verbose = FALSE)
knitr::kable(exact2_res$main_results)
| power | partial_eta_squared | cohen_f | non_centrality | |
|---|---|---|---|---|
| voice | 17.31203 | 0.0132867 | 0.1160416 | 1.050321 |
| emotion | 79.00679 | 0.0914075 | 0.3171804 | 7.847066 |
| voice:emotion | 65.61040 | 0.0683053 | 0.2707638 | 5.718415 |
As we can see here we can tell that we are tad under-powered to
detect the effect of interest. Now, let us use power.ftest
to find the alpha that will get us our desired beta (in this case let us
assume .2).
power.ftest(num_df = exact2_res$anova_table$num_df[3],
den_df = exact2_res$anova_table$den_df[3],
cohen_f = exact2_res$main_results$cohen_f[3],
alpha_level = NULL,
beta_level = .2)
##
## Power Calculation for F-test
##
## num_df = 1
## den_df = 78
## cohen_f = 0.2707638
## alpha_level = 0.125566
## beta_level = 0.2
## power = 80
So, we can see that the required alpha in this case is approximately .12. However, what would be the optimal alpha?
Now, let us use this same approach in the optimal_alpha
function.
res5 = optimal_alpha("power.ftest(num_df = exact2_res$anova_table$num_df[3],
den_df = exact2_res$anova_table$den_df[3],
cohen_f = exact2_res$main_results$cohen_f[3],
alpha_level = x)$power/100",
error = "minimal")
print(res5)
##
## Optimal Alpha
## Alpha Beta Weighted.Combined.Error.Rate
## 1 0.1417106 0.1826088 0.1621597
##
## From power function:
## [1] "power.ftest(num_df = exact2_res$anova_table$num_df[3],\n den_df = exact2_res$anova_table$den_df[3],\n cohen_f = exact2_res$main_results$cohen_f[3],\n alpha_level = x)$power/100"
Interestingly the values for alpha and beta are fairly close to the
calculations we made with power.ftest
alone.
Finally, we can extend everything we’ve done to a convenience
function ANOVA_compromise
. This way we can simply pass on
the design from ANOVA_design
and the optimal alpha can be
determined for every comparison we select in a study.
comp_res = ANOVA_compromise(design_result,
emm = TRUE)
You’ll notice it takes a lot longer to run
ANOVA_compromise
than ANOVA_exact
or
ANOVA_exact2
, but overall the options (such as
emm = TRUE
) are the same. Now, we can go through the
results one-by-one.
#ANOVA results
knitr::kable(comp_res$aov_comp)
| effect | cohen_f | num_df | den_df | alpha | beta | objective |
|---|---|---|---|---|---|---|
| voice | 0.1160416 | 1 | 78 | 0.2793550 | 0.5064869 | 0.3929210 |
| emotion | 0.3171804 | 1 | 78 | 0.1035704 | 0.1251595 | 0.1143650 |
| voice:emotion | 0.2707638 | 1 | 78 | 0.1417106 | 0.1826088 | 0.1621597 |
#MANOVA results
knitr::kable(comp_res$manova_comp)
| effect | cohen_f | num_df | den_df | alpha | beta | objective |
|---|---|---|---|---|---|---|
| (Intercept) | 1.1423652 | 1 | 78 | 0.0000060 | 0.0000005 | 0.0000033 |
| voice | 0.1160416 | 1 | 78 | 0.2793550 | 0.5064869 | 0.3929210 |
| emotion | 0.3171804 | 1 | 78 | 0.1035704 | 0.1251595 | 0.1143650 |
| voice:emotion | 0.2707638 | 1 | 78 | 0.1417106 | 0.1826088 | 0.1621597 |
#emmeans results
knitr::kable(comp_res$emmeans_comp)
| effect | cohen_f | num_df | den_df | alpha | beta | objective |
|---|---|---|---|---|---|---|
| voice_human emotion_cheerful - voice_robot emotion_cheerful | 0.0244637 | 1 | 78 | 0.3185352 | 0.6703282 | 0.4944317 |
| voice_human emotion_cheerful - voice_human emotion_sad | 0.4157393 | 1 | 78 | 0.0464936 | 0.0511495 | 0.0488216 |
| voice_human emotion_cheerful - voice_robot emotion_sad | 0.0097855 | 1 | 78 | 0.3201049 | 0.6781016 | 0.4991032 |
| voice_robot emotion_cheerful - voice_human emotion_sad | 0.2103880 | 1 | 78 | 0.1983048 | 0.2862636 | 0.2422842 |
| voice_robot emotion_cheerful - voice_robot emotion_sad | 0.0328215 | 1 | 78 | 0.3170422 | 0.6630352 | 0.4900387 |
| voice_human emotion_sad - voice_robot emotion_sad | 0.1957098 | 1 | 78 | 0.2123057 | 0.3167599 | 0.2645328 |
In addition, we can extract the optimal alpha plots for any of the
comparisons outlined above. These can be found in
aov_plotlist
, manova_plotlist
, and
emmeans_plotlist
.
comp_res$aov_plotlist
## $voice
##
## $emotion
##
## $`voice:emotion`


Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
2nd Additional Bench STATE CONSUMER DISPUTES REDRESSAL COMMISSION, PUNJAB DAKSHIN MARG, SECTOR 37-A, CHANDIGARH First Appeal No. 188 of 2014 Date of institution: 28.2.2014 Date of Decision: 17.11.2015 Manohar Lal Garg Son of Chranji Lal son of Sant Ram R/o Mandir Wali Gali, Mansa, presently residing at Flat No. 3231, paradise Enclave, Sector 50-D, Chandigarh. Appellant/OP No.1 Versus 1. Shama Rani wife of Sh. Prem Pal son of Suresh Kumar, Near Post Office, Samana, District Patiala. Respondent No.1/Complainant 2. Punjab State Urban Development Authority (PUDA) through its Chief Administrator, Chandigarh (Notice not issued) 3. Punjab State Urban Development Authority (PUDA) through Licensing Authority, PUDA Bhawan, Sector 32, Mohali, Chandigarh (Notice not issued) 4. Alka Garg Wife of Rishi Pal son of Banarsi Dass, resident of Bhagwan Mahavir Street, Tehsil Road, Samana, District Patiala (Notice not issued) Respondent Nos.2 to 4/Op Nos. 2 to 4 First Appeal against the order dated 16.1.2014 passed by the District Consumer Disputes Redressal Forum, Mansa. Quorum:- Shri Gurcharan Singh Saran, Presiding Judicial Member Shri Jasbir Singh Gill, Member Mrs. Surinder Pal Kaur, Member Present:- For the appellant : Sh. P.M. Goyal, Advocate For respondent No.1 : Sh. R.K. Jindal, Advocate For respondent Nos.2&3 : Sh. Balwinder Singh, Advocate For respondent No.4 : Ex.-parte. First Appeal No. 188 of 2014 2 Gurcharan Singh Saran, Presiding Judicial Member ORDER
This order will dispose of 13 appeals, particulars of which are as under:-
Sr. No. Appeal No. Party Names Consumer Date of Complaint Decision of No. the complaints (Appellant) (Respondents)
1. F.A. No. 188 of Manohar Lal Shama Rani & CC No. 144 16.1.2014 2014 Garg Others of 2013
2. F.A. No. 189 of Manohar Lal Vinit Goel & CC No. 146 16.1.2014 2014 Garg Others of 2013
3. F.A. No. 190 of Manohar Lal Santosh Rani CC No. 148 16.1.2014 2014 Garg & Others of 2013
4. F.A. No. 191 of Manohar Lal Geeta Garg & CC No. 147 16.1.2014 2014 Garg Others of 2013
5. F.A. No. 192 of Manohar Lal Manju Goyal & CC No. 145 16.1.2014 2014 Garg Others of 2013
6. F.A. No. 193 of Manohar Lal Chander CC No. 149 16.1.2014 2014 Garg Kanta & of 2013 Others
7. F.A. No. 194 of Manohar Lal Khuaish CC No. 150 16.1.2014 2014 Garg Kumar & of 2013 Others
8. F.A. No. 982 of Manohar Lal Hardeep CC No. 47 5.6.2014 2014 Garg Goyal & of 2014 Others
9. F.A. No. 983 of Manohar Lal Shivji Ram & CC No. 28 5.6.2014 2014 Garg Others of 2014
10. F.A. No. 984 of Manohar Lal Amrit Pal Garg CC No. 27 5.6.2014 2014 Garg & Others of 2014
11. F.A. No. 985 of Manohar Lal Moti Ram & CC No. 29 5.6.2014 2014 Garg Others of 2014
12. F.A. No. 986 of Manohar Lal Surinder CC No. 33 5.6.2014 2014 Garg Kumar Goyal of 2014 & Others
13. F.A. No. 987 of Manohar Lal Niraj Gupta & CC No. 30 5.6.2014 2014 Garg Others of 2014 First Appeal No. 188 of 2014 3 which are arising out of the orders dated 16.1.2014 and 5.6.2014 passed in Consumer Complaint Nos. 144 of 2013, 150 of 2013, 146 of 2013, 145 of 2013, 147 of 2013, 148 of 2013, 149 of 2013, 47 of 2014, 28 of 2014, 27 of 2014, 29 of 2014, 33 of 2014 and 30 of 2014 by the District Forum, Mansa vide which Op No. 1 was directed to develop Shakti Nagar as per the specifications and terms and conditions of the PUDA within a period of six months from the date of receipt of copy of the order. He was further directed to compensate the complainant to the extent of Rs. 30,000/- in each complaint. The amount be paid within a period of one month from the receipt of the copy of the order, failing which it will carry interest @ 9% p.a. from the date of order.
2. The facts have been taken from First Appeal No. 188 of 2014 arising out of complaint No. 144 of 2013. The complainant had filed a complaint against the Ops under Section 12 of the Consumer Protection Act, 1986(in short 'the Act') on the averments that Op No. 1 had developed a colony under the name and style of Shakti Nagar at College Road, Mansa after obtaining licence No. LDC/2001/73 dated 12.3.2011 from Op No. 2 for development and promotion of the colony under the PUDA rules and regulations. As per the licence issued by OP No. 1, colony in question was to be developed within a period of three years. OP No. 4 had purchased a plot No. 11 for a consideration of Rs. 1,50,000/- vide sale deed No. 5357 dated 21.12.2001 registered with Sub Registrar, Mansa on 4.1.2002. Op No. 4 was in need of money and on assurance of OP No. 1 to develop the colony within months, complainant purchased plot No. 11 First Appeal No. 188 of 2014 4 for a consideration of Rs. 4,10,000/- from Op No. 4 vide sale deed No. 7223 dated 17.1.2012 registered with Sub Registrar on 18.1.2012. Accordingly, the complainant had come into the footsteps of OP No. 4 and was entitled to the same rights as were available to Op No. 4. OP No. 1 did not develop the colony as per the terms and conditions of the licence to provide facilities as per specifications i.e. water supply, electricity, roads, parks, sewerage and other basic amenities till date, rather he had got extension of the licence till 11.3.2006. The complainant and other plot holders requested Op Nos. 1 & 2 time and again but none of the Op had paid any heed to the request of the plot holders. The complainant had suffered physical and mental harassment, agony and humiliations as well as monetary loss as he failed to construct the house to enjoy the better residential facilities. The act and conduct of the Ops amounted to unfair trade practice as well as deficiency in service. Hence, the complaint with a direction to Op Nos. 1 to 3 to develop and promote the colony as per specifications, terms and conditions and rules and regulations of the Licencing Authority. They be also directed to pay compensation of Rs. 4,99,000/- alongwith interest @ 18% p.a. and cost of litigation.
3. The notice was issued only to OP No. 1 and no notice was issued to Op Nos. 2 to 4 because Op No. 2 & 3 are only the Licencing Authority and not a service provider whereas Op No. 4 had already sold the plot in favour of the complainant. Op No. 1 in its written version took the preliminary objections that Op No. 1 had already executed sale deed No. 5357 dated 21.12.2001 in favour of First Appeal No. 188 of 2014 5 Op No. 4 i.e. contract between the parties, which can be enforced through Civil Court, therefore, this Forum had no jurisdiction to enforce an agreement. The possession of the plot was handed over to the complainant on the basis of "as is where is". OP No. 1 had already deposited a sum of Rs. 24,76,945/- as cost of external development work with PUDA, who is to provide such work. He had already provided internal water lines, internal sewerage lines and boundary wall of 11 feet height from the original earth level. Each plot has been demarcated, green zone was demarcated, trees, plants and grass was planted. Most of the basic facilities required to be provided by this Op has been provided. Since the plot holders had not started the construction at the spot, therefore, extension of the licence was mandatory. Otherwise plots could be resumed by the PUDA. It was specifically mentioned in the Sale Deed that Op will provide basic amenities in the colony with the cooperation of all the plot holders and parties were to be governed by the terms and conditions of the contract and the rules and regulations of the PUDA. The complainant had purchased a plot from OP No. 4 with an intention to further sell it for a premium, therefore, he had violated the conditions of sale deed No. 2999 dated 10.9.2002, therefore, he was not entitled to file any complaint; complaint was barred by limitation; complaint was bad for non-joinder of necessary parties. It is only the PUDA, who was to determine whether Op had violated the terms and conditions of the licence but no notice was given by the District Forum to the PUDA. After basic facilities were provided by this OP then purchasers were to maintain the colony with their own funds and that the Hon'ble First Appeal No. 188 of 2014 6 Forum had no jurisdiction to entertain this complaint as the procedure under the Act is summary procedure whereas it required voluminous evidence and cross-examination of the witnesses, therefore, the matter be relegated to the Civil Court. On merits, it was admitted that OP No. 1 had taken licence No. LDC/2001/73 from OP No. 2 and it was renewed till March, 2013. Originally OP No. 4 had purchased plot No. 11 from OP No. 1 vide Sale Deed No. 5357 dated 21.12.2001 and the complainant has purchased this plot from Op No. 4. Op No. 4 had violated the terms and conditions of the PUDA by selling the plot in favour of the complainant. There was no privity of contract between the complainant and this Op, therefore, the complaint by the complainant against this Op was not maintainable. Extension of period of the licence given by the PUDA was within the rights of the PUDA. Most of the basic facilities have been provided, therefore, there was no unfair trade practice and deficiency in service on the part of this Op. Complaint was without merit and it be dismissed.
4. The parties were allowed by the learned District Forum to lead their evidence.
5. In support of his allegations, the complainant had tendered into evidence his affidavit Ex. C-1, renewal certificate Ex. C- 2, sale deed Ex. C-3, sale deed Ex. C-4, letter by DDA Ex. C-5, Rapat of Local Commissioner Ex. C-6. On the other hand, OP No. 1 had tendered into evidence affidavit of Manohar Lal Garg Ex. Op-1, sale deed Ex. OP-2, judgment dt. 6.5.2013 Ex. Op-3, sale deed Ex. Op-4, sale deed Ex. Op-5, licence copy Ex. Op-6, letter dt. 19.8.08 First Appeal No. 188 of 2014 7 Ex. Op-7, letter dt. 26.3.09 Ex. Op-8, letter dt. 25.8.08 Ex. Op-9, renewal certificate Ex. Op-10.
6. After going through the allegations in the complaint, written reply filed by OP No.1, evidence and documents brought on the record, the complaint was allowed as referred above.
7. Aggrieved with the order passed by the learned District Forum, appellant/OP No.1 has filed the present appeal.
8. We have heard the learned counsel for the parties.
9. It has been argued by the counsel for the OP No. 1 that the complaint is barred by limitation. Op No. 4 Smt. Alka Garg had purchased the plot in the year 2001 and in case the basic amenities as pleaded in the complaint were not provided by Op No. 1 then the complaint should have been filed within a period of two years after execution of the sale deed in favour of the complainant, in that way, the complaint should have been filed in the year 2003 but the complaint was filed in the year 2013, therefore, it is clearly barred by limitation. The counsel for the appellant has referred certain judgments i.e. Civil Appeal No. 4962 of 2002 "Kandimalla Raghavaiah & Co. versus National Insurance Co. & Anr." decided on 10.7.2009 and Civil Appeal No. 2067 of 2002 "State Bani of India versus M/s B.S. Agricultural Industries (I)" decided on 20.3.2009 by the Hon'ble Apex Court wherein it has been observed that the complaint is to be filed within two years of the cause of action. There is no dispute with regard to the law point settled by the Hon'ble Supreme Court in the above referred judgment but we have to First Appeal No. 188 of 2014 8 determine as to when the cause of action had arisen in favour of the complainant or whether it was a continuous cause of action.
10. Whereas the counsel for complainant has argued that no doubt that Alka Garg was the original owner but after the complainant purchased this plot from Alka Garg, the complainant had come in the footsteps of Alka Garg and he will be entitled to all the rights in the property, which were available to Alka Garg. The counsel for the complainant further stated that Op No. 1 being Developer had taken a licence from Op No. 2 to develop and promote the colony and he was required to provide all the basic amenities as per the terms and conditions of the licence, but he has failed to provide these facilities. In case the facilities are not provided then it will be a continuous cause of action. Even full amenities have not been provided so far as is clear from the written version filed by Op No. 1. In para No. 1 of the preliminary objections, he has stated that most of the basic facilities required to be provided by this Op has been provided by this Op, which shows that all the facilities have not been provided, therefore, it will be a continuous cause of action till all the basic amenities are not provided, therefore, the complaint was not barred by limitation. When this point was dealt with by the District Forum, it was discussed that Op No. 1 has not provided the basic amenities. Originally the licence was valid for a period of three years but lateron, it was extended from time to time and lastly it was extended upto 11.3.2013. Therefore, two years can be counted from that date and in case the limitation is taken from that date, then the compliant is within limitation. A reference can be made to the judgment of the Hon'ble Maharashtra First Appeal No. 188 of 2014 9 State Consumer Disputes Redressal Commission, Mumbai 2015(3) CLT 139 "Samuel Dorman versus M/s Superier Builders & Ors.". In that case, there was delay in delivery of possession. Plea of the Op was that the complaint is barred by limitation as it was filed beyond two years from the date of cause of action. It was observed that the builder has failed to fulfil his obligation to complete the construction of flat. Hence, it can be concluded that there is a continuous cause of action and the complaint is well within limitation. Here also in this case Op No. 1 has failed to fulfil his obligation with regard to provide all the basic amenities and the complaint against the Op is with regard to completion of basic amenities so that he could raise the construction and till these obligations are not completed, it will be a continuous cause of action, therefore, we are of the opinion that the District Forum was correct in its findings that the complaint is within limitation and we affirm the findings so recorded by the District Forum.
11. The next point raised by the counsel for Op No. 1 is that the complainant is not a consumer of the Op. It has been argued by the counsel for the Op No.1 that the plot was sold to respondent No. 4 Alka Garg, therefore, the basic contract was with Alka Garg and there was no contract between the complainant, therefore, there was no relationship of consumer and service provider. No doubt that originally the plot was allotted to Alka Garg but after purchasing this plot from Alka Garg, the complainant has come in the footsteps of Alka Garg. Whether it is Alka Garg or the complainant, the Op was to provide the basic amenities as agreed by him at the time of taking the First Appeal No. 188 of 2014 10 licence from the PUDA and in case he has failed to provide the basic amenities as agreed then certainly, there is deficiency in service on the part of Op. In case the complainant has purchased the plot from Alka Garg then he has purchased all the rights and obligations from Alka Garg, therefore, in case the complainant has come in the footsteps of Alka Garg then we do not agree with the plea raised by the counsel for Op No. 1 that there was no relationship of consumer and service provider between the parties. In case there was relationship of consumer and service provider between Alka Garg and Op No. 1, the same relationship will remain as it is between the complainant and Op No. 1, therefore, Op No. 1 cannot raise this plea that there was no relationship of consumer and service provider between the complainant and Op No. 1.
12. It is next argued that PUDA was a necessary party. As final certificate was to be given by the PUDA but no notice was given to the PUDA. At the time he had taken the licence from PUDA to develop and promote the colony, he had taken certain obligations while developing the colony i.e. to provide the basic amenities to the plot holders. The same has been incorporated in the licence Ex. Op-6 and reads as under:-
"i) The design and specifications of the development works to be provided in the colony shall include:-
(a) metalling of roads and paving of footpaths as per Public Works Department specifications;
(b) turling and plantation of trees; and
(c) street lighting.First Appeal No. 188 of 2014 11
ii) The licencee shall enter into an agreement with the competent authority in Form APR IV within a period of thirty days of the grant of the licence;
iii) The promoter shall deposit with the Competent Authority service charges under section 32 of the Punjab Apartment and Property Regulation Act, 1995;
iv) In the layout plan of the colony, the land reserve roads, open spaces, schools, public and community building and other common uses shall not be less than 41.67% percent of the gross area of the land under the colony;
v) The licencee shall not contravene the provisions of any other law for the time being enforce in the area where the colony is being developed;
vi) The promoter shall maintain a separate account in any Schedule Bank of sums taken by him from persons intending to take or who have taken by apartments or plots, as advance, towards the sale price or for any other purpose or deposit and shall disburse the money for meeting the cost development works, and shall on demand, in writing, by the competent authority, make full and true disclosure of all transactions in respect of that account:
vii) The licence is valid for a period of three years commencing from 12.3.2001 and ending with 11.3.2004 and licencee shall complete the development works within the period;First Appeal No. 188 of 2014 12
ix) The promoter shall carry out and complete the development of the land in accordance with the provisions of the Urban Land (Ceiling and Regulation) Act, 1976(Central Act 33 of 1976) and other laws for the time being in force.
x) The road formation levels will be got approved from the S.E. Patiala before the execution of the work. The plinth levels of the buildings will be kept 0.45 Mtr. above the road level.
xi) Electrical works will be carried out as per PSEB/PUDA specifications under the supervision of PSEB Authorities.
xii) The promoter shall pay the external development charges liveable U/s 5(5) of the P.A.P.R. Act - 1995. Detailed letter in this regard is being issued separately. This licence will be governed by the provisions of the Water (Prevention & Control of the Pollution) Act, 1974 & the Air (Prevention & Control of Pollution) Act, 1981 & as amended from time to time & rules made thereunder."
13. Op No. 1 had applied for extension in the licence and Officers of the PUDA had visited the spot on 3.9.2012 and they had made the following observations:-
"1. Water Supply: Pipe is there but OHSR has not been provided. There was open storage tank and it was intimated that efforts are being made to get the water supply connection from M.C. Mansa.
2. Sewerage System:- Sewerage services were provided but there was no vent shaft in sewerage lines. Manholes were not covered and there was no sewerage treatment plant. First Appeal No. 188 of 2014 13
3. Horticulture :- Road plants was there but parks were not maintained.
4. Electricity:- HT lines were against the norms. No plan was approved by PSPCL. LT lines were erected but there was no pole alignment and there was no provision for street light.
Therefore, even in 2012 the basic amenities were not complete as per the inspection conducted by the Officers of the PUDA that may be the reason that the period of licence to OP No. 1 was extended by PUDA the licencing authority, therefore, all the basic amenities were to be provided by Op No. 1. Therefore, complaint is not bad for non- issuance of the notice to the PUDA as PUDA is only the Licencing Authority.
14. Apart from the report of the Officers of the PUDA, during pendency of similar complaint, the District Forum had appointed Smt. Rekha Sharma, Advocate, as a Local Commissioner, who on 29.9.2008 had submitted her report that except one plot there is no other construction in the colony. She further reported that septic tank was un-covered. Sewerage system was not completed. Water supply was incomplete as there was no tank built up for storage of the clean water. No tubewell was installed inside the colony nor any other source of water connected for water supply system. Electric poles for electric supply were not erected. There was no drainage system in the colony. Even otherwise during the course of arguments, it has been argued by the counsel for Op No. 1 that they have taken up the matter with various Departments to provide the basic amenities, therefore, it is for the Department to give the clearance at the earliest First Appeal No. 188 of 2014 14 possible time. Here it is pertinent to note that the plots were demarcated in the year 2001 but it is to be seen whether the efforts were made by Op No. 1 to provide these facilities and when the matter was taken up by Op No. 1 with the various departments. Apart from his own statement Ex. Op-1, he has placed on the record copy of the sale deed Ex. Op-2, order of the District Forum Ex. Op-3, sale deed executed by Alka Garg in favour of Ex. Op-4, licence Ex. Op-6, letter was written to PUDA for extension of the licence Ex. Op-7, Ex. Op-8 is the renewal letter, which was renewed for the period of three years in 2009. Ex. Op-9 is another letter vide which the licence was extended from 13.8.2006 to 12.8.2009 on the original terms and conditions. Ex. Op-10 is original certificate vide which the licence was extended upto 11.3.2013. Therefore, no letter has been placed on the record, which was written by Op No. 1 to other Departments for providing the basic amenities. In the appeal file, he has placed same documents and with regard to NOC of waste water treatment plant, which was written in the year 2013. A letter dated 5.11.2013 was written to the Chief Engineer (Commercial), PSPCL , Punjab, therefore, in case he has taken the matter with the Departments in 2012 and 2013 then certainly, there is deficiency in service on the part of Op No. 1 because he did not take up the matter with various departments, which was required to be done by him for providing the basic amenities immediately after carving out the colony in the year 2001. Therefore, no plea can be raised by the counsel for the appellant that he has raised the matter with the concerned Departments and that the Departments are not prompt in giving the First Appeal No. 188 of 2014 15 response. In case the matter would have been taken immediately after carving out the colony, by this time everything would have been 'OK'. Therefore, the burden cannot be shifted to the Department when OP No. 1 himself was in default for not taking the matter with the concerned Departments at appropriate time.
15. No other point has been argued before us.
16. In view of the above discussion, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
17. The appellant in F.A. No. 188 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
18. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 189 OF 2014
19. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and Op No. 4 had purchased Plot No. 40 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 2999 dated 10.9.2002, which was lateron purchased by the complainant from Op No. 4 for a consideration of Rs. 1,72,000/- vide sale deed No. 3936 dated First Appeal No. 188 of 2014 16 6.11.2006. Accordingly, the complainant had come to the footsteps of Op No. 4 and was entitled to same rights as were available to Op No.
4. Op No. 1 failed to provide facilities as per specifications.
20. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
21. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
22. The appellant in F.A. No. 189 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
23. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 190 OF 2014
24. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and Op No. 4 had purchased Plot No. 44 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 356 dated 2.5.2002, which was lateron purchased by the complainant from Op No. 4 for a First Appeal No. 188 of 2014 17 consideration of Rs. 2,85,000/- vide sale deed No. 1790 dated 8.7.2008. Accordingly, the complainant had come to the footsteps of Op No. 4 and was entitled to same rights as were available to Op No.
4. Op No. 1 failed to provide facilities as per specifications.
25. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
26. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
27. The appellant in F.A. No. 190 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
28. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 191 OF 2014
29. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and Op No. 4 had purchased Plot No. 41 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 4556 dated 19.11.2001, First Appeal No. 188 of 2014 18 which was lateron purchased by the complainant from Op No. 4 for a consideration of Rs. 4,10,000/- vide sale deed No. 858 dated 9.5.2011. Accordingly, the complainant had come to the footsteps of Op No. 4 and was entitled to same rights as were available to Op No.
4. Op No. 1 failed to provide facilities as per specifications.
30. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
31. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
32. The appellant in F.A. No. 189 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
33. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 190 OF 2014
34. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and the complainant had purchased Plot No. 13 for a sale consideration of First Appeal No. 188 of 2014 19 Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 5358 dated 21.12.2001. Op No. 1 failed to provide facilities as per specifications.
35. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
36. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
37. The appellant in F.A. No. 192 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
38. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 193 OF 2014
39. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and Op No. 4 had purchased Plot No. 12 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 5356 dated 21.12.2001, which was lateron purchased by the complainant from Op No. 4 for a consideration of Rs. 4,10,000/- vide sale deed No. 7222 dated First Appeal No. 188 of 2014 20 17/18.1.2012. Accordingly, the complainant had come to the footsteps of Op No. 4 and was entitled to same rights as were available to Op No. 4. Op No. 1 failed to provide facilities as per specifications.
40. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
41. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
42. The appellant in F.A. No. 193 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
43. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 194 OF 2014
44. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and Op No. 4 had purchased Plot No. 41 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 5704 dated 14.3.2003, First Appeal No. 188 of 2014 21 which was lateron purchased by the complainant from Op No. 4 for a consideration of Rs. 4,10,000/- vide sale deed No. 4612 dated 13.9.2011. Accordingly, the complainant had come to the footsteps of Op No. 4 and was entitled to same rights as were available to Op No.
4. Op No. 1 failed to provide facilities as per specifications.
45. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
46. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
47. The appellant in F.A. No. 194 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
48. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 982 OF 2014
49. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and the complainant had purchased Plot No. 52 for a sale consideration of First Appeal No. 188 of 2014 22 Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 150 dated 10.4.2003. Op No. 1 failed to provide facilities as per specifications.
50. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
51. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
52. The appellant in F.A. No. 982 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
53. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 983 OF 2014
54. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and the complainant had purchased Plot No. 47 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 3435 dated 13.8.2001. Op No. 1 failed to provide facilities as per specifications. First Appeal No. 188 of 2014 23
55. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
56. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
57. The appellant in F.A. No. 983 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
58. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 984 OF 2014
59. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and the complainant had purchased Plot No. 19 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 3429 dated 13.8.2001. Op No. 1 failed to provide facilities as per specifications.
60. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum. First Appeal No. 188 of 2014 24
61. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
62. The appellant in F.A. No. 984 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
63. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 985 OF 2014
64. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and the complainant had purchased Plot No. 28 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 3432 dated 13.8.2001. Op No. 1 failed to provide facilities as per specifications.
65. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
66. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these First Appeal No. 188 of 2014 25 circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
67. The appellant in F.A. No. 985 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
68. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 986 OF 2014
69. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and the complainant had purchased Plot No. 7 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 3428 dated 13.8.2001. Op No. 1 failed to provide facilities as per specifications.
70. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
71. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
First Appeal No. 188 of 2014 26
72. The appellant in F.A. No. 986 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
73. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
FIRST APPEAL NO. 987 OF 2014
74. Brief facts of the case are that Op No. 1 had developed a colony in the name of "Shakti Nagar" at College Road, Mansa and Op No. 4 had purchased Plot No. 26 for a sale consideration of Rs. 1,50,000/- from Op No. 1 vide Sale Deed No. 3442 dated 13.8.2001, which was lateron purchased by the complainant from Op No. 4 for a consideration of Rs. 1,50,000/- vide sale deed No. 2463 dated 1.7.2003. Accordingly, the complainant had come to the footsteps of Op No. 4 and was entitled to same rights as were available to Op No.
4. Op No. 1 failed to provide facilities as per specifications.
75. The reply filed by Op No. 1 is similar as stated in Appeal No. 188 of 2014 and similar order was passed by the District Forum.
76. The points taken in the appeal are similar as taken in F.A. No. 188 of 2014 and with regard to the findings, the findings so recorded in F.A. No. 188 of 2014 be also read in this appeal. In these First Appeal No. 188 of 2014 27 circumstances, we do not see any merit in this appeal and the same is hereby dismissed with no order as to costs.
77. The appellant in F.A. No. 987 of 2014 had deposited an amount of Rs. 15,000/- with this Commission in the appeal. This amount with interest accrued thereon, if any, be remitted by the registry to respondent No.1/complainant by way of a crossed cheque/demand draft after the expiry of 45 days, from the despatch of the order to the parties; subject to stay, if any, by the higher Fora/Court.
78. Remaining amount, if any due, shall be paid by appellant to respondent No.1/complainant within 30 days from the receipt of the copy of the order.
79. The arguments in these appeals were heard on 5.11.2015 and the order was reserved. Now the order be communicated to the parties as per rules.
80. The appeals could not be decided within the statutory period due to heavy pendency of Court cases.
81. Copy of the order be placed on other appeals except F.A. No. 188 of 2014.
(Gurcharan Singh Saran) Presiding Judicial Member (Jasbir Singh Gill) Member November 17, 2015. (Surinder Pal Kaur) as Member First Appeal No. 188 of 2014 28


Back to Random
Convert Clipboard
Copy Code
Using FactCheck:
What am I even looking at?
This is a script for converting
Codewars
tests to
Julia FactCheck
tests. It doesn't really parse the JavaScript, it's just a gauntlet of regex.


Note: When enabled, download progress will not show in the browser until the entire song is downloaded.
Adds ID3v2 metadata tags to all tracks downloaded that have the .mp3 extension. Metadata data is fetched from SoundCloud's API.
The added metadata includes: cover art, title, album artist, genres, duration, release year, bpm, artist url, audio source url, and description.
All tracks will be downloaded in mp3 format. This ensures that metadata will always be added when the 'Add Metadata to mp3 files' option is enabled.
If this option is disabled, the original uploaded format of a track (often of higher quality format) will take precedence when downloading. However, metadata will not be added to non-mp3 files.
Before metadata is added and the file name is established, if the track title contains a substring matching the provided regular expression pattern, the matching part will be removed.
The default setting attempts to remove strings containing 'Free Download' or 'Download Link' patterns that appears in the end of popular track titles.
When entering a custom regular expression, make sure it conforms to Javascript's RegExp format. The provided regex string will be passed into a RegExp constructor with the global flag turned off and the case insensitive flag turned on.


The MultiInstanceComposite actor may be used to instantiate identical processing blocks within a model. See the javadoc MultiInstanceComposite documentation for details.


League
| League Name | |
| League Rank | |
| Members | |
| Record | |
| Points For | |
| Points Against | |
Current Tournament Countdown
Fan Favorites Progress
Terry Porter
Mark Madsen
Bo Outlaw
Brian Scalabrine
A friendly and competitive league for NBA Live Mobile.
| League Name | |
| League Rank | |
| Members | |
| Record | |
| Points For | |
| Points Against | |
Terry Porter
Mark Madsen
Bo Outlaw
Brian Scalabrine
| Username | Franchise Overall | Role | Available for Tournaments |
|---|---|---|---|
If you are interested in joining our League or you just want to say hi you can use our private chat on the bottom right corner and a League Admin will be with you shortly.


In this example Tau is 5 for students that don't participate in post-school program (post-school program = 0), and Tau is 10 for students that participate in post-school program (post-school program = 1).
The true sample average treatment effect (SATE) = 7. However, the difference in means, 88.2 - 68.4 = 19.8, cannot recover the true SATE, because the groups whose outcomes we compare differ in their pre-treatment characteristics.
Only those students who don’t participate in the postschool program select into the treatment, and their pre-treatment scores are higher than students who participate in the post-school program.
| Postschool Program | Pre-treatment Score | Treatment | Potential Outcomes | Observed Outcomes | ||
|---|---|---|---|---|---|---|
| Student | X1 | X2 | Z | If Z =1, Y1 | If Z = 0, Y0 | Y |
| Blake | 0 | 87 | Yes | 95 | 90 | 95 |
| Kennedy | 1 | 70 | No | 80 | 70 | 70 |
| Jordan | 1 | 64 | No | 75 | 65 | 65 |
| Taylor | 0 | 71 | Yes | 77 | 72 | 77 |
| Billie | 0 | 80 | Yes | 87 | 82 | 87 |
| Charlie | 1 | 65 | No | 76 | 66 | 66 |
| Casey | 0 | 78 | Yes | 86 | 81 | 86 |
| Alex | 0 | 88 | Yes | 96 | 91 | 96 |
| Parker | 0 | 71 | No | 77 | 72 | 72 |
| Andi | 1 | 69 | No | 79 | 69 | 69 |
| Postschool Program | Pre-treatment Score | Treatment | Potential Outcomes | Observed Outcomes | ||
|---|---|---|---|---|---|---|
| Student | X1 | X2 | Z | If Z =1, Y1 | If Z = 0, Y0 | Y |
| Blake | 0 | 87 | Yes | 95 | ? | 95 |
| Kennedy | 1 | 70 | No | ? | 70 | 70 |
| Jordan | 1 | 64 | No | ? | 65 | 65 |
| Taylor | 0 | 71 | Yes | 77 | ? | 77 |
| Billie | 0 | 80 | Yes | 87 | ? | 87 |
| Charlie | 1 | 65 | No | ? | 66 | 66 |
| Casey | 0 | 78 | Yes | 86 | ? | 86 |
| Alex | 0 | 88 | Yes | 96 | ? | 96 |
| Parker | 0 | 71 | No | ? | 72 | 72 |
| Andi | 1 | 69 | No | ? | 69 | 69 |
| Postschool Program | Pre-treatment Score | Treatment | Potential Outcomes | Observed Outcomes | ||
|---|---|---|---|---|---|---|
| Student | X1 | X2 | Z | If Z =1, Y1 | If Z = 0, Y0 | Y |
| Blake | 0 | 87 | Yes | 95 | ? | 95 |
| Kennedy | 1 | 70 | No | ? | 70 | 70 |
| Jordan | 1 | 64 | No | ? | 65 | 65 |
| Taylor | 0 | 71 | Yes | 77 | ? | 77 |
| Billie | 0 | 80 | Yes | 87 | ? | 87 |
| Charlie | 1 | 65 | No | ? | 66 | 66 |
| Casey | 0 | 78 | Yes | 86 | ? | 86 |
| Alex | 0 | 88 | Yes | 96 | ? | 96 |
| Parker | 0 | 71 | No | ? | 72 | 72 |
| Andi | 1 | 69 | No | ? | 69 | 69 |