REPORTABLE IN THE SUPREME COURT OF INDIA CRIMINAL APPELLATE JURISDICTION CRIMINAL APPEAL NO. 9 OF 2002 Gujarat Pollution Control Board ....Appellant Versus M/s Nicosulf Industries & Export Pvt. Ltd. and Ors. ....Respondents JUDGMENT
Dr. ARIJIT PASAYAT, J
1. Challenge in this appeal is to the judgment of a learned Single Judge of the Gujarat High Court allowing the Revision Petition filed by the respondents 1 and 2.
2. A complaint under Sections 24, 25, 43, 44 and 47 of the Water (Prevention and Control of Pollution) Act, 1974 (in short the `Act') was 1 filed by the Assistant Environmental Engineer on behalf of the Gujarat Pollution Control Board (in short the `Board') against a private limited company i.e. M/s Nicosulf Industries & Exports Private Limited-respondent no.1 and its co-directors Kishanbhai M. Narsinh, Mihirbhai G. Virji and Dushyant P. Lejawala alleging inter-alia that the accused nos. 2, 3 and 4 are producing Nicotine Sulphate in their factory and using Tobacco Stuff, Lime, Kerosene and Sulphuric Acid as raw-materials, and during the course of the process of production they are discharging 10,800 litres of polluted water every day. Under sections 24 and 25 of the Act, every industry is compulsorily required to obtain prior permission or approval of the Board for discharging its polluted water used by it either within or outside the industry as per section 25(i) of the Act. Permission was granted by imposing certain conditions to the accused persons. If the industry commits breach of conditions, complaint can be filed, which in the instant case was filed alleging that there was breach of condition no.4, as a result of which, under condition no.7, the consent order automatically lapsed. The accused nos.2, 3 and 4 were said to be responsible officers managing day-to-day affairs of the company. On 22-6-1989, a sample of polluted water was collected from the industry. It was analysed by the Laboratory of the Board, which reported that the effluent did not conform to the prescribed standards. 2 The report of the analyst was given on 8-7-1989. Thereafter, show-cause notice was issued to the accused persons. A complaint was accordingly filed.
3. The learned Magistrate convicted all the four accused under sections 24, 25, 43 and 44 of the Act.
4. The judgment of the Lower Appellate Court was challenged on four grounds before the High Court.
5. The first ground of attack was that the complainant had no authority to file the complaint. Hence, the entire prosecution structure collapsed and order of conviction and sentence against the revisionists cannot be maintained. The second ground of attack was that the offence was alleged to have been committed by the Company and the directors of the company can be held liable only when it is established by the prosecution that the directors were managing day to day affairs of the company. The third attack was that even on merits breach of condition No.4 of the consent or permission order is not established. The last attack was that the sample of alleged polluted water was collected in breach of the provisions of Section 21 of the Act.
3
6. Main ground of challenge is that the complainant had no authority to file the complaint and this ground alone was sufficient to set aside the order of conviction and sentence maintained by the first Appellate Court.
7. Reference was made to the complaint which shows that it was filed by one AA Dalauti, Assistant Environmental Engineer on behalf of the appellant-Board. It was pointed out that Shri Dalauti had no delegated authority as required under Section 49 of the Act and as such the complaint was filed by an incompetent person. Reference was made to Section 49 of the Act in this regard. Specifically with reference to Section 49(i)(a) of the Act, the High Court held that the complaint had not been filed by the Board as defined under Section 2(h) of the Act. Though the High Court felt that on this ground alone the petition was bound to succeed, yet it considered the other aspects and set aside the order of conviction and sentence as imposed.
8. In support of the appeal, learned counsel for the appellant submitted that prior to amendment the expression used was "previous sanction of the Board" but after the amendment it was "authorized in this behalf by it". It is pointed out that in exercise of powers under Section 11-A of the Act, the Board delegated to the Chairman the power of sanctioning prosecution vide Resolution dated 27.3.1984. In exercise of this power the Chairman 4 sanctioned as well as authorized complainant to file the complaint in the present case by his order dated 18.8.1989.
9. It is submitted that while considering the validity and/or effectiveness of the order, the High Court proceeded on erroneous presumption that Section 49 was applicable at the time when the present complaint was filed. According to the appellant, though the complaint was filed on 17.10.1989, prior to that Section 49 was amended by Act 53 of 1988 w.e.f. 29.9.1988. So far as the State of Gujarat is concerned, the amendment became effective only when the Gujarat Legislative Assembly passed a resolution adopting the amendment on 29.9.1999 which was notified on 28.10.1999. It is submitted that the Act is an enactment pursuant to Article 252 of the Constitution of India, 1950 (in short the `Constitution'). The Act is relatable to inter-alia Entry 17 of List II, namely, the water that is to say "water supplies, irrigation and canals, drainage and embankments....". In any case, the Parliament as well as all State Legislatures have all along acted on the basis that Act has been enacted pursuant to powers under Article 252 of the Constitution. Further in Preamble to the Act there is categorical assertion by the Parliament to the effect that "And whereas Parliament has no power to make laws for the States with respect to any of 5 the maters aforesaid except as provided in Articles 249 and 250 of the Constitution". It is, therefore, submitted that it was never challenged by the respondents 1 and 2. They cannot be permitted to urge that the Act was not passed pursuant to Article 250 of the Constitution. The passing of the resolution by the State Legislature of two or more States is a condition precedent for investing the Parliament with the power to make a law on that topic or matter and then it shall be lawful for the Parliament to make a law for regulating that matter accordingly. The law so made or enacted by the Parliament under Article 252(1) of the Constitution will apply only to those States whose legislatures have passed resolutions under that provision and also to such States which have afterwards adopted the same by resolution passed by the legislatures of such States in that behalf. Therefore, at the relevant point of time the unamended Section 49 was applicable and delegation to the chairman of the power to sanction prosecution by the Board was valid and effective. Even otherwise resolution dated 27.3.1984 clearly establishes that the Board delegated to the Chairman the power of sanctioning prosecution. Therefore, this was valid and effective even for the purpose of amended Section 49(1)(a) of the Act. Section 49 is in two parts namely (i) a complaint made by the Board and (ii) by any officer authorized in this behalf by it. The delegation of the power of sanctioning 6 prosecution in favour of the Chairman can always be read as the power of authorizing prosecution after Section 49 was amended.
10. The Inspection Report clearly establishes the name of accused No.3 as the person in charge of the unit. In the statement recorded under Section 313 of the Code of Criminal Procedure, 1973 (in short the `Code') A-3 has clearly admitted that the same is true. Reference is also made to Section 21 which deals with power to take samples of effluents and procedure to be followed in connection therewith.
11. In response, learned counsel for the respondents 1 and 2 submitted that the High Court had clearly recorded that the conditions required compliance with the water standards if water over-flowed from the solar evaporation pans and the sample taken was from the drain that ran from the factory to the evaporation pans. On the aforesaid basis, the High Court came to hold that there had been no violation of the terms of the Water Act. The submission of the prosecution that the water flows from the factory to the pans in a kachcha drain thereby there was violation of conditions is not based on materials in the sense that it was not the basis for the complaint and was also not the basis of judgments of courts below. 7
12. Learned counsel for the respondent submitted that the question is whether the amended provisions apply and the authorization has to be by the State Board. That question need not be gone into as the prosecution was required to prove that the solar evaporation pan maintained by the company had over flown and the over flown effluent did not conform to the tolerance limits prescribed. The documents on record clearly establish that the company was discharging its effluent into the drain leading to the solar evaporation pan i.e. into the solar evaporation pan. There was nothing to show that any sample of any over flown effluent has been taken. It is pointed out that the sample taken on 22.6.1989 is not of over flown effluent, but of effluent which was on the way to the solar evaporation pan for further treatment. It is also submitted that Section 21(5) obliges the Board to forward the sample for the purpose of analysis. In the instant case the sample was taken on 22.6.1989 and was received on 28.6.1989. The delay has not been explained.
13. There is no substantial difference in the language of the amended Section 49. The High Court proceeded on the basis that the complaint was illegal since the complaint filed was not duly authorized. Though the High 8 Court proceeded on the basis of amended Section 49, the amended as well as un-amended provisions require the State Board to file a complaint or to authorize any of its officers to file the complaint. The authorization has to be by the State Board. According to the Board under Section 11-A of the Act it had delegated to the Chairman the power to authorize an officer to file a complaint. Resolution dated 27.3.1984 refers to the delegation of power to sanctioning prosecution. The High Court has held that the power to sanction a complaint is distinct from the power to authorize the complaint. This view is clearly unsustainable for the reason that if the provisions are construed in the context that as a check over the complaint filed, then the grant of sanction to file a complaint would be in law an authorization to file the complaint. The stand of the appellant that the difference between sanction and authorization in the context of provisions of the Act and incontra- distinction to the provisions of IPC and the Code is more semantic than real. The stand is well founded. The appeal can be disposed of on the ground that factually there is nothing to show that the sample collected was from the over-flown effluent. The evidence on record clearly shows that the effluent was on the way to the solar evaporation pans for further treatment. The said effluent would never meet the parameters prescribed as it is yet to be treated. Thus, the alleged breach of condition No.4 has not been proved. 9 On that ground alone the appeal deserves to be dismissed. In view of this conclusion it is not necessary to go into the other aspects as to what is the effect of the resolution of the State notified on 28.10.1999 i.e. after the date of amendment of the statute of Section 49 on 29.9.1999. The authorization by the Chairman was on 18.8.1989. In view of the factual aspects highlighted, the appeal deserves to be dismissed which we direct.
...................................J.
(Dr. ARIJIT PASAYAT) ...................................J.
(P. SATHASIVAM) ...................................J.
(AFTAB ALAM) New Delhi, December 4, 2008 10


{% extends 'htc-layout.html' %} {% block pageTitle %} Guide to regulations - Information for innovators {% endblock %} {% block beforeContent %} {{ breadcrumb({ items: [ { href: "/htc", text: "Home" } ], href: "/htc/innovators", text: "Information for innovators" }) }} {% endblock %} {% block content %}
There are no formal regulatory approval bodies or processes for models of care or other types of innovation. However, organisations looking to adopt your innovation may require it to comply with any applicable national Quality Standards set by NICE.
{% from 'pagination/macro.njk' import pagination %} {{ pagination({ "previousUrl": "/htc/innovators/regulations/surgical", "previousPage": "Surgical procedures and techniques" }) }}


{% extends "catalog/base_landing.html" %}
{% load static from staticfiles %}
{% block title %}Makeystreet| Engage with makers around you. {% endblock %}
{% block extra_js %}
{% endblock %}
{% block extra_css %}
{% endblock %}
{% block templates %}
{% include "catalog/t/t_landing_page.html" %}
{% endblock %}
{% block backbone %}
{% include "catalog/bb/bb_landing_page.html" %}
{% endblock %}
{% block no_container %}
Firefly unicycle is an open source personal transportation device. We love building products. It is an attempt to build a kickass hardware community in India. Would you not like to meet other kickass hardware developers just like you? Why you will love makeystreet?
Firefly unicycle - Open Source hardware project.
We want to make large scale open source hardware projects happen.


--- layout: post title: New malware attack hits facebook through chat! date: 2011-03-19 15:14:54.000000000 +01:00 categories: - linux tags: [] status: publish type: post published: true meta: _edit_last: '1' author: ---
I just got pings from three of my friends over facebook chat, all of them containing the same message
Hey, check out this girl, lol, she must be out of her mind for making that video!: bit.ly/eNYMXb
Well, so lets see where does the link take us..
anshup@listsettle-lm: ~$ curl -I bit.ly/eNYMXb
HTTP/1.1 301 Moved
Server: nginx
Date: Sat, 19 Mar 2011 09:35:54 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: _bit=4d8478fa-003c1-04438-d8ac8fa8;domain=.bit.ly;expires=Thu Sep 15 05:35:54 2011;path=/; HttpOnly
Cache-control: private; max-age=90
Location: http://www.torsing.info/
MIME-Version: 1.0
Content-Length: 116
As expected, the first bitly link is a proper redirect to some site. Now lets see what the second link has.
anshup@listsettle-lm: ~$ curl -I http://www.torsing.info/
HTTP/1.1 302 Found
Date: Sat, 19 Mar 2011 09:36:04 GMT
Server: Apache
Location: http://www.torsing.info//dashboard.php
Connection: close
Content-Type: text/html
Hmm, another redirect to same site, not bad.
anshup@listsettle-lm: ~$ curl -I http://www.torsing.info//dashboard.php
HTTP/1.1 200 OK
Date: Sat, 19 Mar 2011 09:36:11 GMT
Server: Apache
Connection: close
Content-Type: text/htmlanshup@listsettle-lm: ~$ curl http://www.torsing.info//dashboard.php
<script type='text/javascript'>top.location.href = 'https://www.facebook.com/login.php?api_key=134003950005663&cancel_url=http%3A%2F%2Fwww.torsing.info%2Fmain.php&display=page&fbconnect=1&next=http%3A%2F%2Fwww.torsing.info%2Fdashboard.php&return_session=1&session_version=3&v=1.0&req_perms=xmpp_login';</script>
Now here is the bad part!
As you see in the last output, its merely a trick to directly access your facebook credentials as if you approved it (thats my assumption, am not sure what it does and am not going to find that out right now.
What I am surprised at is that facebook uses a non salted/non nounced url for such requests.. :!
Definitely you know better facebook :)
lets see how fast it spreads and what all comes out of it!
Lets see a lil about the domain.
anshup@listsettle-lm: ~$ whois torsing.info
Domain ID:D36666838-LRMS
Domain Name:TORSING.INFO
Created On:05-Feb-2011 19:58:43 UTC
Last Updated On:06-Feb-2011 10:32:05 UTC
Expiration Date:05-Feb-2012 19:58:43 UTC
Sponsoring Registrar:GoDaddy.com Inc. (R171-LRMS)
Status:CLIENT DELETE PROHIBITED
Status:CLIENT RENEW PROHIBITED
Status:CLIENT TRANSFER PROHIBITED
Status:CLIENT UPDATE PROHIBITED
Status:TRANSFER PROHIBITED
Registrant ID:CR74380736
Registrant Name:Matej Kalanj
Registrant Organization:
Registrant Street1:Marohniceva 18
Registrant Street2:
Registrant Street3:
Registrant City:Rijeka
Registrant State/Province:Primorsko goranska
Registrant Postal Code:51000
Registrant Country:HR
Registrant Phone:+385.955533376
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant<EMAIL_ADDRESS>Admin ID:CR74380738
Admin Name:Matej Kalanj
Admin Organization:
Admin Street1:Marohniceva 18
Admin Street2:
Admin Street3:
Admin City:Rijeka
Admin State/Province:Primorsko goranska
Admin Postal Code:51000
Admin Country:HR
Admin Phone:+385.955533376
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin<EMAIL_ADDRESS>Billing ID:CR74380739
Billing Name:Matej Kalanj
Billing Organization:
Billing Street1:Marohniceva 18
Billing Street2:
Billing Street3:
Billing City:Rijeka
Billing State/Province:Primorsko goranska
Billing Postal Code:51000
Billing Country:HR
Billing Phone:+385.955533376
Billing Phone Ext.:
Billing FAX:
Billing FAX Ext.:
Billing<EMAIL_ADDRESS>Tech ID:CR74380737
Tech Name:Matej Kalanj
Tech Organization:
Tech Street1:Marohniceva 18
Tech Street2:
Tech Street3:
Tech City:Rijeka
Tech State/Province:Primorsko goranska
Tech Postal Code:51000
Tech Country:HR
Tech Phone:+385.955533376
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech<EMAIL_ADDRESS>Name Server:MDNS1.NMSERVERS.COM
Name Server:MDNS2.NMSERVERS.COM
Hmmm, so a site registered in croatia. Interesting.


Recover Password
Enter your username and a confirmation message will be sent to recover your password.
Username
Send Request


|
PLAY THE GAME
|
ABOUT PYONGYANG RACER
|
ABOUT KORYO TOURS
|
TRAVEL TO THE DPRK (NORTH KOREA) >>
|
VISIT GITHUB PROJECT PAGE
To play Pyongyang Racer, you need to download the Pyongyang Racer application from
https://github.com/aidswidjaja/PyongyangRacer
.


I am a body
Everything appears
in the browsers
This is a paragraph and it is different from the return or enter key
This is H1
This is H2
This is H3
This is H4
This is H5
This is H6


It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using 'Content here, content here', making it look like readable English.
It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout.
It is a long established fact that a reader will be distracted by the readable content of a page when looking at. layout.
It is a long established fact that a reader will be distracted by the readable content of a page when looking at. layout.
It is a long established fact that a reader will be distracted by the readable content of a page when looking at. layout.
It is a long established fact that a reader will be distracted by the readable content of a page when looking at. layout.
It is a long established fact that a reader will be distracted by the readable content of a page when looking at. layout.
It is a long established fact that a reader will be distracted by the readable content of a page when looking at. layout.
Real Visitor
Total Download
Real Visitor
Favorite Peoples
It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout..
Read MoreIt is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout..
Read MoreIt is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout..
Read MoreNeed any help jusct send a message via our email address
+00 901 980680
<EMAIL_ADDRESS>29 road, Sec-08, Uttara-1204
Dhaka, Bangladesh


Created by @HumoBinario
/* /js/examples/base-class.js */
class Human {
constructor(name){
this.name = name;
}
identify() {
return `Hello, I'm ${this.name}`;
}
}
const d00d = new Human('d00d');
console.log(d00d.identify());
console.log(d00d instanceof Human);
Classes aren't something radically new in JS.
ES6 Classes are just a more concise way to declare constructor functions
/* /js/examples/base-class.js */
> console.log(typeof(Human));
function
Similarly to functions, there are two kinds of class definitions:
class declarations and class expressions
Class expressions can be anonymous:
/* /js/examples/class-expressions1.js */
const MyHuman = class {
constructor(name){
this.name = name;
}
identify() {
return `Hello, I'm ${this.name}`;
}
};
const myHumanInstance = new MyHuman('Molly Millions');
console.log(myHumanInstance.identify());
Class expressions can have inner names only visible to them:
/* /js/examples/class-expressions2.js */
const MyHuman = class Human {
constructor(name){
this.name = name;
}
identify() {
return `Hello, I'm ${this.name} and I'm a ${Human.name}`;
}
};
const myHumanInstance = new MyHuman('Jonny Mnemonic');
console.log(myHumanInstance.identify());
console.log(MyHuman.name);
console.log(Human.name); //ReferenceError
/* /js/examples/class-declaration.js */
class Human {
constructor(name){
this.name = name;
}
static sayRace() {
return Human.name;
}
identify() {
return `Hello, I'm ${this.name}`;
}
}
This is a special method, as it defines the function that represents the Class.
There can only be one constructor per Class definition
/* /js/examples/class-declaration.js */
constructor(name){
this.name = name;
}
...
console.log(Human === Human.prototype.constructor);
Also called static properties or class properties, are properties of the Class itself and not its instances.
Created by prefixing a method with static.
/* /js/examples/class-declaration.js */
static sayRace() {
return Human.name;
}
...
console.log(Human.sayRace());
console.log(typeof(Human.sayRace));
They are the methods defined in the Class declaration body; they are inherited by instances of the class.
Called prototype methods because they will be properties of the Class prototype (more on this later).
/* /js/examples/class-declaration.js */
identify() {
return `Hello, I'm ${this.name}`;
}
...
console.log(typeof(Human.prototype.identify));
console.log(Human.prototype.identify()); //Don't do this. Just an example!
console.log(bobby.identify());
Their syntax is just like getters & setters from ES5 Object Literals
/* /js/examples/getter-setter.js */
constructor(name){
this._name = name;
}
get name() {
return this._name;
}
set name(name) {
this._name = name;
}
...
const cayce = new Human('Cayce Pollard');
console.log(cayce.name);
console.log(cayce._name);
cayce.name = "Pollard Cayce";
console.log(cayce.name);
console.log(cayce._name);
Use expressions to define prototype method names by inserting them into square brackets
/* /js/examples/computed-properties.js */
class Human {
constructor(name){
this._name = name;
}
['id'+'entify']() {
return `Hello, I'm ${this._name}`;
}
}
const rei = new Human('Rei Toei');
console.log(rei.identify());
ES6 Classes are NOT hoisted. You cannot use them before their evaluation
A Class definition is actually a function, but you HAVE to call it with the new operator
There are no separators between members of a Class definition.
; are ignored and , result in SyntaxError
The extend clause lets you create a subclass of an existing constructor.
The base-class may or may have not been defined via Class
The extend clause expects an Expression as its operand (more on this later on)
You can only extend from one Base-class at a time
/* /js/examples/sub-classing1.js */
class Cyborg extends Human {
constructor(name){
super(name);
}
identify() {
return `Hello, I'm ${this._name} and I'm a ${Cyborg.name}`;
}
}
const t1000 = new Cyborg("Arnold");
console.log(t1000.identify());
console.log(t1000 instanceof Cyborg);
console.log(t1000 instanceof Human);
The base-class may or may have not been defined via Class
What does that even mean?
/* /js/examples/sub-classing2.js */
function Human(name) {
this._name = name;
this.identify = function identify() {
return `Hello, I'm ${this._name} and I'm a ${Human.name}`;
};
};
class Cyborg extends Human {
...
console.log(t1000 instanceof Cyborg);
console.log(t1000 instanceof Human);
In a derived class, you MUST call super() before being able to use this
The reason is that in ES6 classes, base classes are the ones that actually create the object instance.
/* /js/examples/super-calls.js */
class Cyborg extends Human {
constructor(name, skill){
this._skill = skill; //ReferenceError
super(name);
this._skill = skill; //OK
}
...
const molly = new Cyborg('Molly Millions', 'Hypervision');
console.log(molly._skill);
Classes ALWAYS have a constructor, even when you don't explicitly define it.
Again, the reason for this is that the constructor of a base class MUST be called to be able to obtain the object instance
constructor() {} //implicit constructor for base-classes
constructor(...args){ //implicit constructor for derived-classes
super(...args);
}
In ES6 we can (finally) extend built-in constructors as if they were any other base class
NOT available via transpilers (Babel.js). Engines need to implement this directly.
/* /js/examples/builtin-constructors.js */
class CustomError extends Error {
};
throw new CustomError("Ups! we're fucked!"); //we now have a StackTrace!
The power of extend taking in an expression as operand instead of just an identifier
class Foo extends Bar {
//Foo and Bar are both Classes
}
class Foo extends chain() {
//chain() is a function that returns a Class/Constructor-function
}
class Foo extends alpha {
//where alpha is a variable whose value is a Class/Constructor-function
}
How to take advantage of that to achieve multiple inheritance?
/* /js/examples/multiple-inheritance.js */
//Cyborg extends Hybryd, Human
class Human{
constructor(name) {
this._name = name;
}
}
const Hybrid = (superClass) => class extends superClass {
isHybrid() {
return 'I´m a hybrid';
}
};
class Cyborg extends Hybrid(Human) {
identify () {
return `Hello, I´m ${this._name}, and ${this.isHybrid()}`;
}
}
/* /js/examples/multiple-inheritance.js */
const jonny = new Cyborg("Jonny");
console.log(jonny.isHybrid());
console.log(jonny.identify());
console.log(jonny instanceof Human);
console.log(jonny instanceof Cyborg);
/* /js/examples/multiple-inheritance.js */
console.log(jonny instanceof Hybrid); //TypeError
Hybrid.prototype = Human.prototype;
console.log(jonny instanceof Hybrid); //Now we're good
JavaScript's flavor of inheritance is called Prototypal Inheritance because it relies on prototype properties to inherit methods and data.
/* /js/examples/prototype-base.js */
const molly = new Human("Molly");
console.log(Human instanceof Function);
console.log(molly instanceof Human);
console.log(Human.prototype instanceof Object);
console.log(Human === Human.prototype.constructor);
console.log(Object.getPrototypeOf(Human) === Function.prototype);
console.log(Object.getPrototypeOf(Human.prototype) === Object.prototype);
console.log(Object.getPrototypeOf(molly) === Human.prototype);
/* /js/examples/prototype-derived.js */
const molly = new Cyborg("Molly", "Hypervision");
console.log(Human instanceof Function);
console.log(molly instanceof Human);
console.log(molly instanceof Cyborg);
console.log(Human.prototype instanceof Object);
console.log(Cyborg.prototype instanceof Human);
console.log(Human === Human.prototype.constructor);
console.log(Cyborg === Cyborg.prototype.constructor);
console.log(Object.getPrototypeOf(Cyborg) === Human);
console.log(Object.getPrototypeOf(Human) === Function.prototype);
console.log(Object.getPrototypeOf(molly) === Cyborg.prototype);
console.log(Object.getPrototypeOf(Cyborg.prototype) === Human.prototype);
console.log(Object.getPrototypeOf(Human.prototype) === Object.prototype);
/* /js/examples/private-via-constructor.js */
class Human{
constructor(name) {
Object.assign(this, {
getName () {
return name;
},
setName (_name){
name = _name;
}
});
}
}
/* /js/examples/private-via-constructor.js */
const billy = new Human("Billy");
console.log(billy.name);
console.log(billy.getName());
billy.setName("Juancho");
console.log(billy.getName());
PROS
CONS
/* /js/examples/private-via-naming.js */
class Human{
constructor(name) {
this._name = name;
}
get name () {
return this._name;
}
set name (name) {
this._name = name;
}
}
/* /js/examples/private-via-naming.js */
const barack = new Human("Barack");
console.log(barack._name);
console.log(barack.name);
barack.name = "Obama";
console.log(barack.name);
console.log(barack._name);
barack._name = "Hussein";
console.log(barack.name);
PROS
CONS
/* /js/examples/private-via-weakmaps.js */
const _name = new WeakMap();
class Human{
constructor(name) {
_name.set(this, name);
}
get name () {
return _name.get(this);
}
set name (name) {
_name.set(this, name);
}
}
/* /js/examples/private-via-weakmaps.js */
const albert = new Human("Albert Hoffman");
console.log(albert.name);
albert.name = "Hoffman Albert";
console.log(albert.name);
console.log(albert._name);
PROS
CONS
/* /js/examples/private-via-symbol.js */
const _name = Symbol('Name');
class Human{
constructor(name) {
this[_name] = name;
}
get name () {
return this[_name];
}
set name (name) {
this[_name] = name;
}
}
/* /js/examples/private-via-symbol.js */
const albert = new Human("Albert Hoffman");
console.log(albert.name);
albert.name = "Hoffman Albert";
console.log(albert.name);
console.log(albert._name);
PROS
CONS


Table of Contents
Introduction
Review Framework Elements
Review Source Structure
Define DDE_RUNTIME vs. Project Locations
Demo Execution Flow
Driver Commands
High-Level Test Records
Component Test Records
Generic Test Records
Define Custom vs. Core Actions
Core Actions
Custom Actions
Add Core Actions
Adding Driver Commands
Adding Component Functions
Adding A New Component
Understanding Namespaces (Scope)
Add Custom Extensions
Custom Extension Namespace
Custom Record Types
Custom Driver Commands
Custom Test Commands
Review Documentation Standards
API Doc Format
XML (Keywords) Doc Format
Demo Publishing Tools
SQA Library Publishing
Action Map Publishing
DDEngineReference Publishing
XML2DB Publishing
Debug XML Publishing


In continuous search for new challenges. I am passionate about technology and overcome the obstacles that arise on a daily basis. I like teamwork, being able to share knowledge and experiences among my colleagues. My interest is to belong to a company with a good working environment with great challenges, where I can contribute my knowledge and acquired experiences
Duties Dev Service Desk :
- Development of RIA applications using NodeJS and MongoDB.
- Data Migration with MongpDB Aggregation
- Building new features required Web & UI/UX Design with Vuejs CLI and Vuetify Framework
- Testing code with Xunit in C#, and Mocha and Chai in Nodejs
- Code Reviews
- Manager: Marius Smit
- Email<EMAIL_ADDRESS>- Telephone: +27 73 438 3675
- Duties Dev Service Desk :
- Investigations
- Fixing bugs
- Building new features required
- Develop Marketing Campaigns
- Code Reviews
- Manager: Arneau Van Der Horst
-Email<EMAIL_ADDRESS>- Telephone: +27 67 612 4965, +27 74 077 9027
- Managing FOH
- Dealing with Customers and bookings
- Counting stock
- HR
- Close down
Building website or different projects in development, design or anything else.
View Project


---
layout: post
status: publish
published: true
title: 'New Series: Daily App Find!'
author: Arthur Rosa
author_login: arthurlockman
author_email<EMAIL_ADDRESS>author_url: https://b.rthr.me
wordpress_id: 206
wordpress_url: http://b.rthr.me/?p=206
date: '2010-08-26 18:53:29 -0400'
date_gmt: '2010-08-26 18:53:29 -0400'
---
I know that for the past few weeks my blog has been suspiciously devoid of content. I therefore am starting a new series to get my blog back to where it should be. The new series will be called the Daily App Find! I will showcase an app a day (hopefully every day) that I found and thought I should share with everyone else. These apps will be for pretty much all platforms; be it Android, iOS, Mac, or Windows. Starting tomorrow I will showcase some neat apps that everyone should go try out. Hold on too your hats, this one's gonna be good.
All for Now!


--- layout: post title: Weekend at home-ish date: 2015-01-10 21:39:45.000000000 -08:00 type: post background: '/img/posts/bg.jpg' parent_id: '0' published: true password: '' status: publish categories: - travel tags: [] meta: _edit_last: '2' _thumbnail_id: '1000' permalink: "/travel/weekend-at-home-ish/" ---
Met up with a large group for happy hour last night at my friend, Christian's bar, Molokos on Mississippi. Had lovely conversations, some stilted, but for the most part a wonderful time.
Tonight I have my first official houseguest, Melinda has proposed coming out to visit and I am so excited! It has involved putting out the awning, cleaning up the whole place, and dumping my grey water in the pasture. Now that I'm showering in here, all that is left is doing laundry and I'm completely independent. Very exciting!
More chores though so I have to go.


MISSION: IMPOSSIBLE A film review by James Berardinelli Copyright 1996 James Berardinelli
RATING (0 TO 10): 6.0 Alternative Scale: **1/2 out of ****
United States, 1996 U.S. Release Date: 5/22/96 (wide) Running Length: 1:50 MPAA Classification: PG-13 (Violence, mature themes) Theatrical Aspect Ratio: 2.35:1
Cast: Tom Cruise, Emmanuelle Beart, Jon Voight, Vanessa Redgrave, Henry Czerny, Ving Rhames, Jean Reno, Kristin Scott-Thomas, Emilio Estevez Director: Brian DePalma Producers: Tom Cruise and Paula Wagner Screenplay: David Koepp and Robert Towne Cinematography: Stephen H. Burum Music: Danny Elfman; "Mission Impossible" theme by Lalo Schifrin U.S. Distributor: Paramount Pictures
The first star vehicle of the summer of 1996 is also the first major disappointment of the season. MISSION: IMPOSSIBLE, the big screen resurrection of the popular late-'60s/early-'70s series, fails to generate much in the way of excitement or intrigue. This globetrotting adventure looks like an opportunity for Tom Cruise to play James Bond - - a role he is totally unsuited for. The writing for last year's 007 return, GOLDENEYE, isn't a lot better than that for MISSION: IMPOSSIBLE, but, as an action hero, Pierce Brosnan is considerably more debonair and charismatic than Cruise.
There's no Bond in MISSION: IMPOSSIBLE. Instead, the lead character is Ethan Hunt, the point man for Jim Phelps' IMF (Impossible Missions Force). Phelps (played by Jon Voight, not Peter Graves) receives assignment messages from his boss, Kittridge (Henry Czerny), via video transmissions rather than old-fashioned tapes. His group's latest job is to prevent something called a "NOC list" from falling into the hands of an international arms dealer (Vanessa Redgrave). If placed on the open market, the NOC list would put every United States deep cover agent in danger of exposure. However, when they embark on this mission, the IMF runs straight into an ambush where everyone is killed except Hunt and Phelps' wife, Claire (Emmanuelle Beart). Because he survives the carefully-orchestrated massacre, Hunt is suspected of turning traitor.
Fans of the TV series expecting a faithful translation may be disappointed. Except for a few nods to its small-screen predecessor, this MISSION: IMPOSSIBLE is a vastly different, autonomous entity. Nine years ago, director Brian DePalma used a similar approach for a superior version of THE UNTOUCHABLES, but lightning hasn't struck twice. Teetering on an uncertain edge between action flick and thriller, MISSION: IMPOSSIBLE doesn't succeed well as either. There are some high-energy moments, but none offers more than a moment's edge-of-the- seat excitement. Too much of what happens in MISSION: IMPOSSIBLE comes across as fait accompli.
The predictable plot generates little interest. It's pathetically easy to guess the mole's identity despite the screenwriters' attempts to obscure the issue. The overall storyline contains a legion of gaping holes -- the more you think about it, the less sense it makes. Weak character identification allows TWISTER to seem like a masterpiece by comparison. In fact, taken as a whole, TWISTER is a significantly more involving spectacle.
Megastar Tom Cruise (who also co-produced the movie) struts and smirks his way through his role in a way that makes Hunt easy to dislike. It's not a particularly good performance, either. Cruise's supporting players form an interesting group, although not necessarily the kind of names one might expect in a big-budget action film. They include a highly-respected French actress, Emmanuelle Beart (MANON OF THE SPRING, NELLY & MONSIEUR ARNAUD); a veteran American actor, Jon Voight (MIDNIGHT COWBOY); FOUR WEDDINGS AND A FUNERAL's Kristin Scott- Thomas; and the internationally-renowned Vanessa Redgrave.
What does it say about the current status of American motion pictures that three of Paramount Pictures' big 1996 releases, MISSION: IMPOSSIBLE, A VERY BRADY SEQUEL, and STAR TREK: FIRST CONTACT, are TV series regurgitations? If this movie is any indication, originality isn't high on the studio's list of priorities. TWISTER has taken a critical drubbing because of its style-over-substance approach to entertainment, but MISSION: IMPOSSIBLE is a worse offender. The substance here isn't appreciably stronger, while the style is less eye- popping. Due primarily to several deftly-crafted action sequences, MISSION: IMPOSSIBLE boasts a few memorable moments. Keeping in mind what's expected from would-be summer blockbusters, this movie isn't a disaster, but, all things considered, there's little reason to make it a high priority for theatrical viewing.
- James Berardinelli e-mail<EMAIL_ADDRESS>web: http://www.cybernex.net/~berardin
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Before Change
self._labels_shape = (1,) // Shape of labels tensor excluding leading batch dimension
self._labels_range = (0, self.num_classes-1) // Possible labels" values inclusive
if self.__dtype == "float16" and self.__have_float16_lrn:
print("[WARNING] The data type is "float16" and I assume MXNET provides a float16 kernel for LRN layer. "
"If this model uses LRN and your MXNET version is outdated, you will get error. In this case, to "
"disable LRN layers in float16 regime, define the following variable "DLBS_MXNET_NO_FLOAT16_LRN" "
"(the value of this variable does not matter) i.e.: "
"-Pruntime.launcher="\"DLBS_MXNET_NO_FLOAT16_LRN=1 \""")
if self.__dtype == "float16" and not self.__have_float16_lrn:
print("[WARNING] The data type is "float16" and you disable LRN layers. All calls to Model.maybe_lrn "
" will do nothing. If your MXNET version is up to date and provides LRN float16 kernel make sure "
"DLBS_MXNET_NO_FLOAT16_LRN environment variable is not defined. All this is relevant only if this "
"model uses LRN operators.")
@staticmethod
def conv_shape(num_channels, spatial_dims, layout="NCHW"):
Return shape of a feature map tensor for convolutional models.
After Change
self._labels_shape = (1,) // Shape of labels tensor excluding leading batch dimension
self._labels_range = (0, self.num_classes-1) // Possible labels" values inclusive
if self.__dtype == "float16" and self.__have_float16_lrn:
logging.warning(
"The data type is "float16" and I assume MXNET provides a float16 kernel for LRN layer. If this model "
"uses LRN and your MXNET version is outdated, you will get error. In this case, to disable LRN layers "
"in float16 regime, define the following variable "DLBS_MXNET_NO_FLOAT16_LRN" (the value of this "
"variable does not matter) i.e.: -Pruntime.launcher="\"DLBS_MXNET_NO_FLOAT16_LRN=1 \""")
if self.__dtype == "float16" and not self.__have_float16_lrn:
logging.warning(
"The data type is "float16" and you disable LRN layers. All calls to Model.maybe_lrn will do nothing. "
"If your MXNET version is up to date and provides LRN float16 kernel make sure "


The Maros and Meszaros test set (mirror) is a collection of convex quadratic programming examples from a variety of sources. The examples are available in QPS format, which is a subset of the SIF format used by CUTEr. Thus, the Maros and Meszaros set provide a further collection of interesting examples for those who have CUTE interfaces to their optimization packages. See
Istvan Maros and Csaba Meszaros
"A repository of convex quadratic programming problems",
Optimization Methods and Software (OMS) Volumes 11&12 (December, 1999), 671-681,
Special Issue on Interior Point Methods (CD supplement with software)
Guest Editors: Florian Potra, Cornelis Roos and Tamas Terlaky
| name | files available | CUTEr classification |
|---|---|---|
| AUG2D | ascii file, gzipped file | QLR2-AN-20200-10000 |
| AUG2DC | ascii file, gzipped file | QLR2-AN-20200-10000 |
| AUG2DCQP | ascii file, gzipped file | QLR2-AN-20200-10000 |
| AUG2DQP | ascii file, gzipped file | QLR2-AN-20200-10000 |
| AUG3D | ascii file, gzipped file | QLR2-AN-3873-1000 |
| AUG3DC | ascii file, gzipped file | QLR2-AN-3873-1000 |
| AUG3DCQP | ascii file, gzipped file | QLR2-AN-3873-1000 |
| AUG3DQP | ascii file, gzipped file | QLR2-AN-3873-1000 |
| BOYD1 | ascii file, gzipped file | QLR2-AN-93261-18 |
| BOYD2 | ascii file, gzipped file | QLR2-AN-93263-0 |
| CONT-050 | ascii file, gzipped file | QLR2-AN-2597-2401 |
| CONT-100 | ascii file, gzipped file | QLR2-AN-10197-9801 |
| CONT-101 | ascii file, gzipped file | QLR2-AN-10197-10098 |
| CONT-200 | ascii file, gzipped file | QLR2-AN-40397-39601 |
| CONT-201 | ascii file, gzipped file | QLR2-AN-40397-40198 |
| CONT-300 | ascii file, gzipped file | QLR2-AN-90597-90298 |
| CVXQP1_L | ascii file, gzipped file | QLR2-AN-10000-5000 |
| CVXQP1_M | ascii file, gzipped file | QLR2-AN-1000-500 |
| CVXQP1_S | ascii file, gzipped file | QLR2-AN-100-50 |
| CVXQP2_L | ascii file, gzipped file | QLR2-AN-10000-2500 |
| CVXQP2_M | ascii file, gzipped file | QLR2-AN-1000-250 |
| CVXQP2_S | ascii file, gzipped file | QLR2-AN-100-25 |
| CVXQP3_L | ascii file, gzipped file | QLR2-AN-10000-7500 |
| CVXQP3_M | ascii file, gzipped file | QLR2-AN-1000-750 |
| CVXQP3_S | ascii file, gzipped file | QLR2-AN-100-75 |
| DPKLO1 | ascii file, gzipped file | QLR2-AN-133-77 |
| DTOC3 | ascii file, gzipped file | QLR2-AN-14999-9998 |
| DUAL1 | ascii file, gzipped file | QLR2-AN-85-1 |
| DUAL2 | ascii file, gzipped file | QLR2-AN-96-1 |
| DUAL3 | ascii file, gzipped file | QLR2-AN-111-1 |
| DUAL4 | ascii file, gzipped file | QLR2-AN-75-1 |
| DUALC1 | ascii file, gzipped file | QLR2-AN-9-215 |
| DUALC2 | ascii file, gzipped file | QLR2-AN-7-229 |
| DUALC5 | ascii file, gzipped file | QLR2-AN-8-278 |
| DUALC8 | ascii file, gzipped file | QLR2-AN-8-503 |
| EXDATA | ascii file, gzipped file | QLR2-AN-3000-3001 |
| GENHS28 | ascii file, gzipped file | QLR2-AN-10-8 |
| GOULDQP2 | ascii file, gzipped file | QLR2-AN-699-349 |
| GOULDQP3 | ascii file, gzipped file | QLR2-AN-699-349 |
| HS118 | ascii file, gzipped file | QLR2-AN-15-17 |
| HS21 | ascii file, gzipped file | QLR2-AN-2-1 |
| HS268 | ascii file, gzipped file | QLR2-AN-5-5 |
| HS35 | ascii file, gzipped file | QLR2-AN-3-1 |
| HS35MOD | ascii file, gzipped file | QLR2-AN-3-1 |
| HS51 | ascii file, gzipped file | QLR2-AN-5-3 |
| HS52 | ascii file, gzipped file | QLR2-AN-5-3 |
| HS53 | ascii file, gzipped file | QLR2-AN-5-3 |
| HS76 | ascii file, gzipped file | QLR2-AN-4-3 |
| HUES-MOD | ascii file, gzipped file | QLR2-AN-10000-2 |
| HUESTIS | ascii file, gzipped file | QLR2-AN-10000-2 |
| KSIP | ascii file, gzipped file | QLR2-AN-20-1001 |
| LASER | ascii file, gzipped file | QLR2-AN-1002-1000 |
| LISWET1 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET10 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET11 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET12 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET2 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET3 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET4 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET5 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET6 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET7 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET8 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LISWET9 | ascii file, gzipped file | QLR2-AN-10002-10000 |
| LOTSCHD | ascii file, gzipped file | QLR2-AN-12-7 |
| MOSARQP1 | ascii file, gzipped file | QLR2-AN-2500-700 |
| MOSARQP2 | ascii file, gzipped file | QLR2-AN-900-600 |
| POWELL20 | ascii file, gzipped file | QLR2-AN-10000-10000 |
| PRIMAL1 | ascii file, gzipped file | QLR2-AN-325-85 |
| PRIMAL2 | ascii file, gzipped file | QLR2-AN-649-96 |
| PRIMAL3 | ascii file, gzipped file | QLR2-AN-745-111 |
| PRIMAL4 | ascii file, gzipped file | QLR2-AN-1489-75 |
| PRIMALC1 | ascii file, gzipped file | QLR2-AN-230-9 |
| PRIMALC2 | ascii file, gzipped file | QLR2-AN-231-7 |
| PRIMALC5 | ascii file, gzipped file | QLR2-AN-287-8 |
| PRIMALC8 | ascii file, gzipped file | QLR2-AN-520-8 |
| Q25FV47 | ascii file, gzipped file | QLR2-AN-1571-820 |
| QADLITTL | ascii file, gzipped file | QLR2-AN-97-56 |
| QAFIRO | ascii file, gzipped file | QLR2-AN-32-27 |
| QBANDM | ascii file, gzipped file | QLR2-AN-472-305 |
| QBEACONF | ascii file, gzipped file | QLR2-AN-262-173 |
| QBORE3D | ascii file, gzipped file | QLR2-AN-315-233 |
| QBRANDY | ascii file, gzipped file | QLR2-AN-249-220 |
| QCAPRI | ascii file, gzipped file | QLR2-AN-353-271 |
| QE226 | ascii file, gzipped file | QLR2-AN-282-223 |
| QETAMACR | ascii file, gzipped file | QLR2-AN-688-400 |
| QFFFFF80 | ascii file, gzipped file | QLR2-AN-854-524 |
| QFORPLAN | ascii file, gzipped file | QLR2-AN-421-161 |
| QGFRDXPN | ascii file, gzipped file | QLR2-AN-1092-616 |
| QGROW15 | ascii file, gzipped file | QLR2-AN-645-300 |
| QGROW22 | ascii file, gzipped file | QLR2-AN-946-440 |
| QGROW7 | ascii file, gzipped file | QLR2-AN-301-140 |
| QISRAEL | ascii file, gzipped file | QLR2-AN-142-174 |
| QPCBLEND | ascii file, gzipped file | QLR2-AN-83-74 |
| QPCBOEI1 | ascii file, gzipped file | QLR2-AN-384-351 |
| QPCBOEI2 | ascii file, gzipped file | QLR2-AN-143-166 |
| QPCSTAIR | ascii file, gzipped file | QLR2-AN-467-356 |
| QPILOTNO | ascii file, gzipped file | QLR2-AN-2172-975 |
| QPTEST | ascii file, gzipped file | QLR2-AN-2-2 |
| QRECIPE | ascii file, gzipped file | QLR2-AN-180-91 |
| QSC205 | ascii file, gzipped file | QLR2-AN-203-205 |
| QSCAGR25 | ascii file, gzipped file | QLR2-AN-500-471 |
| QSCAGR7 | ascii file, gzipped file | QLR2-AN-140-129 |
| QSCFXM1 | ascii file, gzipped file | QLR2-AN-457-330 |
| QSCFXM2 | ascii file, gzipped file | QLR2-AN-914-660 |
| QSCFXM3 | ascii file, gzipped file | QLR2-AN-1371-990 |
| QSCORPIO | ascii file, gzipped file | QLR2-AN-358-388 |
| QSCRS8 | ascii file, gzipped file | QLR2-AN-1169-490 |
| QSCSD1 | ascii file, gzipped file | QLR2-AN-760-77 |
| QSCSD6 | ascii file, gzipped file | QLR2-AN-1350-147 |
| QSCSD8 | ascii file, gzipped file | QLR2-AN-2750-397 |
| QSCTAP1 | ascii file, gzipped file | QLR2-AN-480-300 |
| QSCTAP2 | ascii file, gzipped file | QLR2-AN-1880-1090 |
| QSCTAP3 | ascii file, gzipped file | QLR2-AN-2480-1480 |
| QSEBA | ascii file, gzipped file | QLR2-AN-1028-515 |
| QSHARE1B | ascii file, gzipped file | QLR2-AN-225-117 |
| QSHARE2B | ascii file, gzipped file | QLR2-AN-79-96 |
| QSHELL | ascii file, gzipped file | QLR2-AN-1775-536 |
| QSHIP04L | ascii file, gzipped file | QLR2-AN-2118-402 |
| QSHIP04S | ascii file, gzipped file | QLR2-AN-1458-402 |
| QSHIP08L | ascii file, gzipped file | QLR2-AN-4283-778 |
| QSHIP08S | ascii file, gzipped file | QLR2-AN-2387-778 |
| QSHIP12L | ascii file, gzipped file | QLR2-AN-5427-1151 |
| QSHIP12S | ascii file, gzipped file | QLR2-AN-2763-1151 |
| QSIERRA | ascii file, gzipped file | QLR2-AN-2036-1227 |
| QSTAIR | ascii file, gzipped file | QLR2-AN-467-356 |
| QSTANDAT | ascii file, gzipped file | QLR2-AN-1075-359 |
| S268 | ascii file, gzipped file | QLR2-AN-5-5 |
| STADAT1 | ascii file, gzipped file | QLR2-AN-2001-3999 |
| STADAT2 | ascii file, gzipped file | QLR2-AN-2001-3999 |
| STADAT3 | ascii file, gzipped file | QLR2-AN-4001-7999 |
| STCQP1 | ascii file, gzipped file | QLR2-AN-4097-2052 |
| STCQP2 | ascii file, gzipped file | QLR2-AN-4097-2052 |
| TAME | ascii file, gzipped file | QLR2-AN-2-1 |
| UBH1 | ascii file, gzipped file | QLR2-AN-18009-12000 |
| VALUES | ascii file, gzipped file | QLR2-AN-202-1 |
| YAO | ascii file, gzipped file | QLR2-AN-2002-2000 |
| ZECEVIC2 | ascii file, gzipped file | QLR2-AN-2-2 |
The CUTEr set of linear and nonlinear test problems and the Netlib set of linear programming test problems are also available.


2016/02/08: Basic Ruby Classes
In today's blog post I'll be giving a very brief overview of how to set up a basic class. To begin, let's discuss what a class is. In object oriented programming, a class is a template for an object--a blue-print, if you will. And to further the analogy, let's build a very basic house using classes.
We are going to create our template (class) of a house so that we can build a house for our friends Billy, Bob, and Joe. To minimize our work, we will create a template once, and use that to make a house for each of them, with perhaps a few distinct characteristics. We want to indicate what color is the house, what pet resides inside and what car we might find in the garage. Oh, and we should indicate who owns the house. We will use instance variables to keep track of this. Instance variables are variables that belong to a specific instance of our object. While every house can accept a pet and vehicle and color, each instance will be unique so that Billy's pet isn't going to be Bob's pet. Let's begin by defining the aforementioned attributes of these houses in our template. We will place the following code into a ruby file called "house.rb":
class House
attr_accessor :owner, :color, :pet, :garaged_vehicle
def initialize(owner = nil, color = nil, pet = nil, vehicle = nil)
@owner = owner
@color = color
@pet = pet
@garaged_vehicle = vehicle
end
def print_details
puts "#{@owner} owns this #{@color} house."
puts "On the couch sits #{@owner}'s pet<EMAIL_ADDRESS>puts "In the garage you'll find a<EMAIL_ADDRESS>end
end
Now we can assign everyone their houses based on their tastes.
billys_house = House.new("Billy","","frog","")
billys_house.color = "green"
billys_house.pet = "turtle"
billys_house.garaged_vehicle = "motorcycle"
bobs_house = House.new("Bob","white","cat","Mustang")
joes_house = House.new()
joes_house.owner = "Joe"
joes_house.color = "blue"
joes_house.pet = "dog"
joes_house.garaged_vehicle = "truck"
Notice that Billy doesn't have all of his information in the beginning. He only knows he has a frog. However, later he decides to change his pet to a turtle. Joe is even worse. When we first create Joe's house, he doesn't even know what he wants. We assign him ownership and his house attributes after-the-fact by setting the individual instance variables. This is allowed because we have declared those variables "attr_accessor" which allows us to use the dot-notation to read and write to these instance variables.
Next we call the instance method "print_details" to print the details of the houses.
billys_house.print_details
joes_house.print_details
bobs_house.print_details
Which when you run the code with "ruby house.rb", the following gets output to the console/terminal/STDOUT:
Billy owns this green house.
On the couch sits Billy's pet turtle.
In the garage you'll find a motorcycle.
Joe owns this blue house.
On the couch sits Joe's pet dog.
In the garage you'll find a truck.
Bob owns this white house.
On the couch sits Bob's pet cat.
In the garage you'll find a Mustang.
Notice how everyone's own house knows its own content?! This is the essence of a class. We used the class template to stamp out three different instances (copies) of the House class for each of our friends Billy, Bob and Joe. Pretty neat stuff. Until next time. -- JLH


Cocorita
Extends:
Cocorita class
Constructor Summary
| Public Constructor | ||
| public |
constructor(options: Object): Cocorita Constructor |
Member Summary
| Public Members | ||
| public |
Translations object |
|
| public |
Normally, when a target language translation is found missing, an empty string is emitted. |
|
| public |
initialize: String[] Array of target languages to be initialized if a translation is missing |
|
| public |
Target language |
|
| public set |
Set target language id |
|
| public get |
get target language id |
Method Summary
| Public Methods | ||
| public |
Get translations data serialized to json or yaml format |
|
| public |
Get a copy of translations data object |
|
| public |
Load translations data from a database file or a translations object |
|
| public |
Translate a string of source text in the target language. |
Public Constructors
Public Members
public defaultTarget: * source
Normally, when a target language translation is found missing, an empty string is emitted. If defaultTarget value is set to 'source', the source text is emitted instead.
Public Methods
public dump(format: String): String source
Get translations data serialized to json or yaml format
Params:
| Name | Type | Attribute | Description |
| format | String | 'json' or 'yaml' |
Throw:
public load(source: String | Object, format: String) source
Load translations data from a database file or a translations object
Throw:
public tr(source: String, replaces: Object): String source
Translate a string of source text in the target language.
If the translation is not available in the database the method return a blank string.
If the initialize option was passed to the constructor, then this method will check all the
target languages translations for the source text and will initialize them with a blank string
were are not available.
Emit:
Emitted if target translation does not exists in data base |


This is the response to the coding challenge received from Genesis Research.
You will find that the settings have been broken into four files.
common.py
,local.py
,test.py
,production.py
.
common.py
gives us a base file that is inherited in the other three files.
The settings in these files are overridden in each file if needed.
local.py
is a configuration for local development, these settings should not ever
be used in a production environment. They will and can expose sensitive information.
test.py
is a configuration for test environments. Much like local.py
these files should not be used in production. This file should be referenced when running automated tests.
production.py
is the configuration that should be used when deploying to a production
environment. This file is configured to run a Django server behind a load balancer that terminates
SSL. These are sane configurations, but should be reviewed before placing in to a production environment.
This project was built using Python 3.8, but should work on any version that is 3.6+. To run this environment you can follow the below steps.
clone https://github.com/DustinHolden/challenge.git
cd
into the root directorypython3 -m venv ./venv
) using your preferred methodsource ./venv/bin/activate
pip install -r requirements.txt
./manage.py migrate
./manage.py runserver
This project was set up to use the Argon2 password hasher. If you encounter any issues
installing requirements, you can comment out 'django.contrib.auth.hashers.Argon2PasswordHasher'
and remove argon2-cffi==20.1.0
from the requirements.txt
file. Argon2 is the recommended
password hasher for Django, but is not included by default.
Django-Environ was used to build most of the settings files. This library is very helpful in
setting sane defaults for each configuration. Though, you will note that there are not many defaults set
in the production.py
because we want to reference these settings from the servers environment.
If we do not want to reference them from the servers environment, we can distribute a .env
file
with these variables set. In most cases we want to keep the .env
outside of version control.
A few items that were left out of the production set up were error logging, performance monitoring, and cloud storage. I recommend using Sentry for error logging, New Relic for performance monitoring, and django-storages for interacting with different cloud providers.
For your convenience, a registration process was included. You can access it
here. Once you POST
your
response, you will receive a token. This token must be used in the REST API calls. Include
this token in the Authorization
header with a value in this format
Token YOUR_TOKEN_HERE
.
You can also browse the API via the Django Rest Framework browsable API by going here. You will still need to be logged in to access any information.
The Django admin has also been made available to create, update, or delete any information.
You will need to create a user with the appropriate authorization to access the admin.
./manage.py createsuperuser
is the quickest way to add a superuser. Then you can
log into the admin here.


Event Location:
Mt. Hood Community College
26000 S.E. Stark Street
Portland, Oregon
Abstract:
Well established relational database principles help us decide when and how to use the XML features in SQL Server. The audience will learn what's missing from the typical understanding of first normal form ("1NF") and how to apply 1NF to XML related database design choices. If you think (like many DBAs) that XML is a curse or (like some developers) that XML is a cure-all, this presentation is for you. Contrary to typical technology presentations, this focuses on what we should do over just a list of features and syntax.
Speaker(s): Eric Wilson,
Abstract:
SQL injection is a term you've heard often, but do you really understand what it means for a database developer or administrator? Can’t you just leave that to the application developers to deal with? This session will help you understand what SQL injection is, why it is a risk for your database, and how to guard against it.
Speaker(s): Rob Garrison,
Abstract:
Table index design and implementations have significant impact to the overall database performance and operations. In this session Joshua will take you through simple practical steps for: - Identifying Missing Indexes - Implementing Clustered Index - Optimizing Multiple Non-Clustered Indexes for a Table - Capturing Index Usages During the session, your questions and sharing your experience/knowledge are highly encouraged.
Speaker(s): Joshua Jin,
Abstract:
Partitioning is arguably the key feature needed to manage large SQL Server databases. In this presentation I will briefly review the main concepts of partitioning and then will provide information from actual experience in implementing partitioning, including code, tips and lessons learned. It is primarily focused on SQL 2005, but will include a brief discussion of the enhancements in SQL 2008.
Speaker(s): Steve Moss,
Abstract:
This session will cover T-SQL coding best practices. The basics on how to code T-SQL statements to optimize your queries will be covered. In this session you will discover some of the common pitfalls that can cause T-SQL statements to run slow. A number of demos will be done to show how by making slight changes in your code will minimize the resources used to process your queries. From this session you will be able to take home a list of T-SQL coding guidelines to help your code more efficient T-SQL statements.
Speaker(s): Greg Larsen,
Abstract:
Improving Performance while reducing storage costs through Compression. A partial list of items covered are: backup Compression Internals, how to enable Backup Compression, improving Backup Times, reducing Storage I/O and Space, restoring a database with Backup Compression, and what about going to tape?
Speaker(s): Ryan Lence,
Abstract:
Buck Woody, Microsoft's "Real World DBA" will show you how to use the Management Data Warehouse, Data Collector, and the new Activity monitor to fix unit and integration performance issues.
Speaker(s): Buck Woody,
Abstract:
Do you need five 9's of uptime? High Availability of applications and databases are rapidly becoming the "norm" around the globe. It is clearly one of the hottest topics that is important for database administrators, data architects and system architects to fully understand and to plan for. This presentation covers assessing, planning, choosing, implementing and administering a high availability solution along with the business justifications of different approaches to achieve high availability (including SQL Clustering, Data Replication, Database Mirroring, and Database Snapshots).
Speaker(s): Paul Bertucci,
Abstract:
What does and doesn’t work in a BI implementation? Rachel will cover what makes it work –the people skills, how to choose the right tool set and the best practices process for a successful implementation.Learn how to cross the IT-Business User chasm and build a successful career in an exploding field.
Speaker(s): Rachel Dyer,
Abstract:
How to create fewer, more capable reports with SQL Server 2008 Reporting Services, using expert patterns and recipes that meet multiple report requirements. Material will be presented from our forthcoming Wiley book: Super Reports – Patterns and Recipes for Reporting Services 2005 and 2008.
Speaker(s): Paul Turley,
Abstract:
For the IT pro and BI solution architects: How to provide the tools, training and environment to enable your business users to create useful reports. Train your business users to utilize Report Builder 2.0 and Analysis Services to achieve real business value. You will learn how to balance IT production reporting solutions from ad-hoc reporting and then migrate mission-critical prototype reports with the involvement of the user community.
Speaker(s): Paul Turley,
Abstract:
Everyone is getting hit with data security requirements. SQL 2005 introduced column-level encryption, but there are drawbacks to using it. The big security news in SQL Server 2008 is Transparent Data Encryption. On the surface, Transparent Data Encryption seems to be a security "silver bullet". The most important feature (besides securing the data) is that it does not require any changes to your application code. How much will TDE affect performance in an OLTP environment? This session will help you understand what TDE offers, discuss the list of caveats, and explain the performance testing and results.
Speaker(s): Rob Garrison,
This is a list of speakers from the XML Guidebook records. The details and URLs were valid at the time of the event.
LinkedIn: http://www.linkedin.com/in/paul-bertucci-59738b
Paul Bertucci is the founder of Data by Design, LLC (www.dataxdesign.com – formerly Database Architechs), a global database consulting firm with offices in the United States and Paris, France. Former Chief Architect/Shared Services Director for Autodesk (BI/DW/ODS, Big Data, Identity Management, SOA, Integration (EAI amp; ETL), MDM, Collaboration/Social, SaaS platforms, and Enterprise Architecture). Former Chief Data Architect at Symantec. Author SQL Server Unleashed book series, SQL Server High Availability, and SQL Performance and Tuning. Frequent speaker at Database and MDM conferences around the globe. Formal education: UC. Berkeley, Electrical Engineering and Computer Science.
LinkedIn: https://www.linkedin.com/in/pturley
Contact: http://www.sqlserverbiblog.com
Paul is a Principal Consultant for Pragmatic Works, a Mentor and Microsoft Data Platform MVP. He consults, writes, speaks, teaches blogs about business intelligence and reporting solutions. He works with companies around the world to model data, visualize and deliver critical information to make informed business decisions; using the Microsoft data platform and business analytics tools. He is a Director of the Oregon Data Community PASS chapter user group, the author and lead author of Professional SQL Server 2016 Reporting Services and 14 other titles from Wrox Microsoft Press. He holds several certifications including MCSE for the Data Platform and BI.
Rachel Dyer, Vice President of Implementation, joined On Demand Analysis® in 2001. She crosses the IT-User gap by playing a bit of both roles. Rachel is a graduate of Harvard University and Harvard Business School.
Contact: http://persistencevision.blogspot.com/
Rob is a Data Architect working for Fiserv in Portland, Oregon. He has over twenty years of IT experience, with most of that time focused on transactional SQL Server. He has a number of articles published and speaks regularly at user groups and other events.
LinkedIn: https://www.linkedin.com/in/pturley
Contact: http://www.sqlserverbiblog.com
Paul is a Principal Consultant for Pragmatic Works, a Mentor and Microsoft Data Platform MVP. He consults, writes, speaks, teaches blogs about business intelligence and reporting solutions. He works with companies around the world to model data, visualize and deliver critical information to make informed business decisions; using the Microsoft data platform and business analytics tools. He is a Director of the Oregon Data Community PASS chapter user group, the author and lead author of Professional SQL Server 2016 Reporting Services and 14 other titles from Wrox Microsoft Press. He holds several certifications including MCSE for the Data Platform and BI.
LinkedIn: http://www.linkedin.com/in/buckwoody
Contact: http://buckwoody.wordpress.com/
Born helpless, naked, and unable to provide for himself, Buck Woody overcame these amazing handicaps to become a software developer, data professional, teacher, and a productive invertebrate member of society.
Joshua Jin is a frequent speaker at SQL PASS local chapter in Portland, Oregon. He holds MCITP Business Intelligence Developer, Database Administrator, and Database Developer certifications for SQL Server 2005. Joshua is one of contributing authors of “Professional SQL Server 2005 Performance Tuning” book by Wiley/Wrox. At Intel IT, currently he is the development lead of a large SQL BI project for a private Cloud.
Steve Moss is the Data Architect at Ecova, the total energy and sustainability management company whose sole purpose is to see more, save more and sustain more for our clients. Steve has been working in IT for over 13 years as a Data Architect, Manager of Database Administration, Sr. DBA and Systems Consultant. He specializes in Microsoft data-centric techologies, including SQL Server, Analysis Services, Integration Services and other associated data technologies.
Eric has designed and implemented database-centric software solutions for 14 years in a variety of industries spanning financial, publication, e-commerce, and manufacturing. His passion is how to couple fundamental theory (principles) with pragmatic tradeoffs to achieve the best results. He has been a Developer, a DBA, and a Data Architect, including many years as team lead or manager. He has led both OLTP and DSS projects using SQL Server. In his spare time he is working toward a master's degre
Contact: http://persistencevision.blogspot.com/
Rob is a Data Architect working for Fiserv in Portland, Oregon. He has over twenty years of IT experience, with most of that time focused on transactional SQL Server. He has a number of articles published and speaks regularly at user groups and other events.
LinkedIn: https://www.linkedin.com/in/grlarsen/
Greg Larsen has been working with SQL Server since 1999. He has authored 100's of articles related to SQL Server. He holds a MCSE Data Management and Analytics. Greg also a SQL Server Consultant, adjunct professor and technical writer.
Contact: http://dbtune.net/default.aspx
Ryan Lence works as an independent Senior Database Engineer in Portland, Oregon. Ryan enjoys the challenges associated with designing stable, scalable, and redundant environments that enable businesses and their clients to focus on their primary mission. With over 12 years of Enterprise experience and numerous IT certifications Ryan's primary focus is SQL 2008. Ryan is currently working towards his MCM in SQL 2008.
The following is a list of sponsors that helped fund the event.


Quick Chocolate Chip
A classic with a dash of thinking-outside-the-box
Ingredients
- 1 package of chocolate chip cookie dough
This recipe works well for when you have a time-crunch problem, but still want to appear as though you put forth some effort in the kitchen.
Preheat the oven (to whatever temperature the package calls for, probably about 375 degrees). If your oven is anything like mine, it could take up to 15 minutes for it to actually get up to the right temperature. You might want to have an oven thermometer on hand just to double-check it.
Gather the “ingredients”. You want to make sure that you have the proper package (no one wants to bite into a cookie thinking it’s chocolate chip only to find out it’s oatmeal raisin). While not an ingredient, be sure to have two cookie sheets on hand (along with parchment paper if you don’t really want to have to clean up).
Open the package.

(For square package) Break off the pre-determined squares of dough and place them onto your baking sheets, evenly spaced so they won’t run together as they bake.
Set the timer for however long the package says (usually 4 minutes then flip the cookies to the other rack, top on bottom and bottom on top).
Set up your cooling racks. Due to the lack of counter space, you might just have to squeeze all of the cookies onto one rack. Or you can get a handy-dandy rack stand like I did and have multiple racks only take up the space of one.
Remove cookies from the oven when done. Grab a spatula and move the cookies onto the cooling racks. Turn off your oven, and let the cookies cool. If you time it right, the cookies can be cooling on the rack, wafting that “just baked” smell into the apartment as your friends walk in, amazed you had time and space to bake the cookies yourself.


| Opcode*/Instruction | Op/En | 64/32 bit Mode Support | CPUID Feature Flag | Description |
|---|---|---|---|---|
| 66 0F 3A 09 /r ib ROUNDPD xmm1, xmm2/m128, imm8 | RMI | V/V | SSE4_1 | Round packed double precision floating-point values in xmm2/m128 and place the result in xmm1. The rounding mode is determined by imm8. |
| VEX.128.66.0F3A.WIG 09 /r ib VROUNDPD xmm1, xmm2/m128, imm8 | RMI | V/V | AVX | Round packed double-precision floating-point values in xmm2/m128 and place the result in xmm1. The rounding mode is determined by imm8. |
| VEX.256.66.0F3A.WIG 09 /r ib VROUNDPD ymm1, ymm2/m256, imm8 | RMI | V/V | AVX | Round packed double-precision floating-point values in ymm2/m256 and place the result in ymm1. The rounding mode is determined by imm8. |
| Op/En | Operand 1 | Operand 2 | Operand 3 | Operand 4 |
| RMI | ModRM:reg (w) | ModRM:r/m (r) | imm8 | NA |
Round the 2 double-precision floating-point values in the source operand (second operand) using the rounding mode specified in the immediate operand (third operand) and place the results in the destination operand (first operand). The rounding process rounds each input floating-point value to an integer value and returns the integer result as a double-precision floating-point value.
The immediate operand specifies control fields for the rounding operation, three bit fields are defined and shown in Figure 4-24. Bit 3 of the immediate byte controls processor behavior for a precision exception, bit 2 selects the source of rounding mode control. Bits 1:0 specify a non-sticky rounding-mode value (Table 4-18 lists the encoded values for rounding-mode field).
The Precision Floating-Point Exception is signaled according to the immediate operand. If any source operand is an SNaN then it will be converted to a QNaN. If DAZ is set to ‘1 then denormals will be converted to zero before rounding.
128-bit Legacy SSE version: The second source can be an XMM register or 128-bit memory location. The destina-tion is not distinct from the first source XMM register and the upper bits (VLMAX-1:128) of the corresponding YMM register destination are unmodified.
VEX.128 encoded version: the source operand second source operand or a 128-bit memory location. The destina-tion operand is an XMM register. The upper bits (VLMAX-1:128) of the corresponding YMM register destination are zeroed.
VEX.256 encoded version: The source operand is a YMM register or a 256-bit memory location. The destination operand is a YMM register.
Note: In VEX-encoded versions, VEX.vvvv is reserved and must be 1111b, otherwise instructions will #UD.
| Rounding Mode | RC Field Setting | Description |
|---|---|---|
| Round to nearest (even) | 00B | Rounded result is the closest to the infinitely precise result. If two values are equally close, the result is the even value (i.e., the integer value with the least-significant bit of zero). |
| Round down (toward −∞) | 01B | Rounded result is closest to but no greater than the infinitely precise result. |
| Round up (toward +∞) | 10B | Rounded result is closest to but no less than the infinitely precise result. |
| Round toward zero (Truncate) | 11B | Rounded result is closest to but no greater in absolute value than the infinitely precise result. |
IF (imm[2] = ‘1) THEN // rounding mode is determined by MXCSR.RC DEST[63:0] (cid:197) ConvertDPFPToInteger_M(SRC[63:0]); DEST[127:64] (cid:197) ConvertDPFPToInteger_M(SRC[127:64]); ELSE // rounding mode is determined by IMM8.RC DEST[63:0] (cid:197) ConvertDPFPToInteger_Imm(SRC[63:0]); DEST[127:64] (cid:197) ConvertDPFPToInteger_Imm(SRC[127:64]); FI
ROUNDPD (128-bit Legacy SSE version)
DEST[63:0] (cid:197) RoundToInteger(SRC[63:0]], ROUND_CONTROL) DEST[127:64] (cid:197) RoundToInteger(SRC[127:64]], ROUND_CONTROL) DEST[VLMAX-1:128] (Unmodified)
VROUNDPD (VEX.128 encoded version)
DEST[63:0] (cid:197) RoundToInteger(SRC[63:0]], ROUND_CONTROL) DEST[127:64] (cid:197) RoundToInteger(SRC[127:64]], ROUND_CONTROL) DEST[VLMAX-1:128] (cid:197) 0
VROUNDPD (VEX.256 encoded version)
DEST[63:0] (cid:197) RoundToInteger(SRC[63:0], ROUND_CONTROL) DEST[127:64] (cid:197) RoundToInteger(SRC[127:64]], ROUND_CONTROL) DEST[191:128] (cid:197) RoundToInteger(SRC[191:128]], ROUND_CONTROL) DEST[255:192] (cid:197) RoundToInteger(SRC[255:192] ], ROUND_CONTROL)
__m128 _mm_round_pd(__m128d s1, int iRoundMode);
__m128 _mm_floor_pd(__m128d s1);
__m128 _mm_ceil_pd(__m128d s1)
__m256 _mm256_round_pd(__m256d s1, int iRoundMode);
__m256 _mm256_floor_pd(__m256d s1);
__m256 _mm256_ceil_pd(__m256d s1)
Invalid (signaled only if SRC = SNaN)
Precision (signaled only if imm[3] = ‘0; if imm[3] = ‘1, then the Precision Mask in the MXSCSR is ignored and preci-sion exception is not signaled.)
Note that Denormal is not signaled by ROUNDPD.
See Exceptions Type 2; additionally
| #UD | If VEX.vvvv ≠ 1111B. |


| Calidad | Coyoacan | Iztapalapa | Benito Juarez | Alvaro obregon | Coyoacan | Iztapalapa | Benito Juarez | Alvaro obregon |
|---|---|---|---|---|---|---|---|---|
| $300 | $400 | $450 | $900 | $300 | $400 | $450 | $900 | |
| $400 | $500 | $650 | $1000 | $400 | $500 | $650 | $1000 | |
| $600 | $800 | $950 | $1500 | $600 | $800 | $950 | $1500 | |
| $700 | $900 | $1050 | $1700 | $700 | $900 | $1050 | $1700 | |
| $800 | $900 | $1150 | $1800 | $800 | $900 | $1150 | $1800 |


Misc. configurations
This article explains how miscellaneous configuration files on Pikifen work. These are plain engine text files.
Game configuration
This file controls some general settings about how the game works. It can be found in Game_data/Misc/Config.txt
. Create it if it does not exist. The defaults can be found here.
The following properties exist:
game_name
: Name of the fangame.game_version
: Version of the fangame. Can be anything, but the preferred format is something like "1.2.3".
carrying_color_move
: Color to use for the carrying numbers when an object that is meant for the ship is being carried. Format is "red green blue" or "red green blue alpha".carrying_color_stop
: Same as above, but for when the object is not moving.carrying_speed_base_mult
: When an object is being carried, its movement speed depends on the carriers' average speed (and more). With 0 carriers, the average speed is multiplied by base_mult, and with all spots taken, it's multiplied by max_mult. This property controls the base value. In other words, this controls how high the slowest speed of a carried object is.carrying_speed_max_mult
: Same as above, but the max_mult. In other words, this controls how high the fastest speed of a carried object is.carrying_speed_weight_mult
: For every 1 unit of weight, decrease the carrying speed by this much.
day_minutes_start
: When a normal day starts. This follows a format similar to real life, so 0 is midnight, 60 is 1 AM, 120 is 2 AM, 420 is 7 AM.day_minutes_end
: Same as above, but for when the day ends.day_minutes_per_irl_sec
: For every real-time second, these many in-game minutes pass.
pikmin_order
: Preferred order to sort Pikmin with. Used when swapping Pikmin, dismissing them, organizing them in an Onion, etc. Separate each type with a semicolon (;). e.g.Red Pikmin;Yellow Pikmin;Blue Pikmin
. Types you do not specify will go to the end of the list.standard_pikmin_height
: The height of a "standard" Pikmin, i.e. a Pikmin that's not shorter or taller than most. Used to help calculate some physics logic.standard_pikmin_radius
: The radius of a "standard" Pikmin, i.e. a Pikmin that's not skinnier or fatter than most. Used to help calculate some physics logic.
leader_order
: Likepikmin_order
, but for the leaders.spray_order
: Likepikmin_order
, but for sprays.
idle_task_range
: Minimum distance between a Pikmin and a task before the Pikmin can take the task, when the Pikmin is idling.swarm_task_range
: Same as above, but for a Pikmin in the group during swarming.max_pikmin_in_field
: Maximum number of Pikmin that can be on the field.maturity_power_mult
: Every maturity level, multiply a Pikmin's attack power by this much.maturity_speed_mult
: Every maturity level, multiply a Pikmin's walking speed by this much.pikmin_chase_range
: Pikmin will chase after enemies unless they're this far away.
can_throw_leaders
: "true" if it's possible to throw leaders, "false" if not.cursor_max_dist
: Maximum distance away from the leader that their cursor can go to.cursor_spin_speed
: How quickly the mouse cursor's icon spins, in degrees per second.next_pluck_range
: When auto-plucking, a leader will only choose the next Pikmin if it is within this distance.onion_open_range
: Leaders can open an Onion if they're within this range from the center of the Onion object.group_member_grab_range
: A leader can grab the closest group member only if it is within this distance.pluck_range
: A leader can pluck a Pikmin only if it is within this distance.whistle_growth_speed
: How quickly the whistle's radius grows in size, in pixels per second.
message_char_interval
: Time interval between characters when displaying a message, in seconds. 0 shows the entire text instantly.zoom_max_level
: Maximum level of zoom (i.e. how close the camera can get).zoom_min_level
: Minimum level of zoom (i.e. how far away the camera can get).
HUD
The position and size of the HUD's elements can be customized in Game_data/Misc/HUD.txt
. In order to work with any window size, this data is specified in percentages, not pixels. This means that an X and Y of "50" equals the center of the screen on any window size.
There are two blocks, positions
and files
. Inside the first block, every property's value takes on the format x y w h
, which are the X and Y coordinates of the center of the item, plus the total width and total height. The numbers you put in don't use a percentage sign. To hide a HUD element, just put 0 0 0 0
. Inside the second block, you just specify the file name of the image that represents a HUD element, or a HUD element's component.
The list of properties for each block is as follows. The defaults can be found here.
Positions
time
: Time of day, represented by the Sun Meter.day_bubble
: The bubble for the current day number.day_nr
: Current day number.leader_1_icon
: Icon of the current leader.leader_2_icon
: Icon of the next leader.leader_3_icon
: Icon of the next next leader.leader_1_health
: Health wheel of the current leader.leader_2_health
: Health wheel of the next leader.leader_3_health
: Health wheel of the next next leader.pikmin_standby_icon
: Icon of the type of Pikmin in standby (the closest Pikmin), sans leaf/bud/flower.pikmin_standby_m_icon
: Icon of the maturity of the Pikmin in standby.pikmin_standby_x
: Multiplication sign ("×"), found to the right of the standby icon in Pikmin and Pikmin 2.pikmin_standby_nr
: Number of Pikmin of the standby type.pikmin_group_nr
: Number of Pikmin on the leader's group.pikmin_field_nr
: Number of Pikmin on the field.pikmin_total_nr
: Number of total Pikmin (field + Onions).pikmin_slash_1
: One of the slashes that go between the counter numbers. There are three of them to be used at will, depending on how many counter numbers you want visible.pikmin_slash_2
: See above.pikmin_slash_3
: See above.spray_1_icon
: Icon of the spray, when there is only one type, icon of spray #1 (the "up" one), when there are two types, or icon of the currently selected spray, when there are more than 2.spray_1_amount
: Same as above, but its amount. This includes the multiplication sign ("×").spray_1_button
: Same as above, but the button to press.spray_2_icon
: Icon of spray #2 (the "down" one), when there are two types.spray_2_amount
: Same as above, but its amount. This includes the multiplication sign ("×").spray_2_button
: Same as above, but the button to press.spray_prev_icon
: Icon of the previous spray on the list, when there are more than two types.spray_prev_button
: Same as above, but the button to press.spray_next_icon
: Icon of the next spray on the list, when there are more than two types.spray_next_button
: Same as above, but the button to press.
Files
bubble
: Standard, circular bubbles. Used on the standby Pikmin icon, leader icons, etc.checkbox_check
: A checkbox's "check". Used in menus.counter_bubble_field
: The bubble in which the Pikmin-on-field counter is contained.counter_bubble_group
: Same as above, but the in-group counter.counter_bubble_standby
: Same as above, but the counter of group members of the current standby type.counter_bubble_total
: Same as above, but the Pikmin total counter.day_bubble
: The bubble in which the day counter is contained.distant_pikmin_marker
: The graphic that gets overlayed on top of the standby Pikmin's icon, to indicate that the closest Pikmin is too far away to grab.hard_bubble
: A rough, hard bubble. Used on the Sun Meter, leader icons, etc.message_box
: A message box's background.mouse_button_1_icon
: Icon that represents the left mouse button.mouse_button_2_icon
: Icon that represents the right mouse button.mouse_button_3_icon
: Icon that represents the middle mouse button.mouse_wheel_down_icon
: Icon that represents the mouse wheel being scrolled down.mouse_wheel_up_icon
: Icon that represents the mouse wheel being scrolled up.no_pikmin_bubble
: Bubble to show when there are no Pikmin in the group.sun
: Icon for the sun in the Sun Meter.
Spike damage
"Spike damage" is a mechanic where objects that suffered damage can immediately retaliate by damaging their attacker. In the Pikmin games, this is used by a White Pikmin to release poison to the enemy that ate it, in order to cause poison damage. In the engine, the same can be done, but any object can retaliate in any way, whether it is swallowed or damaged normally.
The folder Game_data/Spike_damage_types
controls the types of spike damage that exist in the game. Each text file represents one type of spike damage, and the properties inside control how it works. The name of the file does not matter.
The properties are:
name
: The name of this type of spike damage. You will need to use this name when referring to this type elsewhere.damage
: How much damage to cause. What exactly this number means depends on theis_damage_ratio
property.ingestion_only
:true
if the spike damage should only be caused when the object is ingested,false
if it's meant to be caused when the object is hurt normally. Ingestion only works for Pikmin.is_damage_ratio
: Iftrue
, then the number specified indamage
is the ratio of total health to sap away. For instance,0.5
means one half of the enemy's total health is removed. Iffalse
, the number is just a normal amount of damage. Default isfalse
.particle_generator
: When the damage is applied, some particles can be spawned. This is the name of the particle generator to use, if any. The particles are spawned in the position of the object that receives the damage.particle_offset
: If particles are meant to spawn, you can offset them from the object's center here. The format isx y z
, and these are relative coordinates.
Remember to change the object type properties for the objects you want to deal this spike damage, as well as the different spike damage vulnerability modifiers, as explained here.
System asset file names
Some graphics and sounds are used by the engine in several ways, instead of used specifically for a user-made enemy, area, etc. Inside the file Game_data/Misc/System_asset_file_names.txt
you can specify the file name (and path) of some or all of these assets. This text file has a list of properties, where each property's name is the name of the asset, and the value is the file name, inside the folder Game_data/Graphics
. Example: mouse_cursor = Asterisk.png
will make the mouse cursor in-game use the Asterisk.png
image. You can find the defaults in the source code, in the function init_asset_file_names
, visible here.
area_name_font
: Font to use for area names.bubble_box
: Bubble-like box. In-engine, it is split into three equal-sized rows and three equal-sized columns, and uses that split to texture the boxes.checkbox_check
: The checkmark of checkboxes in menus.cursor
: Leader cursor.cursor_invalid
: Overlay to place on top of the leader cursor when a throw is invalid.counter_font
: Font to use for counters in the HUD.editor_icons
: Spritesheet where all editor icons are.enemy_spirit
: Enemy spirit.swarm_arrow
: Arrow that comes out from the leader when swarming.icon
: The game's icon.idle_glow
: Glowing effect on idle Pikmin.main_font
: The game's main text font.main_menu
: Background for the main menu.more
: Icon used in menus to indicate there is still more content beyond. This graphic faces the right, and gets flipped in-engine when needed.mouse_button_1_icon
: Icon for the left mouse button.mouse_button_2_icon
: Icon for the right mouse button.mouse_button_3_icon
: Icon for the middle mouse button.mouse_cursor
: Mouse cursor.mouse_wheel_down_icon
: Icon for the mouse wheel scrolling down.mouse_wheel_up_icon
: Icon for the mouse wheel scrolling up.notification
: Notification bubble.pikmin_silhouette
: Silhouette of a Pikmin. Used in the area editor's cross-section feature.pikmin_spirit
: Pikmin spirit.shadow
: Object shadows.smack
: Smack particle.smoke
: Smoke particle.sparkle
: Sparkle particle.spotlight
: Spotlight texture to use for blackout weather.value_font
: Font to use for numeric values, like the carrying fraction numbers.wave_ring
: Particle for waves in water, used when objects are standing in water.
Title screen
The title screen (or main menu) has some settings that can be changed, mostly in regards to the logo made up of Pikmin. These are all specified in /Game_data/Misc/Title_screen.txt
.
The settings for the logo are inside a logo
block. They are:
min_screen_limit
: Top-left coordinates of the logo's placement on-screen, in screen width or height percentage. For example,10 20
means the logo starts at 10% of screen width, and 20% of the screen height.max_screen_limit
: Same as above, but for the bottom-right.pikmin_max_speed
: Each Pikmin's speed is random. This is the maximum speed possible, in pixels per second.pikmin_min_speed
: Same as above, but minimum possible.pikmin_speed_smoothness
: The closer to their destination, the more the Pikmin slow down, based on this multiplier.0.08
is a good number.pikmin_sway_amount
: How many pixels a Pikmin sways left or right when standing still.pikmin_sway_max_speed
: Each Pikmin's swaying speed is random. This is the maximum speed, in radians per second (the Y part is ignored when swaying).pikmin_sway_min_speed
: Same as above, but the minimum speed.pikmin_size
: Pikmin size, in screen dimension percentage. For instance,3 2
means each Pikmin cannot be any larger than 3% of the screen width nor 2% of the screen height.pikmin_types
: This block specifies the types of Pikmin you'll encounter in the title logo. Except every type is simply defined by the image of its flower. In this block, every line is a type, in the formatcharacter = image
, wherecharacter
is a text character representing this Pikmin type in the logo map (see below), andimage
is the name of the image in the/Game_data/Graphics
folder (extension included).map
: A representation of the logo. The Pikmin are organized in a grid, and that grid is spread to fit in the limits specified above. Every line in this block represents a line in the grid, with every character matching a cell in that line. A character represents a Pikmin type or a blank space, if it's a character specified in thepikmin_types
block or a dot (.
), respectively.


Issue 6454:
Create FBTest that covers HTML panel search
Steps to reproduce
- Open Firebug, select the HTML panel
- Use the search box to search in the panel
- There should be 10 occurences of 'testing' (case insensitive)
- There should be 4 occurences of 'testing' (case sensitive)
- There should be 5 occurences of 'Testing' (case insensitive)


--- layout: tweet ---
Off to Ash Wednesday service with home community.
2/25/2009, 5:07:21 PM
Favs: 0
Retweets: 0


{% load static %}
{% include "quiz/navbar.html" %}
Create gamified Quizzes and interactive lessons to engage any learner.
NavGrills
Get Started With NavGrills
{% include "quiz/footer.html" %}


Telegram chat: clickhouse_en
Wechat: 4 groups (ask your friend to invite)
PostgreSQL wire protocol Geographical dictionaries Data coarsening with TTL expressions Parallel calculation of FINAL Insertion into ODBC and JDBC Cassandra dictionary source Dictionary layout for SSD Settings for data formats in dictionaries Removal of leader election for replicas Support for Distributed over Distributed queries Query metrics from PMU GROUP BY optimization on sorted data Apache Arrow import/export MsgPack format "direct" dictionary source
— Compact data parts (since version 20.3).
— In-memory data parts (since version 20.6).
— Write-Ahead Log (since version 20.6).
— Durability settings (since version 20.10).
Developer — Anton Popov.
1. Wide — the classic format.
2. Compact — all columns in a single file.
3. Memory — all data in memory.
Managed by the following settings:
— min_bytes_for_wide_part,
min_rows_for_wide_part:
if the size is bigger — then use wide format.
— min_bytes_for_compact_part,
min_rows_for_compact_part:
if the size is bigger — then use compact format,
if less — use memory format.
Wide > Compact > Memory
The classic format.
Every column and index in its own files.
Optimal for reading from disk, especially from slow HDDs.
Zero-cost ALTER ADD/REMOVE COLUMN.
All columns in a single file.
Optimal for data insertion.
Especially on slow filesystems.
Less optimal for reading.
It's recommended for small data parts.
Not recommended to enable for all data parts.
Available since version 20.3, but disabled by default.
Since version 20.10 enabled by default for data parts up to 10 MB.
Data in RAM.
+ optional Write-Ahead Log.
— in_memory_parts_enable_wal;
— write_ahead_log_max_bytes.
Even better performance on insertion...
... if you did not enable write-ahead log.
Even better performance for reading...
... but data in memory is stored uncompressed.
All data parts are replicated as usual.
This is an experimental feature.
What if all your data is stored on a single server?
What if you don't use replication?
What if you do use replication but within a single region?
— so, we need to simply call fsync before answering to INSERT query?
Eat My Data (2007):
http://mirror.linux.org.au/pub/linux.conf.au/2007/video/talks/278.pdf
Files Are Hard (2015):
https://danluu.com/file-consistency/
PostgreSQL "Fsyncgate" (2018):
https://lwn.net/Articles/752063/
Can Applications Recover from fsync Failures? (2020):
https://www.usenix.org/conference/atc20/presentation/rebello
What if all your data is stored on a single server?
What if you don't use replication?
What if you do use replication but within a single region?
Then take this:
— min_rows_to_fsync_after_merge;
— min_compressed_bytes_to_fsync_after_merge;
— min_compressed_bytes_to_fsync_after_fetch;
— fsync_after_insert;
— fsync_part_directory;
— write_ahead_log_bytes_to_fsync;
— write_ahead_log_interval_ms_to_fsync;
— in_memory_parts_insert_sync.
The functions: normalizeQuery, normalizedQueryHash.
SELECT normalizeQuery(query) FROM system.query_log
— replaces literals to ?
— replaces lists of literals to ?..
— replaces complex aliases to `?`
Available since version 20.8.
One my friend has a query...
... but he don't want to show it to me.
Solution:
clickhouse-format --obfuscate < query.sql
Available since version 20.10.
Data Obfuscation: https://presentations.clickhouse.tech/highload_spb_2019/#
CREATE TABLE hits
(
event_time DateTime,
...
) ENGINE MergeTree ORDER BY ...
TTL event_time + INTERVAL 1 MONTH
RECOMPRESS CODEC(ZSTD(1)),
event_time + INTERVAL 1 YEAR
RECOMPRESS CODEC(ZSTD(6))
Developer — Alexander Sapin. Available since version 20.10.
CREATE TABLE hits
(
event_time DateTime CODEC(Delta, Default),
...
) ENGINE MergeTree ORDER BY ...
ALTER TABLE hits MODIFY COLUMN c
REMOVE COMMENT|CODEC|TTL
|DEFAULT|MATERIALIZED|ALIAS
Developer — Alexander Sapin. Available since version 20.10.
SELECT * EXCEPT(secret_column) FROM table;
SELECT table.* REPLACE(
(URL LIKE '%yandex%' ? '' : URL) AS URL) FROM table;
SELECT COLUMNS('^packet_') FROM table;
SELECT t.* APPLY(sum) FROM table AS t;
SELECT COLUMNS(x, y, z) APPLY(sum) FROM table;
Developer — Amos Bird, mfridental. Available since version 20.10.
COLUMNS('regexp'): developer — mfridental. Available since version 19.12.
20.11 — testing.
20.10 — stable.
20.9 — stable.
20.8 — LTS until 2021-09-30.
20.7 ... 20.4 — obsolete.
20.3 — LTS until 2021-03-12.
...
19.14 — obsolete.
Streaming data import from RabbitMQ.
Kerberos authentication for Kafka.
WITH for subqueries with global scope (Amos Bird).
New formats: Regexp, RawBLOB, JSONAsString, LinesAsString.
Allow to run clickhouse without packages and configs.
system.crash_log table, Sentry integration.
Aggregate function for rank correlation statistic.
256bit Decimal.
Backups.
GRPC interface.
Projections (Amos Bird).
Support for OpenTracing.
An alternative to ZooKeeper.
Hedged distributed requests.
Reading of subcolumns from tables.
Semi-duplicate text matching (ucasFL).
Functions for geographical data analysis.


Project:
par_ui
License: BSD
Dependencies:
std_msgs
roscpp
par_kinematics
par_trajectory_planning
tinyxml
Used by: None
All Packages
Main Page
Classes
Files
Class List
Class Members
Config Member List
This is the complete list of members for
Config
, including all inherited members.
chatter_pub_cmd
Config
[private]
cmd
Config
[private]
config
Config
[private]
Config
(ros::ServiceClient &coord_client, par_kinematics::coord &coords, par_trajectory_planning::commands &cmd, ros::Publisher &chatter_pub_cmd)
Config
coord_client
Config
[private]
coords
Config
[private]
parse_xml_init
()
Config
[private]
parse_xml_ptp
()
Config
[private]
parse_xml_ptp_row
(TiXmlNode *node, double &X, double &Y, double &Z, uint16_t &operating_mode)
Config
[private]
read
(const std::string &file)
Config
par_ui
Author(s): Wouter van Teijlingen
autogenerated on Mon Jun 13 2011 17:06:40


So this report is basically to inform people who are on an SSRI such as Prozac and are considering DXM use.
I was on a 20mg daily dose of Prozac starting last summer for anxiety and depression. Looking back, and seeing all the side effects as I have stopped taking it, really makes me almost regret starting it in the first place. While it helped me grow a lot, I feel that there are other ways of dealing with depression that don't involve chemicals.
Starting last month (June), I stopped taking my dose (as instructed by my physician). I felt that I no longer needed it, and just didn't like the idea of being on medicine indefinitely. Once stopping, I remembered reading about DXM online and decided that I would try it once I gave my body some time to cycle the Prozac. After a week, I started getting common withdrawal symptoms of the medicine. I had a symptom referred to as 'brain shocks' or 'brain zaps.' It is very hard to explain, and if you would like to know more I suggest searching online. This can be a very uncomfortable symptom, and at this point I was really regretting ever starting the medicine, as nobody had ever informed me that the withdrawal would be intense at all. The next week, I was still experiencing these brain zaps, albeit less frequently and less intensely. I can only imagine what a withdrawal from a larger dose or from something like Paxil would be like.
I decided that the medicine was probably almost completely out of my system, so I had my first experience with DXM. It was a very good experience, and the next day I realized that my withdrawal symptoms were completely gone. I assumed the Prozac was out of my system, and finally felt free of it. I repeated the DXM maybe about 10 times in the next few weeks.
It has been about 4 days since taking DXM, as my tolerance was ridiculous and I can't really go into stores and buy 3 bottles of cough syrup for very long before raising suspicions. This situation seemed fine, but yesterday I started experiencing the exact same Prozac withdrawal symptoms again (extremely vivid dreams, brain zaps). I have since concluded that DXM acts similar to an SSRI. It was replacing my daily Prozac dose for the few weeks that I was taking it. I stopped experiencing withdrawal symptoms because my body simply thought I had started my Prozac again. I was very upset when I learned this, as it felt like I was chained to a drug again. I took one of my pills yesterday (a common thing doctors will tell you to do to ease withdrawal symptoms), but I plan on never taking one again.
I will not use DXM for a while, as this time I want to be absolutely sure that my body is not dependent on an SSRI and that dosing will not just result in loss of progress to free myself from the little pill.
Thank you for reading and be safe!!
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.