Session tokens transmission over HTTP
- Login to web app (get session token) and with this session walk through all of the app functionality, search for HTTPS to HTTP transitions and new cookies reception. Use Burp proxy history.
- Are all Set-Cookie directives tagged as Secure?
- Does app accept login over HTTP if URL modified?
- If login over HTTP - Is new session token issued after login phase?
- If app uses HTTPS everywhere. Is server's port 80 opened? Can be any pages there accessed with authenticated session?
Session tokens transmitted via GET requests
- Even if authentication uses POST request, test if same parameters can be used in GET request
Sesion tokens in Logs
- Identify logging or monitoring functionality where session tokens can be viewed(Discover content)
- Identify instances where session tokens are transmitted through GET requests
- Inject target with off-site links to your server and watch log on your webserver if it contains Referer header with session token
Vulnerable mappings of tokens to sessions
- Test if is possible to login with same username from 2 different computers. If yes, attacker can login without being detected.
- Login and logout few times and check if new session token is generated every time.
Session caching enabled
- Check if in all authenticated requests is Cache-Control: max-age=0 so that session token is not cached on HTTP proxy
Vulnerable session termination
- Examine session token expiration time and settings (What Expires= times are used on persistent cookies, and are they
- reasonable?)
- Test logout functionality if it really invalidates session on the webserver and not just in the browser
- Logout function should be on all authenticated pages and as visible as possible
- Test if expiration of cookie has effect on cookie expiration on the server.
Client Exposure to Token Hijacking
- Identify cross-site scripting vulns and determine if they can be used against site users
- Identify format of issued tokens and try to modify it and login with it.
- Examine if token created for unathenticated user may be later used to retrieve user's sensitive data
Session Fixation
- If site issues tokens to unathenticated users and doesn't issue new session token after login phase then it's vulnerable to session fixation
- If session token is issued after the login, try to login again with this token and different user and check if token didn't changed and now is used with new user
- Try if arbitrary token string can be passed to web app
- Attacker can forge login request and let user to login with that request which contains attacker known session token
Cookie Domain/Path Restrictions
- Search sensitive cookies for domain andpathattributes and for setting it to parent domain or root path. If found then cookies can be submitted to parent domain and all subdomains (bad!) (in case of path=/cookie is sent to all subdirectories)
- Check if there is trailing /in pathdirective
- Cookie without domain attribute is resent only to domain it was issued from
- Cookie with domain attribute is resent in requests to domain and all subdomains
- Create list of sensitive cookies with their domains and subdomains access


After a careful review of the wholesale and retail gas trading and scheduling process it has been decided that the Gas Logistics teams should report directly into the Enron America's Commercial organization. This realignment will help to strengthen the commercial focus and communication between the trading desks and the schedulers and will play a critical role as Enron tries to maximize opportunities and maintain a competitive trading edge. The details are as follows:
Wholesale
Bob Superty will maintain his management of the Logistics support functions which include the Transport Rate team (Kim Olinger), Electronic Commerce team (Tammy Lee-Jaquet) and Regulatory Affairs teams (Suzanne Calcagno). In addition, Bob will now manage the Northeast Logistics team as part of the East desk. Bob will report directly to Scott Neal and will also help coordinate the Logistics function across all regions working closely with each of the regional Logistics Managers, Commercial desk heads and Enron Americas senior management team.
Victor LaMadrid will manage the Southeast Logistics team and will report directly to Scott Neal. Victor's knowledge and overall east desk experience will be critical to help maximize east desk opportunities and promote new initiatives across all regions.
Lisa Kinsey will manage the Central Logistics team and will report directly to Hunter Shively.
Patti Sullivan will manage the West Logistics team and will report directly to Mike Grigsby.
Darren Farmer will manage the Texas Logistics team and will report directly to Tom Martin
George Smith will manage the Well Head Logistics team and will report directly to Fred Lagrasta.
Retail
Donna Greif will now report directly to Don Black. Each of the regional Logistics Managers (East - Marde Driscoll-Ernest, Central - Charlie Muzzy, West - Sabra Dinari) will continue to report directly to Donna. Donna will continue her ongoing efforts in the development and integration of the new retail trading systems, prior period adjustments and development of a strong and talented Logistics team.
Congratulations to all involved and welcome to the commercial gas team - John Lavorato, President and CEO, Enron Americas.
_____________________________________________________________________________________________________________________
Assistants - Please forward on to your groups.
***********
EDRM Enron Email Data Set has been produced in EML, PST and NSF format by ZL Technologies, Inc. This Data Set is licensed under a Creative Commons Attribution 3.0 United States License <http://creativecommons.org/licenses/by/3.0/us/> . To provide attribution, please cite to "ZL Technologies, Inc. (http://www.zlti.com)."
***********
California


The 'Resource' is what is being booked or reserved.
A resource can be anything you want, a room (meeting room, exercise room, etc), a person (doctor, hair stylist, etc) or an object (computer, golf clubs, Ferrari)
This screen is used to set basic information about the resource such as name, description and cost.
Also here is where you can assign users as resource administrators. A user that has been assigned as an
administrator will, when logged in and viewing the front end booking screen, see an 'Administrator' link.
This link will open a front-end admin screen that will allow them to view and process resource requests. They will only be able to see requests for resources that they are 'Administrator' for.
Cancel: Abort changes and return to the previous screen.
Save: Save changes and return to the previous screen.
Help: Opens this help screen.
Name: A resource must have a name. ex: 'Meeting Rom A' or 'Dr. Allan Harper.'
Description: The description is often just set to the name but can also include more information. This is the field that will be shown in the dropdown list so keep it as short as possible.
Cost: Cost is a free form text field so you can put things like `$10/hr + $20 deposit`. This appears in the resource dropdown list for the customer.
Rate: Rate is used by the PayPal implementation. Rate is the amount you charge as a decimal number. This is used by the system to calculate total charge for PayPal.
Email To: To have notifications for this resource sent to one or more special email addresses, enter them here. Example: foo@bar.com,abc.xyz.com (use comma to separate multiple addresses) If this field is left blank resource requests will be sent to the address specified in the configuration section. The resource level overrides the component level. If you set a notification address at the resource level, the component level is ignored, if you want both you will need to add both at the resource level.
SMS Phone: To have SMS text message notifications sent to this resource enter a cell phone here (only one supported). This feature requires a Clickatell account be setup and configured. See the Configure screen Clickatell tab. If this field is left empty, no SMS messages will be sent to the resource.
SMS notifications are sent, to the resource, on these events :
- New booking
- User cancel from front end
- Booking status change; [status any status] -> accepted, by admin or front-end admin.
- Booking status change; [status any status] -> cancelled, by admin or front-end admin.
Prevent Duplicate Bookings / Max Duplicated:
Prevent Duplicate Bookings = No: means, don't even check, allow any number of duplicates.
Prevent Duplicate Bookings = Yes: means, check for dupes and stop any more than Max Duplicates.
Max Dupe = 0, allow only the first booking
Max Dupe = 1, allow initial booking + one duplicate (2 bookings total)
Max Dupe = 2, allow initial booking + two duplicates (3 bookings total)
etc..
Global = use the duplicate booking setting at the control configuration level.
Default Calendar Category: Enter a default calendar category for this resource. This is only applicable if you are using 'auto-accept' and a 3rd party calendar (JCalPro or JEvents)
Resource Administrators: Select one or more users to be administrators for this resource. When a resource administrator accesses the front-end control they see only requests for their resources. A user can administer one or many resources and a resource can have one or many administrators.
Time Slots: Global = use 'Global' time slots Resource specific = this resource has it's own time slots defined. Use the Time Slots screen to set time slots.
Allow Booking on Days: Un-check any days you wish to be disabled on the popup calendar.
Non-work day message: For days not chceked above, you can display an optional message in the GAD grid for that day. <br>Example:"-- not available --" or "*** My Day Off ;-) ***"
Minimum lead time**: Enter the minimum number of hours a person can book ahead. This was added for sites allowing 'current day' booking.
Example: set to 1 = someone can book an appointment for 1 hour from now, set to 24 and attempts to book appointments less than 24 hours from now will be blocked.
Normal setting is '0' with Disable Dates Before set to 'Tomorrow' means a visitor can book anytime tomorrow.
Disable Dates Before**: Dates to disable on user's popup calendar.
Disable Dates After**: Dates to disable on user's popup calendar.
You can use the above two settings when you want to allow bookings on ONLY certain dates, ex: appointments during a 3 day event. Disable dates before and after the event so users can only book appointments during the event.
Leave as 'Tomorrow' and 'Not Set' for day to day appointment booking on an on-going basis.
Display Order: Enter a number to indicate what order this resource should appear in the dropdown list.
Published: Only resources with Published set to Yes will appear in the dropdown list on the Booking screen
** These settings do not change the Graphic Availability Display (GAD) booking screen grid but do effect the validation. That means a user may see a timeslot that shows as available but when they try to book it the validation may tell them there is not enough lead time.


I am a reasonably competent surfer, but new enough to the sport that I remember what it was like to be a complete beginner. Here are some tips I wish I had been given when I was just getting started:
- Start with a longboard. You'll want a 9-foot or even a 10-foot board for learning. If you're very small, you might get away with an 8-footer, but whatever you do, don't get a 6'1" potato chip just because all your friends are shortboarders or because the guy behind the counter at the surf shop thinks longboards are uncool. You'll catch more waves, enjoy yourself more and learn much more quickly on a longboard. Even a second-hand longboard will likely be expensive, but that just means you'll almost certainly be able to sell it for the same price if you decide to switch to a shorter board (despite what some people think, longboards aren't "training wheels" for riding waves—some of the most skillful surfers I have ever seen were riding longboards).
- Pop-up method. A lot of people will tell you should "pop up in one smooth motion". This is by far the least useful piece of advice given to beginner surfers, and you should ignore it completely.   Rather than keeping your back straight, however, you should arch it so that only your upper body is elevated; your pelvis should remain more or less planted on the board.

The key point to keep in mind in this step is that your feet move forward to be under your body, rather than your body moving back to be over your feet. A rearward shift of weight on a surfboard puts the brakes on, allowing the wave to overtake you. If you find yourself kneeling on your surfboard at any point during your popup, you are probably making this mistake, rocking your hips back to be over your knees, causing your surfboard to slow down. Avoid this mistake by remembering these important words of wisdom: "bum low, head high".
If you find yourself making an A-frame of your body, legs straight, bent at the waist, with both your hands and feet on the board, it is because you have straightened your legs before you should have. Keep your knees bent until your feet are under your body.
Note that this step SHOULD be performed in one smooth motion.
-
You should now be in a deep crouch, with your hands still planted on your board. Stand up (this step is optional).
-
Paddle smarter, not harder. The second most useless piece of advice given to beginners is "paddle harder!" Sure, you have to paddle hard to get a wave, especially when you lack the judgement and manoeuverability needed to be at the wave's sweet spot at just the right time, but come on—you're already paddling harder than any of the experienced surfers out there. What you need to do is paddle the right way, using your body posture to adjust your fore-and-aft weight distribution at certain, critical moments.
When you see a wave coming, start paddling to get up a bit of speed. Just before the wave gets to you, keep paddling steadily, but adjust your weight distribution backwards by arching your back, moving your head and shoulders as far up and back as you can (watch some shortboarders sometime to see how they do it).
I find that throwing my weight forward in this manner is far more effective than simply paddling harder. This explains how an experienced surfer can sometimes catch a wave with a single stroke, while a furiously windmilling beginner just falls off the back of the same wave.
-
Don't grab the rails when popping up. I already mentioned this, but it is worth repeating here as a separate tip: when popping up, place your hands flat on the board in front of you, rather than grabbing the rails. There is a tendency for beginners to cling to their boards like grim death rather than popping up when they slide down the face of a wave, and having a firm grip on the board will make this all the more likely. Later, when you are a good surfer, grabbing the rails may be useful in some circumstances, but it can hold you back when you're learning.
The final two points are safety tips:
- Fall flat.  Head-first falls should definitely be avoided.
- Always be ready to turn turtle. "Turning turtle"—grabbing the sides of your surfboard and capsizing it—is useful for getting under waves. It is also useful for avoiding being hit by another surfer who is getting too close. Don't wait to find out if you are going to be hit; turn turtle right away if you are in any doubt at all.
So why do people say you should pop up "in one smooth motion"? Because that's how it feels when you put it all together on a steep wave. Watch people surfing for a while, though; you'll notice that on gentler waves—the kind you should be learning on—surfers will often hold the arched-back push-up position for a second or two to be sure they have caught the wave before completing their pop-ups. Evidently, breaking the popup down into discrete steps is not just a mental exercise for learning purposes, but an actual, functional technique as well.


WARNINGS AND "TOKENS."
AMONGST the mining population there is a deeply-rooted belief in warnings. The following, related by a very respectable man, formerly a miner, well illustrates this -
"My father, when a lad, worked with a companion (James or 'Jim,' as he was called) in Germo. They lived close by Old Wheal Grey in Breage. One evening, the daughter of the person with whom they lodged came in to her mother, crying, 'Billy and Jim ben out theer for more than a hour, and I ben chasm them among the Kilyur banks, and they waan't ler me catch them. As fast as I do go to one, they do go to another.' 'Hould your tongue, child,' said the mother; ''twas their forenoon core, and they both ben up in bed this hours.' 'I 'm sure I ben chasm them,' said the girl. The mother then went up-stairs and awoke the lads, telling them the story. One of them said, ''Tis a warning; somethin will happen in un old end, and I shan't go to mine this core.' 'Nonsense,' said the other; 'don't let us be so foolish;. the child has been playing with some strangers, and it isn't worth while to be spaled for any such foolishness.' 'I tell you,' replied the other,' I won't go.' As it was useless for one man to go alone, both remained away. In the course of the night, however a run took place in the end they were working in, and tens of thousands of kibblefuls came away. Had they been at work, it was scarcely possible for them to have escaped."
At Wheal Vor it has always been and is now believed that a fatal accident in the mine is presaged by the appearance of a hare or white rabbit in one of the engine-houses. The men solemnly declare that they have chased these appearances till they were hemmed in apparently, without being able to catch thçm. The white rabbit on one occasion being run into a "windbore" lying on the ground, and, though stopped in, escaped.
In this mine there appears to be a general belief among the men in "tokens" and supernatural appearances. A few months since, a fine old man reported, on being relieved from his turn as watcher, that during the night he heard a loud sound like the emptying of a cartload of rubbish in front of the account-house, where he was staying.  The poor fellow, considering the strange sound as a "warning," pined away and died within a few weeks.


Vostok Spaceport
Web services
Grafana
http://localhost:6303/
Graphite Web
http://localhost:6304/
Kibana
http://localhost:6305/
Gate
http://localhost:6306/
Management API
http://localhost:6307/
Tracing API
http://localhost:6308/


[1]
Seamless useability.; Kind of pricey compared to competitors.
[2]
easy ti use; Gave me my actuel on the wrong street ???


{% extends "base.html" %} {% block content %}
The administrator has been notified. Sorry for the inconvenience!


Select your location
United States - English
United States - Spanish
Afghanistan - English
Albania - English
Algeria - French
Algeria - English
American Samoa - English
Angola - English
Anguilla - English
Antigua - English
Argentina - Spanish
Argentina - English
Armenia - English
Aruba - English
Australia - English
Austria - German
Austria - English
Azerbaijan - English
Bahamas - English
Bahrain - English
Bangladesh - English
Barbados - English
Belarus - English
Belgium - English
Belgium - French
Belgium - Dutch
Belize - English
Benin - English
Bermuda - English
Bhutan - English
Bolivia - Spanish
Bolivia - English
Bonaire (Netherlands Antilles) - English
Bosnia Herzegovina - English
Botswana - English
Brazil - Portuguese
Brazil - English
British Virgin Islands - English
Brunei - English
Bulgaria - Bulgarian
Bulgaria - English
Burkina Faso - English
Burundi - English
Cambodia - English
Cameroon - English
Canada - English
Canada - French
Cape Verde - English
Cayman Islands - English
Central African Republic - English
Chad - English
Chile - Spanish
Chile - English
China - Chinese
China - English
Colombia - Spanish
Colombia - English
Comoros - English
Congo - English
Congo, The Democratic Republic of - English
Cook Islands - English
Costa Rica - Spanish
Costa Rica - English
Croatia - English
Curacao (Netherlands Antilles) - English
Cyprus - Greek
Cyprus - English
Czech Republic - Czech
Czech Republic - English
Denmark - Danish
Denmark - English
Djibouti - English
Dominica - English
Dominican Republic - Spanish
Dominican Republic - English
Ecuador - Spanish
Ecuador - English
Egypt - English
El Salvador - Spanish
El Salvador - English
Equatorial Guinea - English
Eritrea - English
Estonia - Estonian
Estonia - English
Ethiopia - English
Fiji - English
Finland - Finnish
Finland - English
France - French
France - English
French Guiana - English
French Polynesia - English
Gabon - English
Gambia - English
Georgia - English
Germany - German
Germany - English
Ghana - English
Gibraltar - English
Greece - Greek
Greece - English
Grenada - English
Guadeloupe - English
Guam - English
Guatemala - Spanish
Guatemala - English
Guinea - English
Guinea Bissau - English
Guyana - English
Haiti - English
Honduras - Spanish
Honduras - English
Hong Kong - Chinese
Hong Kong - English
Hungary - Hungarian
Hungary - English
Iceland - English
India - English
Indonesia - English
Iraq - English
Ireland (Republic of) - English
Israel - Hebrew
Israel - English
Italy - Italian
Italy - English
Ivory Coast - English
Jamaica - English
Japan - Japanese
Japan - English
Jordan - English
Kazakhstan - English
Kenya - English
Kiribati - English
Kosovo - English
Kosrae Island - English
Kuwait - English
Kyrgyzstan - English
Laos - English
Latvia - Latvian
Latvia - English
Lebanon - English
Lesotho - English
Liberia - English
Libya - English
Lithuania - Lithuanian
Lithuania - English
Luxembourg - French
Luxembourg - English
Macau - Chinese
Macau - English
Macedonia (FYROM) - English
Madagascar - English
Malawi - English
Malaysia - English
Maldives - English
Mali - English
Malta - English
Marshall Islands - English
Martinique - English
Mauritania - English
Mauritius - English
Mayotte - English
Mexico - Spanish
Mexico - English
Moldova - English
Mongolia - English
Montenegro - English
Montserrat - English
Morocco - French
Morocco - English
Mozambique - English
Namibia - English
Nepal - English
Netherlands - Dutch
Netherlands - English
New Caledonia - English
New Zealand - English
Nicaragua - Spanish
Nicaragua - English
Niger - English
Nigeria - English
Northern Mariana Islands - English
Norway - Norwegian
Norway - English
Oman - English
Pakistan - English
Palau - English
Panama - Spanish
Panama - English
Papua New Guinea - English
Paraguay - Spanish
Paraguay - English
Peru - Spanish
Peru - English
Philippines - English
Poland - Polish
Poland - English
Ponape - English
Portugal - Portuguese
Portugal - English
Puerto Rico - Spanish
Puerto Rico - English
Qatar - English
Reunion - English
Romania - Romanian
Romania - English
Rota - English
Russia - Russian
Russia - English
Rwanda - English
Saba (Netherlands Antilles) - English
Saipan - English
Samoa - English
Saudi Arabia - English
Senegal - English
Serbia - English
Seychelles - English
Sierra Leone - English
Singapore - English
Slovakia - Slovak
Slovakia - English
Slovenia - English
Solomon Islands - English
South Africa - English
South Korea - Korean
South Korea - English
Spain - Spanish
Spain - English
Sri Lanka - English
St. Barthelemy - English
St. Croix - English
St. Eustatius (Netherlands Antilles) - English
St. John - English
St. Kitts and Nevis - English
St. Lucia - English
St. Maarten (Netherlands Antilles) - English
St. Thomas - English
St. Vincent and the Grenadines - English
Suriname - English
Swaziland - English
Sweden - Swedish
Sweden - English
Switzerland - English
Switzerland - German
Switzerland - French
Syria - English
Taiwan - Chinese
Taiwan - English
Tajikistan - English
Tanzania - English
Thailand - English
Tinian - English
Togo - English
Tonga - English
Tortola - English
Trinidad and Tobago - English
Truk - English
Tunisia - French
Tunisia - English
Turkey - Turkish
Turkey - English
Turkmenistan - English
Turks and Caicos - English
Tuvalu - English
US Virgin Islands - English
Uganda - English
Ukraine - English
Union Island - English
United Arab Emirates - English
United Kingdom - English
United States - English
Uruguay - Spanish
Uruguay - English
Uzbekistan - English
Vanuatu - English
Venezuela - Spanish
Venezuela - English
Vietnam - Vietnamese
Vietnam - English
Virgin Gorda - English
Wallis and Futuna - English
Yap - English
Yemen - English
Zambia - English
Zimbabwe - English
Remember this location.
Copyright © 1994-2016 United Parcel Service of America, Inc. All rights reserved.
Web Site Terms of Use
|
Privacy Notice
|
U.S. Home
|
UPS Solutions


SIGN UP.
User Name
Email
Mobile No.
Password
Show Password
Security Question
Who was your childhood hero?
What is your favourite color?
What is your best friend name?
Answer
Sign Up


Pivot
Converts information present in rows to columns
For example if the input table is as follow:
|Plate|Parameter|Dimension|
+-----+---------+---------+
| 1|height | 245|
| 1|width | 480|
| 2|height | 490|
| 2|width | 960|
If you select Pattern as Pivot columns and use ${Parameter} for Pattern and
set in the Other Columns tab Plate for Keys and Dimension for the Values, you will obtain the following result:
|Plate|height |width |
+-----+---------+---------+
| 1| 245| 480|
| 2| 490| 960|
If you change in the Other Columns tab, the Keys to Dimension and the Values to Plate, you will obtain the following table:
|Dimension|height |width |
+---------+---------+---------+
| 245| 1| ?|
| 280| ?| 1|
| 490| 2| ?|
| 960| ?| 2|
If you elect Plate as Pivot columns and choose in the Other Columns tab Parameter for Keys and Dimension for the Values (assuming the domain of Plate
was computed before, using the Domain Calculator KNIME node) setting the Pattern to ${Plate} will yield the following result:
|Parameter|1 |2 |
+---------+----+----+
|height | 245| ?|
|width | 490| ?|
|height | ?| 280|
|width | ?| 960|
Finally, you might want to pivot using the data in Parameter, rather than Plate. To do this, select Plate as Pivot columns,
and choose in the Other Columns tab Parameter for Keys and Dimension for the Values
after what you should change the Pattern to: "${}_on_plate_${Plate}". Doing this will result in the following table:
|Parameter|Dimension_on_plate_1|Dimension_on_plate_2|
+---------+--------------------+--------------------+
|height | 245| 280|
|width | 490| 960|
See also: sample workflow.
Dialog Options
- Pivot columns
- Values from these columns will become the parts of the columns in the result table (no columns with these names will be present). The domain of these columns should be available. Please use Domain Calculator node to achieve this.
- Pattern
- The format of the new columns.
${} - is replaced by the value contained in the columns selected as Values (in the Other Columns tab),
${pivot column name} value(s) of one of the nominal column used for pivoting (cf. columns selected in Pivot columns)).
- Behaviour
-
Handling of missing values in the result:
- fillEmpty - put empty cells.
- signalError - stop the conversion with an error.
What to do if there will be missing parts in the result:
- fillEmpty - put empty cells there
- signalError - stop the conversion with error.
- HiLite Strategy
- Support HiLite or not.
- Other Columns/Values
- The values of these columns will be added as part of the newly created columns names in place of ${}.
- Other Columns/Keys
- Data used for in the resulting cells.
Ports
- Input Ports
-
| 0 |
A table with known domains for the keys and pivoting columns. |
- Output Ports
-
| 0 |
Pivoted Table: The resulting transformed table. |
| 1 |
Reverse Pattern: A variable containing the pattern to use with the unpivot node. |


I'm Abhijit Das a.k.a silverFoxA
I'm a passionate mobile application and web developer.
I have started my professional career as a graphics designer. I had no coding background, I just learnt all myself from the open resources out there in internet. Becoming a programmer was just a dream, it was a dream of contributing something to virtual reality, which I thought pretty intersting 4 years back and I still think there's so many things to explore.
I strive to be an enterprenuer, with only one goal in mind, which is to make one of the rights, "Right to Information" truely valid.
"You can't connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future."
-Lt Steve Jobs
This is how I work
Study Project
More than 80% of the product's success lies in the problem statement. Hence I focus more on it to ensure User Acceptance.
Design
Design models brings sense to the idea and the study put spices to it, to make it interactive with better user experience.
Product Development
Development is completely simple, as all the details are made, clean code is the key point.
Success
Finally the product development comes to an end after handing over to the user and getting valid good response.


This Customised Kia Seltos Looks Deceptively Cool With Black Wheels
by Surendhar MKia Seltos has been customised by an owner with Lenso wheels, Michelin tyres, black roof and front grille garnish among other changes
We showed you a couple of modified versions of the Kia Seltos based on off-road theme, recently taken at a dealer display in the United States and they boded well with the flowing styling package the regular SUV carries.
The Seltos has been around for nearly three months now and we have not seen a whole lot of modifications done to the vehicle by owners and it does really surprise us considering the popularity of the five-seater that became the most sold SUV in the country in October 2019 and it could continue to do so in the coming months.
Pictures of an accessorised Seltos appeared on the internet further reiterate why the mid-size SUV is supple to modifications. Posted by its owner ‘Mr. Sunoj Palliyal on a Facebook group, the mod job looks sportier than the stock model with only a few alterations to its exterior and he thinks the accessories are competitively priced for the Seltos.
 The side lower door cladding is also blackened for a more serious appeal.
The stock tyres are opted for new Michelins with 16-inch black Lenso alloy wheels. The basic paint protection film from Llumar replaces the standard sun film and the PPF (Paint Protection Film) has to be attended by trained experts, said the Seltos’ owner. Elements like mats and chrome embellishments are not available in the market for the SUV just yet according to him.
He tried matte wrapping the brand’s signature Tiger Nose front grille but at least thrice the carbon wrap peeled off due to contours in the grille and the only solution is to get it painted for no such hassle, he suggested. The black alloys, in particular, do enhance the bold stature of the SUV.


Voice programming: a how-to
01:15 PM - 01:40 PM on August 16, 2015, Room 701Evan Fredericksen
- Audience level:
- intermediate
- Watch:
- http://youtu.be/mKUkp6CiNtU
Description
Despite the many people who suffer from RSI, the subject of programming by voice is still a relatively unexplored one. Although there are numerous proof-of-concept demonstrations available online and many brilliant pieces of software that make voice programming possible, much of the configuration and learning of best practices are left to the user. This talk will cover what exactly goes into creating and using a voice programming environment.
Abstract
Programming by voice is a subject that naturally raises suspicions about its feasibility.
There are several components involved in a voice programming environment: the speech-to-text engine, transferring this text to the user's system (sometimes a surprisingly difficult task), figuring out how to match certain text patterns to functions, keystrokes and mouse actions, and finding and configuring a text editor or IDE that can accommodate these requirements. I will talk about my experiences with tooling for each step of the way, as well as various best practices found through personal trial and error.
Finally, I will talk about the potential for using for voice commands in gaming. The games will be primarily slower, turn-based games that voice commands can augment or even replace keyboard and (to a lesser extent) mouse-driven input.


nips nips2000 nips2000-lda knowledge-graph by maker-knowledge-mining
topicId: wordWeight*wordName (topN-words)
topic #0: 0.008*gaussianization + 0.005*irwls + 0.005*svc + 0.004*retinotopic + 0.004*eye + 0.003*univariate + 0.003*postural + 0.003*position + 0.003*auditory + 0.002*intermediate
topic #1: 0.005*variational + 0.003*qx + 0.003*ssms + 0.002*qo + 0.002*factorisation + 0.002*diag + 0.002*junction + 0.001*qz + 0.001*conjugacy + 0.001*ssm
topic #2: 0.008*auditory + 0.005*source + 0.005*masking + 0.004*frequency + 0.004*sources + 0.003*tone + 0.003*sound + 0.003*separation + 0.003*refiltering + 0.003*responses
topic #3: 0.004*singularities + 0.003*fo + 0.002*jeffreys + 0.002*kullback + 0.002*fq + 0.002*da + 0.002*asymptotic + 0.002*pole + 0.002*watanabe + 0.002*algebraic
topic #4: 0.007*hmm + 0.006*fields + 0.006*receptive + 0.005*mds + 0.005*asr + 0.004*bands + 0.004*subband + 0.003*bases + 0.003*frequency + 0.003*olshausen
topic #5: 0.004*imprinted + 0.004*oscillatory + 0.003*wo + 0.003*stored + 0.003*imprinting + 0.002*excitatory + 0.002*resonant + 0.002*frequency + 0.002*oscillation + 0.001*iwt
topic #6: 0.008*slds + 0.004*switching + 0.003*lip + 0.003*lds + 0.003*lca + 0.003*viterbi + 0.003*hmm + 0.002*bank + 0.002*emotion + 0.002*bases
topic #7: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #8: 0.006*speech + 0.005*microphone + 0.004*denoising + 0.003*clean + 0.003*dereverberation + 0.002*enhancement + 0.002*ar + 0.002*reverberation + 0.001*production + 0.001*dff
topic #9: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #10: 0.009*reinforcement + 0.008*weights + 0.006*local + 0.006*risk + 0.006*cost + 0.006*approximate + 0.006*framework + 0.006*task + 0.005*machines + 0.005*optimal
topic #11: 0.007*shape + 0.003*matching + 0.003*shapes + 0.003*prototypes + 0.002*correspondences + 0.002*prototype + 0.002*ssd + 0.002*descriptor + 0.001*tps + 0.001*contexts
topic #12: 0.008*aoa + 0.004*naming + 0.004*assignment + 0.004*transforms + 0.003*phone + 0.003*pji + 0.003*tlle + 0.003*sse + 0.003*stream + 0.002*factored
topic #13: 0.004*albuquerque + 0.004*mexico + 0.003*bartlett + 0.003*predictor + 0.002*nm + 0.002*gn + 0.002*schapire + 0.002*lipschitz + 0.002*inequalities + 0.001*mathematics
topic #14: 0.005*kalman + 0.003*conditioning + 0.003*whitening + 0.003*blocking + 0.003*backward + 0.002*goodall + 0.002*sound + 0.002*trials + 0.002*wn + 0.001*wagner
topic #15: 0.007*arrival + 0.005*poisson + 0.004*tmdp + 0.004*traffic + 0.003*admission + 0.003*piecewise + 0.003*call + 0.003*scheduling + 0.002*driving + 0.002*link
topic #16: 0.006*nnbm + 0.005*neuron + 0.004*ppa + 0.003*nnbd + 0.003*contribution + 0.002*nonnegative + 0.002*lesions + 0.002*evolved + 0.002*lesioned + 0.002*translationally
topic #17: 0.011*kernel + 0.006*image + 0.006*feature + 0.006*matrix + 0.005*bounds + 0.005*covariance + 0.005*images + 0.005*neurons + 0.005*support + 0.005*data
topic #18: 0.010*synaptic + 0.005*postsynaptic + 0.003*stdp + 0.003*plasticity + 0.003*hebbian + 0.003*depression + 0.002*rare + 0.002*potentiation + 0.002*presentation + 0.002*triggered
topic #19: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #20: 0.004*string + 0.003*text + 0.003*strings + 0.002*subsequences + 0.002*sx + 0.002*document + 0.002*substrings + 0.002*subsequence + 0.002*substring + 0.001*documents
topic #21: 0.005*ocular + 0.004*dominance + 0.003*arbor + 0.002*stripe + 0.002*topography + 0.002*eigenfunctions + 0.002*obermayer + 0.002*equilibrium + 0.002*wr + 0.002*wl
topic #22: 0.006*jensen + 0.004*discriminative + 0.003*attentional + 0.002*rf + 0.002*dendritic + 0.002*mel + 0.002*criteria + 0.001*latent + 0.001*macaque + 0.001*contemporary
topic #23: 0.009*ht + 0.002*auxiliary + 0.002*wtw + 0.002*wiah + 0.002*wia + 0.001*nmf + 0.001*ialt + 0.001*nonincreasing + 0.001*ub + 0.001*halt
topic #24: 0.006*penev + 0.005*jlx + 0.004*pr + 0.003*atick + 0.003*xo + 0.003*dij + 0.002*redlich + 0.002*uij + 0.002*factorial + 0.002*neighborhoods
topic #25: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #26: 0.007*scheme + 0.006*variational + 0.005*word + 0.004*words + 0.004*schemes + 0.004*derivation + 0.004*plefka + 0.003*trigram + 0.003*sjj + 0.003*language
topic #27: 0.009*baback + 0.004*mitsubishi + 0.004*excitatory + 0.003*moghaddam + 0.003*attention + 0.003*electric + 0.002*desimone + 0.002*branch + 0.002*laboratory + 0.002*modulatory
topic #28: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #29: 0.006*almap + 0.003*voted + 0.002*romma + 0.002*wk + 0.002*corrections + 0.002*nn + 0.001*ilw + 0.001*gentile + 0.001*corr + 0.001*testerr
topic #30: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #31: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #32: 0.009*posterior + 0.007*random + 0.006*convergence + 0.006*sampling + 0.005*pi + 0.005*conditions + 0.005*chain + 0.004*shape + 0.004*generate + 0.004*weak
topic #33: 0.012*margin + 0.008*bound + 0.008*speech + 0.008*points + 0.007*signal + 0.007*theorem + 0.007*perceptron + 0.007*signals + 0.006*classifier + 0.006*algorithms
topic #34: 0.007*winnow + 0.004*cavity + 0.004*wj + 0.004*spin + 0.004*regularized + 0.004*spins + 0.003*freezing + 0.003*ui + 0.003*restoration + 0.002*hyperparameters
topic #35: 0.006*lagrange + 0.006*dictionary + 0.005*multiplier + 0.004*letter + 0.004*demixing + 0.003*lagrangian + 0.003*hmms + 0.003*multipliers + 0.003*word + 0.003*cica
topic #36: 0.009*boltzmann + 0.006*gibbs + 0.005*tap + 0.005*agents + 0.005*experts + 0.004*bound + 0.003*third + 0.003*blocker + 0.003*energy + 0.003*tuned
topic #37: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #38: 0.010*cells + 0.006*place + 0.005*activity + 0.005*occam + 0.005*hippocampal + 0.004*robot + 0.004*razor + 0.003*gatsby + 0.003*population + 0.003*neuroscience
topic #39: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #40: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #41: 0.004*contours + 0.003*clustering + 0.003*sphere + 0.003*cluster + 0.002*clusters + 0.002*tel + 0.002*valleys + 0.002*enclosed + 0.002*enclose + 0.002*aviv
topic #42: 0.014*stimulus + 0.007*response + 0.007*firing + 0.006*cell + 0.006*gain + 0.006*inhibition + 0.006*inhibitory + 0.005*stimuli + 0.005*switch + 0.005*amplitude
topic #43: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #44: 0.004*bonuses + 0.003*shaping + 0.003*bonus + 0.003*oa + 0.003*dopamine + 0.002*novelty + 0.002*schultz + 0.002*da + 0.002*trial + 0.001*cs
topic #45: 0.007*generalisation + 0.007*classifiers + 0.005*particle + 0.004*metropolis + 0.004*bayes + 0.003*rejection + 0.003*contour + 0.003*pw + 0.003*contours + 0.003*condensation
topic #46: 0.004*rbmrate + 0.003*eigenfaces + 0.002*gallery + 0.002*individuals + 0.002*lighting + 0.002*feret + 0.002*fisherfaces + 0.001*replicas + 0.001*corr + 0.001*months
topic #47: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #48: 0.004*profit + 0.004*success + 0.003*modes + 0.003*sk + 0.003*diseases + 0.003*densest + 0.003*frey + 0.003*probable + 0.003*variational + 0.003*symptom
topic #49: 0.005*lda + 0.005*disturbance + 0.004*rl + 0.004*controller + 0.003*cepstral + 0.003*pendulum + 0.003*rrl + 0.003*bhattacharyya + 0.002*discriminant + 0.002*bayes
topic #50: 0.004*svd + 0.004*zj + 0.003*gensvd + 0.003*scan + 0.002*uo + 0.002*hansen + 0.002*uj + 0.002*scans + 0.001*qj + 0.001*generalizable
topic #51: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #52: 0.005*rbm + 0.005*visible + 0.003*sisj + 0.003*qo + 0.003*generative + 0.002*contrastive + 0.002*sj + 0.002*units + 0.002*causal + 0.002*experts
topic #53: 0.007*document + 0.003*documents + 0.003*plsa + 0.002*web + 0.002*phits + 0.002*topics + 0.002*links + 0.002*link + 0.002*dj + 0.002*zk
topic #54: 0.008*tree + 0.007*process + 0.006*gp + 0.005*nn + 0.005*bayesian + 0.005*dimension + 0.005*infinite + 0.004*graphs + 0.004*iterative + 0.004*unit
topic #55: 0.013*network + 0.013*hidden + 0.008*networks + 0.008*object + 0.008*variables + 0.008*variable + 0.007*representation + 0.007*structure + 0.007*system + 0.006*learned
topic #56: 0.009*mdl + 0.008*kfd + 0.003*fisher + 0.003*flmp + 0.003*discriminant + 0.002*geometric + 0.002*prt + 0.002*gcm + 0.002*lim + 0.002*distinguishable
topic #57: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #58: 0.005*source + 0.005*abnormal + 0.003*votes + 0.003*instances + 0.002*vote + 0.002*rbf + 0.002*nash + 0.002*hypersphere + 0.002*sources + 0.002*abnormalities
topic #59: 0.005*tunneling + 0.005*egocentric + 0.005*parietal + 0.005*bump + 0.004*circuit + 0.004*floating + 0.003*ihei + 0.003*gate + 0.003*allocentric + 0.002*competitive
topic #60: 0.005*spike + 0.004*amt + 0.003*source + 0.003*xia + 0.003*smt + 0.003*nmf + 0.002*diag + 0.002*lr + 0.002*hh + 0.002*msec
topic #61: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #62: 0.010*model + 0.010*state + 0.009*models + 0.008*policy + 0.008*reward + 0.007*action + 0.007*probability + 0.006*agent + 0.006*states + 0.006*decision
topic #63: 0.004*uv + 0.002*yd + 0.002*ug + 0.002*wp + 0.002*vp + 0.002*wb + 0.002*hp + 0.002*xg + 0.002*xw + 0.002*yy
topic #64: 0.005*option + 0.004*taxi + 0.004*options + 0.003*distinctions + 0.002*leaf + 0.002*passenger + 0.002*execution + 0.001*temporally + 0.001*automated + 0.001*navigate
topic #65: 0.010*ica + 0.008*binary + 0.007*inference + 0.007*code + 0.007*layer + 0.006*codes + 0.006*xj + 0.006*propagation + 0.005*proposed + 0.005*phase
topic #66: 0.007*nets + 0.004*net + 0.003*hu + 0.003*overfitting + 0.003*bp + 0.002*mlps + 0.002*capacity + 0.002*excess + 0.002*stopping + 0.002*backprop
topic #67: 0.008*input + 0.008*learning + 0.007*units + 0.007*output + 0.007*prior + 0.006*field + 0.005*density + 0.005*distribution + 0.005*recurrent + 0.005*rule
topic #68: 0.008*causal + 0.004*option + 0.003*price + 0.003*flp + 0.003*softplus + 0.003*pricing + 0.002*wb + 0.002*universal + 0.002*power + 0.002*approximator
topic #69: 0.006*audio + 0.005*smart + 0.005*molecules + 0.004*facesync + 0.004*synchronization + 0.003*chips + 0.003*video + 0.003*photo + 0.003*switches + 0.003*biochemical
topic #70: 0.006*sprite + 0.005*video + 0.003*motion + 0.003*animation + 0.003*path + 0.002*sprites + 0.002*animations + 0.002*ik + 0.001*rendering + 0.001*visually
topic #71: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #72: 0.007*symbolic + 0.005*anagram + 0.004*reordering + 0.004*diagrams + 0.003*subsymbolic + 0.003*pruning + 0.003*cognition + 0.002*diagram + 0.002*vn + 0.002*shuffled
topic #73: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #74: 0.005*phrases + 0.005*phrase + 0.003*classifiers + 0.002*cscl + 0.002*shallow + 0.002*snow + 0.002*csp + 0.002*sls + 0.002*slo + 0.001*parsing
topic #75: 0.007*shot + 0.005*relaxation + 0.005*segmentation + 0.005*clustering + 0.005*pairwise + 0.005*distances + 0.005*initial + 0.004*clusters + 0.004*xj + 0.004*duration
topic #76: 0.010*error + 0.009*xi + 0.009*gaussian + 0.008*kernels + 0.008*approximation + 0.007*exp + 0.006*regression + 0.006*processes + 0.005*order + 0.005*eigenvalues
topic #77: 0.012*permitted + 0.006*separable + 0.005*pham + 0.005*forbidden + 0.005*steady + 0.004*wn + 0.004*xiyi + 0.003*xy + 0.003*hyperplane + 0.003*ham
topic #78: 0.005*transform + 0.004*coder + 0.003*quantizer + 0.002*latent + 0.002*coders + 0.002*coding + 0.002*qa + 0.002*partitioning + 0.001*dony + 0.001*cot
topic #79: 0.012*bayesian + 0.008*noise + 0.007*parameters + 0.005*control + 0.004*domain + 0.004*tr + 0.004*therefore + 0.004*ex + 0.004*instances + 0.004*query
topic #80: 0.004*chip + 0.004*duty + 0.003*oscillators + 0.003*voltages + 0.002*oscillator + 0.002*leg + 0.002*locomotion + 0.002*vb + 0.002*legs + 0.002*gait
topic #81: 0.010*filter + 0.008*spike + 0.008*time + 0.007*rate + 0.006*video + 0.006*temporal + 0.006*graph + 0.005*patterns + 0.005*dynamic + 0.005*xt
topic #82: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #83: 0.000*synaptic + 0.000*dynamic + 0.000*filter + 0.000*synapses + 0.000*uij + 0.000*zq + 0.000*network + 0.000*hj + 0.000*wij + 0.000*fading
topic #84: 0.002*burgess + 0.001*patients + 0.001*hemispatial + 0.001*mental + 0.000*cacucd + 0.000*externally + 0.000*visuospatial + 0.000*activated + 0.000*falling + 0.000*stars
topic #85: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #86: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #87: 0.008*synapse + 0.007*synapses + 0.003*postsynaptic + 0.003*spike + 0.003*rk + 0.002*fl + 0.002*synaptic + 0.002*msec + 0.002*xk + 0.001*specificity
topic #88: 0.003*gps + 0.003*kt + 0.003*posterior + 0.002*online + 0.002*gp + 0.002*predictors + 0.002*yla + 0.002*kl + 0.002*overcome + 0.002*birmingham
topic #89: 0.005*unlabeled + 0.004*yli + 0.004*ams + 0.004*suppression + 0.003*noise + 0.003*snr + 0.003*speech + 0.003*labeled + 0.002*discriminative + 0.002*modulation
topic #90: 0.011*algorithm + 0.011*training + 0.008*svm + 0.007*test + 0.007*yi + 0.006*class + 0.006*examples + 0.006*boosting + 0.005*machine + 0.005*sets
topic #91: 0.009*belief + 0.008*nodes + 0.008*graphical + 0.006*sigmoid + 0.006*audio + 0.006*mean + 0.006*si + 0.005*xk + 0.005*gpr + 0.004*exponential
topic #92: 0.006*bp + 0.005*kikuchi + 0.004*decoding + 0.003*gbp + 0.003*gallager + 0.003*messages + 0.003*lattice + 0.003*bethe + 0.002*xs + 0.002*thermodynamic
topic #93: 0.009*neuron + 0.006*pitch + 0.006*spiking + 0.005*voltage + 0.005*adaptation + 0.005*presynaptic + 0.004*frequency + 0.004*mechanisms + 0.004*periodic + 0.003*channels
topic #94: 0.007*motion + 0.007*diffusion + 0.004*tracking + 0.004*sde + 0.003*cpt + 0.003*walking + 0.003*luettin + 0.002*paths + 0.002*limb + 0.002*cycle
topic #95: 0.000*xq + 0.000*physical + 0.000*noting + 0.000*objects + 0.000*offered + 0.000*offers + 0.000*operates + 0.000*ordinate + 0.000*parallel + 0.000*past
topic #96: 0.003*vc + 0.003*stability + 0.002*zm + 0.002*notations + 0.002*refined + 0.002*zl + 0.002*bousquet + 0.002*covering + 0.002*cedex + 0.002*avenue
topic #97: 0.008*solution + 0.008*distributions + 0.007*ml + 0.006*obtain + 0.005*projection + 0.005*pt + 0.005*upper + 0.005*unsupervised + 0.004*elements + 0.004*generative
topic #98: 0.008*ncut + 0.004*label + 0.004*kgs + 0.003*piecewise + 0.003*bpm + 0.002*pwlz + 0.002*sampler + 0.002*sij + 0.002*wj + 0.002*transduction
topic #99: 0.008*demodulator + 0.007*dogleg + 0.005*subjects + 0.005*tenenbaum + 0.004*bit + 0.003*concept + 0.003*trials + 0.003*trial + 0.003*numbers + 0.003*demodulators
Latent Dirichlet allocation
In natural language processing, latent Dirichlet allocation (LDA) is a generative model that allows sets of observations to be explained by unobserved groups that explain why some parts of the data are similar. For example, if observations are words collected into documents, it posits that each document is a mixture of a small number of topics and that each word's creation is attributable to one of the document's topics. LDA is an example of a topic model and was first presented as a graphical model for topic discovery by David Blei, Andrew Ng, and Michael Jordan in 2003.
Topics in LDA
In LDA, each document may be viewed as a mixture of various topics. This is similar to probabilistic latent semantic analysis (pLSA), except that in LDA the topic distribution is assumed to have a Dirichlet prior. In practice, this results in more reasonable mixtures of topics in a document. It has been noted, however, that the pLSA model is equivalent to the LDA model under a uniform Dirichlet prior distribution.
For example, an LDA model might have topics that can be classified as CAT_related and DOG_related. A topic has probabilities of generating various words, such as milk, meow, and kitten, which can be classified and interpreted by the viewer as "CAT_related". Naturally, the word cat itself will have high probability given this topic. The DOG_related topic likewise has probabilities of generating each word: puppy, bark, and bone might have high probability. Words without special relevance, such as the (see function word), will have roughly even probability between classes (or can be placed into a separate category). A topic is not strongly defined, neither semantically nor epistemologically. It is identified on the basis of supervised labeling and (manual) pruning on the basis of their likelihood of co-occurrence. A lexical word may occur in several topics with a different probability, however, with a different typical set of neighboring words in each topic.
Each document is assumed to be characterized by a particular set of topics. This is akin to the standard bag of words model assumption, and makes the individual words exchangeable.
Model
With plate notation, the dependencies among the many variables can be captured concisely. The boxes are “plates” representing replicates. The outer plate represents documents, while the inner plate represents the repeated choice of topics and words within a document. M denotes the number of documents, N the number of words in a document. Thus:
α is the parameter of the Dirichlet prior on the per-document topic distributions,
β is the parameter of the Dirichlet prior on the per-topic word distribution,
\theta_i is the topic distribution for document i,
\phi_k is the word distribution for topic k,
z_{ij} is the topic for the jth word in document i, and
w_{ij} is the specific word.
The w_{ij} are the only observable variables, and the other variables are latent variables. Mostly, the basic LDA model will be extended to a smoothed version to gain better results .[citation needed] The plate notation is shown on the right, where K denotes the number of topics considered in the model and:
\phi is a K*V (V is the dimension of the vocabulary) Markov matrix each row of which denotes the word distribution of a topic.
The generative process behind is that documents are represented as random mixtures over latent topics, where each topic is characterized by a distribution over words. LDA assumes the following generative process for a corpus D consisting of M documents each of length N_i:
1. Choose \theta_i \, \sim \, \mathrm{Dir}(\alpha) , where i \in \{ 1,\dots,M \} and \mathrm{Dir}(\alpha) is the Dirichlet distribution for parameter \alpha
2. Choose \phi_k \, \sim \, \mathrm{Dir}(\beta) , where k \in \{ 1,\dots,K \}
3. For each of the word positions i, j, where j \in \{ 1,\dots,N_i \} , and i \in \{ 1,\dots,M \}
(a) Choose a topic z_{i,j} \,\sim\, \mathrm{Multinomial}(\theta_i).
(b) Choose a word w_{i,j} \,\sim\, \mathrm{Multinomial}( \phi_{z_{i,j}}) .
(Note that the Multinomial distribution here refers to the Multinomial with only one trial. It is formally equivalent to the categorical distribution.)
The lengths N_i are treated as independent of all the other data generating variables (q and z). The subscript is often dropped, as in the plate diagrams shown here.
Inference
Learning the various distributions (the set of topics, their associated word probabilities, the topic of each word, and the particular topic mixture of each document) is a problem of Bayesian inference. The original paper used a variational Bayes approximation of the posterior distribution;[1] alternative inference techniques use Gibbs sampling and expectation propagation.
Following is the derivation of the equations for collapsed Gibbs sampling, which means \varphis and \thetas will be integrated out. For simplicity, in this derivation the documents are all assumed to have the same length N_{}. The derivation is equally valid if the document lengths vary.
Applications, extensions and similar techniques
Topic modeling is a classic problem in information retrieval. Related models and techniques are, among others, latent semantic indexing, independent component analysis, probabilistic latent semantic indexing, non-negative matrix factorization, and Gamma-Poisson distribution.
The LDA model is highly modular and can therefore be easily extended. The main field of interest is modeling relations between topics. This is achieved by using another distribution on the simplex instead of the Dirichlet. The Correlated Topic Model follows this approach, inducing a correlation structure between topics by using the logistic normal distribution instead of the Dirichlet. Another extension is the hierarchical LDA (hLDA), where topics are joined together in a hierarchy by using the nested Chinese restaurant process. LDA can also be extended to a corpus in which a document includes two types of information (e.g., words and names), as in the LDA-dual model. Nonparametric extensions of LDA include the Hierarchical Dirichlet process mixture model, which allows the number of topics to be unbounded and learnt from data and the Nested Chinese Restaurant Process which allows topics to be arranged in a hierarchy whose structure is learnt from data.
As noted earlier, PLSA is similar to LDA. The LDA model is essentially the Bayesian version of PLSA model. The Bayesian formulation tends to perform better on small datasets because Bayesian methods can avoid overfitting the data. In a very large dataset, the results are probably the same. One difference is that PLSA uses a variable d to represent a document in the training set. So in PLSA, when presented with a document the model hasn't seen before, we fix \Pr(w \mid z)—the probability of words under topics—to be that learned from the training set and use the same EM algorithm to infer \Pr(z \mid d)—the topic distribution under d. Blei argues that this step is cheating because you are essentially refitting the model to the new data.
Variations on LDA have been used to automatically put natural images into categories, such as "bedroom" or "forest", by treating an image as a document, and small patches of the image as words; one of the variations is called Spatial Latent Dirichlet Allocation.
from wiki http://en.wikipedia.org/wiki/Latent_Dirichlet_allocation


Enclosed * by * whitespace
Enclosed ** by ** whitespace
Enclosed _ by _ whitespace
Enclosed __ by __ whitespace


The Strato is a versatile guitar, usable for most styles of music and has been used in many genres, including country, reggae, rock, pop, folk, soul, rhythm and blues, blues, jazz, punk, and heavy metal.
Its typical design features a solid mahogany body with a carved maple top and a single cutaway, a mahogany set-in neck with a rosewood fretboard, two pickups with independent volume and tone controls, and a stoptail bridge, although variants exist.
The original one. Pure.
the world's first commercially successful solid-body electric guitar. Its simple yet effective design and revolutionary sound broke ground and set trends in electric guitar manufacturing and popular music.


Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
REPORTABLE IN THE SUPREME COURT OF INDIA CRIMINAL APPELLATE JURISDICTION CRIMINAL APPEAL NO. 2019 OF 2008 (Arising out of S.L.P. (Crl.) No. 1660 of 2005) U.P. Pollution Control Board .... Appellant (s) Versus Dr. Bhupendra Kumar Modi & Anr. .... Respondent(s) JUDGMENT
P. Sathasivam, J.
1) Leave granted.
2) This appeal is directed against the order dated 29.11.2004 passed in Crl. Misc. Case No. 1347 of 2001 of the High Court of Judicature at Allahabad, Lucknow Bench quashing the Complaint Case No. 44 of 1988 filed by the U.P. Pollution Control Board, Lucknow through its officers against M/s Modi Carpets Ltd. Raebareli and 12 others under Section 44 of the Water (Prevention & Control of Pollution) Act, 1974 (hereinafter referred to as "the Act") pending in the Court of Special Judicial Magistrate (Pollution), Lucknow.
3) Background facts, in a nutshell, are as follows:
The State Board for Prevention and Control of Water Pollution was constituted on 03.02.1975 by the Government of U.P. and it has been named as - U.P. Pollution Control Board (hereinafter referred to as "the Board") which is the appellant herein vide notification No. 2179/9-2-100-74 dated 13.07.1982. On the application submitted by M/s Modi Carpets Ltd., Raebareli, seeking consent to discharge effluent, the appellant-Board granted conditional consent to discharge their trade effluent in the river Sai. Since the conditions of consent were not being complied with by M/s Modi Carpets Ltd., a letter dated 30.4.1983 was sent by the appellant-Board to M/s Modi Carpets Ltd., Raebareli informing that non- compliance of the consent conditions is an offence under Section 44 of the Act. On 07.06.1983, the inspection of unit of M/s Modi Carpets Ltd. was done by the officers of the Board 2 wherein it was found that polluted trade effluent was being discharged into the river Sai through drain without any treatment and construction of effluent treatment plant was yet to be started. On 19.01.1984, the Board again sent a letter to M/s Modi Carpets Ltd. that conditions of the consent order dated 22.1.1983 were not complied with. Again it was reiterated that non-compliance of the conditions of consent would be an offence under Section 44 of the Act. On 13.09.1984, the unit was again inspected by the officers of the Board and it was found that effluent was being discharged without any treatment. For this, Modi Carpets Ltd. sent a reply dated 18.10.1984 to the appellant-Board giving clarifications for not complying with the consent conditions and the same was considered and rejected by the Board on 31.10.1984 on the ground that the unit was not complying with the prescribed standards, consent conditions and also the application was incomplete in various aspects.
4) Since M/s Modi Carpets Ltd. was not complying with the provisions of the Act and there was violation of Sections 25 & 3 26 of the Act, a complaint under Section 44 was filed by the Board through its Assistant Environmental Engineer against respondent No.1 as well as other persons namely, Chairman, Vice-Chairman, Managing Director, Joint Managing Director, Directors, General Manager, Commercial Manager and Company Secretary of M/s Modi Carpets Ltd. before the C.J.M., Raebareli. It was specifically mentioned in the complaint that the aforesaid persons are responsible for the conduct of the business of the company and for their monetary benefits continued to discharge noxious and polluting trade effluent of the company without complying with the conditions of consent and mandatory provisions of law. A petition under Section 482 of the Criminal Procedure Code was filed before the High Court of Judicature at Allahabad being Criminal Misc. Petition No. 14119 of 1985 by M/s Modi Carpets Ltd. & Ors. for quashing the aforesaid complaint and also for other reliefs. Vide order dated 5.11.1985, the High Court stayed further proceedings in the complaint case. On the objection of the Board that the Principal Bench at Allahabad had no territorial jurisdiction to 4 decide the petition, the first respondent herein filed a petition under Section 482 of the Crl.P.C. before Lucknow Bench of the High Court being Crl. Misc. Case No. 1347 of 2001. In the said petition, it was alleged that the first respondent, Dr. Bhupendra Kumar Modi, Joint Managing Director was not concerned with day-to-day business of the company and cannot be prosecuted for the offence committed by the Company, hence, it was prayed that Complaint Case No. 44 of 1988 filed by the appellant-Board be quashed.
5) The appellant-Board filed a counter affidavit before the High Court wherein it was stated that the complaint could not be quashed at the initial stage and whether a person is responsible for conduct of day-to-day business of the Company or not, is a question which has to be decided by evidence. In any event it was stated that the complaint discloses materials to proceed further.
6) By impugned order dated 29.11.2004, the High Court quashed the complaint so far as it related to respondent No.1 on the main ground that there was no material on record to 5 show that respondent No.1 was, at the relevant time, incharge and responsible to the company for conduct of its business. Aggrieved by the said judgment of the Lucknow Bench, the appellant-Board has filed the above appeal by way of special leave.
7) Heard Mr. Rakesh K. Khanna, learned Senior Counsel, appearing for the appellant-Board and Mr. L.N. Rao, learned senior counsel, appearing for the 1st respondent.
8) The only point for consideration in this appeal is whether the complaint of U.P. Pollution Control Board discloses any material against the first respondent i.e., Dr. Bhupendra Kumar Modi, Joint Managing Director, particularly, his control over the decision making process of the Company and whether the High Court was justified in quashing the same in so far as Dr. Bhupendra Kumar Modi in a petition under Section 482 Cr.P.C.
9) The High Court while accepting the case of Dr. Bhupendra Kumar Modi perused the complaint of the Board. According to it, nowhere it is specifically stated in the 6 complaint and there is also no material on record to show that Dr. Bhupendra Kumar Modi was, at the relevant time, in- charge and responsible to the Company for the conduct of the business. The High Court also concluded that there was no specific allegation that at the relevant time, respondent No.1 was in-charge of the Company or was looking after the day-to- day affairs of the company or that the offence has been committed with his consent or connivance. By arriving such conclusion the High Court quashed the prosecution in so far as the first respondent herein is concerned. In the same order, the High Court made it clear that the prosecution is free to proceed against other persons mentioned in the complaint.
10) In order to answer the questions raised, we verified the complaint (Annexure - 8) of the Board laid under Section 44 of the Act. Section 25 (1) of the Act makes it mandatory for every new industry to obtain consent of the "Board" for bringing into use any new or altered outlet for the discharge of its trade effluent into the stream or well or on land as defined in Section 2 of the Act read with its amending Act [Act No. 44 of 7 1978]. The Company and all the persons in-charge of the day- to-day affairs are required to abide by the mandatory provisions for operating their industrial establishment. The complaint further shows that the Company had applied for the grant of consent of the Board for the discharge of its trade effluent on 29.09.1982 which was received by the Board on 04.10.1982 and after considering all aspects the conditional consent order No. 83/170 dated 22.01.1983 was issued in favour of the Company. According to the Complainant, the Company had not sent the report for proper compliance of the condition which was imposed. Accordingly, the site of the Company at Raebareli had been inspected by the officers of the Board on 07.06.1983 and on 13.09.1984 in the presence of representatives of the Company. According to the Board, the accused persons intentionally failed to comply with the conditions of consent order dated 22.01.1983 and to construct proper effluent treatment plant and discharging without consent of the Board. This has been asserted in para 15 of the complaint. In para 16, it is stated that the accused persons, namely, 2-13 are Chairman, Managing 8 Director/Joint Managing Director, Directors, Secretaries and Managers of M/s Modi Carpets Ltd., Raebareli, who are responsible for the conduct of the business of the Company and also for not complying the conditions and for not constructing proper plant for the treatment of their highly polluting trade effluent so as to conform to the standard laid down by the Board. In the same paragraph, it is further asserted that the accused persons are deliberately avoiding the provisions of Section 25 of the Act for which they are punishable under Section 44 read with Section 47 of the Act. In para 17 of the complaint, it is specifically stated that at the time of commission of offence all the persons were in-charge of the business of the Company and responsible for the day-to- day working of the Company and also for conducting of the business of the Company and continuous commissioning of offence under Section 44 of the Act and the construction of effluent treatment plant can be taken up only when these senior authorities resolved to do so. It is further stated that the offence mentioned in the complaint is being continuously committed against the society at large, animals and aquatic 9 life in particular because of their personal monetary gains. In para 21, it is specifically stated that the Chairman, Directors and Secretaries are the brain and nerve centre of Modi Carpets and conducting the business of the Company which has been discharging its trade effluents into stream for which they are to be punished under Section 44 read with Section 47 of the Act. In para 22, it is asserted that under the provisions of Section 47 of the Act where an offence has been committed by a Company every person, who at the time of commission of the offence was in-charge of and responsible to the Company for the conduct of the business shall be deemed to be guilty of the offence and liable to be proceeded and punished accordingly.
11) Apart from the above specific averments, the Board has also placed a letter dated 22.01.1983 granting conditional consent to respondent No.1, copy of the inspection reports, various letters/communications and their reply as Annexures P-1 to P-7.
1 0
12) Among the various provisions of the Act, we are more concerned about Section 47 which speaks about offences by companies which reads thus:
"47. Offences by companies.- (1) Where an offence under this Act has been committed by a company, every person who at the time the offence was committed was in charge of, and was responsible to the company for the conduct of, the business of the company, as well as the company, shall be deemed to be guilty of the offence and shall be liable to be proceeded against and punished accordingly:
Provided that nothing contained in this sub-section shall render any such person liable to any punishment provided in this Act if he proves that the offence was committed without his knowledge or that he exercised all due diligence to prevent the commission of such offence.
(2) Notwithstanding anything contained in sub-section (1), where an offence under this Act has been committed by a company and it is proved that the offence has been committed with the consent or connivance of, or is attributable to any neglect on the part of, any director, manager, secretary or other officer of the company, such director, manager, secretary or other officer shall also be deemed to be guilty of that offence and shall be liable to be proceeded against and punished accordingly.
Explanation.- For the purposes of this section,-
(a) "company" means any body corporate, and includes a firm or other association of individuals; and
(b) "director" in relation to a firm means a partner in the firm."
Section 25 speaks about restrictions on new outlets and new discharges and Section 26 relates to provision regarding existing discharge of sewage or trade effluent. Section 44 1 1 speaks about penalty for contravention of Section 25 or Section 26.
13) It is not in dispute that the first respondent before letting out trade effluent into a stream or a river has to satisfy certain conditions in terms of the provisions of the Act and the order of the authorities concerned. It is also not in dispute that without a consent order by the Board the Company cannot let out untreated effluent into a land or stream or river. Though a consent order was issued by the Board it has been specifically stated in the complaint that those conditions have not been fulfilled by the Company. In those circumstances, in the interest of the public health, the appellant-Board through its officers laid a complaint against the persons, who are in charge of the day-to-day affairs and in the decision making process. There is no need to place all the materials at the threshold. However, on perusal of the complaint and the relevant materials in the form of documents, the learned Special Judicial Magistrate (Pollution) entertained the same and issued summons to the named persons in the complaint. 1 2 Inasmuch as the High Court quashed the complaint against the first respondent herein who is a Joint Managing Director of the Company, we are concerned about the averments/allegations against him in respect of his concern in the day-to-day affairs and in the decision making process. We have already referred to the relevant averments/materials adverted to in the complaint. Before going into the reasoning and conclusion of the High Court for quashing the complaint against the first respondent herein, let us consider various decisions of this Court with reference to the very same provisions, namely, Sections 44 and 47 of the Act as well as the jurisdiction of the High Court under Section 482 of Cr.PC.
14) It is settled legal position that at the stage of issuing process, the Magistrate is mainly concerned with the allegations made in the complaint or the evidence led in support of the same and he is only to be prima facie satisfied whether there are sufficient grounds for proceeding against the accused. In Smt. Nagawwa vs. Veeranna Shivalingappa Konjalgi and Others, (1976) 3 SCC 736, this 1 3 Court has held that it is not the province of the Magistrate to enter into a detailed discussion on the merits or demerits of the case. It was further held that whether a process should be issued, the Magistrate can take into consideration improbabilities appearing on the face of the complaint or in the evidence led by the complainant in support of the allegations. The Magistrate has been given an undoubted discretion in the matter and the discretion has to be judicially exercised by him. It was further held that once the Magistrate has exercised his discretion, it is not for the High Court or even this Court to substitute its own discretion for that of the Magistrate or to examine their case on merits with a view to find out whether or not the allegations in the complaint, if proved, would ultimately end in conviction of the accused. This Court has held that in the following cases, an order of the Magistrate issuing process against the accused can be quashed:
"(1) where the allegations made in the complaint or the statements of the witnesses recorded in support of the same taken at their face value make out absolutely no case against the accused or the complaint does not disclose the essential ingredients of an offence which is alleged against the accused;1 4
(2) where the allegations made in the complaint are patently absurd and inherently improbable so that no prudent person can ever reach a conclusion that there is sufficient ground for proceeding against the accused; (3) where the discretion exercised by the Magistrate in issuing process is capricious and arbitrary having been based either on no evidence or on materials which are wholly irrelevant or inadmissible; and (4) where the complaint suffers from fundamental legal defects, such as, want of sanction, or absence of a complaint by legally competent authority and the like." No doubt the grounds mentioned above are purely illustrative and it provides only guidelines to indicate contingencies where the High Court can quash the proceedings. Though argument was advanced based on the decision in State of Karnataka vs. Pratap Chand and Others, (1981) 2 SCC 335, it was decided in a case relating to conviction under Drugs and Cosmetics Act, 1940 and not quashing of a complaint based merely on a petition or an affidavit. Hence, the said decision is not applicable to the case on hand.
15) Though reliance was placed on a decision of this Court in Municipal Corporation of Delhi vs. Ram Kishan Rohtagi and Others, (1983) 1 SCC 1, a perusal of the said decision makes it clear that the complaint in that case was vague as 1 5 regards the Directors and the Court has concluded that no offence revealed against them, hence the High Court was justified in quashing the proceedings against the Directors.
16) The next decision pressed into service by the first respondent is State of Haryana vs. Brij Lal Mittal and Others, (1998) 5 SCC 343. In the said decision, after finding that except a bald statement in the complaint that the respondents therein were Directors of the manufacturers, there is no other allegation to indicate, even prima facie, that they were in charge of the Company and also responsible to the Company for the conduct of its business. This Court agreed with the High Court in quashing the prosecution against the three Directors.
17) Reliance was also placed on the decision in Nalin Thakor and Others vs. State of Gujarat and Others, (2003) 12 SCC 461. This Court, after finding that there is no allegation as regards the requirement of sub-section (2) of Section 47 and the learned Judicial Magistrate issued 1 6 summons without application of mind, allowed the appeal and set aside the summons issued against the appellants therein.
18) In the earlier part of our order, we have extensively adverted to the specific averments/assertions in the complaint of the Board with reference to all the officers i.e. named persons in the complaint including the first respondent who is Joint Managing Director of the Company. In those circumstances, we are of the view that the above-mentioned decisions relied on by the first respondent are not helpful to the stand taken by him. It is useful to refer the decision in the case of U.P. Pollution Control Board vs Messrs Modi Distillery and Others, (1987) 3 SCC 684. The said case, by special leave, was directed against the judgment and order of the High Court of Allahabad dated 16.05.1984 setting aside, in its revisional jurisdiction, order of the CJM, Ghaziabad dated 03.11.1983 directing issue of process against the respondents therein on a complaint filed by the appellant Pollution Control Board under Section 44 of Water (Prevention and Control of Pollution) Act, 1974. The issue involved therein was whether the Chairman, Vice-Chairman, Managing 1 7 Director and Members of the Board of Directors of M/s Modi Industries Limited, the company owning the industrial unit called M/s Modi Distillery could be proceeded against on a complaint against the said industrial unit. Learned Single Judge of the High Court found that there was no sufficient ground against the respondent inasmuch as the allegations made in the complaint do not constitute an offence punishable under Section 44 for the admitted contravention of Sections 25(1) and 26 read with Section 47 of the Act. The facts narrated above clearly show that the same is identical to the case on hand. This Court taking note of the provisions particularly, Sections 25 (1) (2) and 26 as well as Sections 44 and 47 and the averments in the complaint after finding that prima facie materials are available and all the issues to be dealt with by the Judicial Magistrate at the time of trial, set aside the order of the High Court interfering with the order of CJM directing issue of process to the respondents and directed the learned Magistrate to proceed with the trial in accordance with law. No doubt, it is true that the learned Single Judge of the High Court quashed the proceedings on 1 8 the ground that there could be no vicarious liability saddled on the Chairman, Vice-chairman, Managing Director and other members of the Board of Directors of the Company under Section 47 of the Act unless there was a prosecution of the Company i.e. M/s Modi Industries Ltd. In the case on hand, it is not in dispute that the Company has been shown as first accused in the complaint apart from including Chairman, Managing Director, Jt. Managing Director, General Manager, Directors, General Manager, Commercial Manager and Company Secretary as well as their specific role in the day-to-day affairs and decision making process.
19) U.P. Pollution Control Board vs. Mohan Meakins Ltd. and Others, (2000) 3 SCC 745 is a case filed by the very same appellant- U.P. Pollution Control Board and in similar circumstances this Court interfered with the order of the High Court as well as the order of the Sessions Court quashing the similar complaint. In the said case, the Board initiated proceedings for prosecuting Mohan Meakins Ltd and its Directors for discharging trade effluents in the river Gomti which is a tributary of the Ganga. The learned trial Judge on 1 9 satisfying the averments in the complaint of the Board issued process against the accused at the first instance. The respondents/Company and its Directors desired the trial Court to discharge them without even making their first appearance in the Court. When the attempt made for that failed, they moved for exemption from appearance in the Court. In the meanwhile, the Sessions Judge, Lucknow entertained a revision moved by the accused against the order issuing process to them and quashed it on the erroneous ground that the Magistrate did not pass a speaking order for issuing such summons. The CJM before whom the complaint was filed thereafter passed a detailed order on 25.04.1984 and again issued process to the accused. The order was again challenged by the accused in revision before the Sessions Court and the same Sessions Judge again quashed it by order dated 25.08.1984. The Board moved before the High Court in a revision against the said order. Though the revision was moved in 1984 itself it took 15 years for the High Court to dismiss the revision petition as per the order passed by a learned Single Judge on 27.07.1999. Questioning the same, 2 0 the Board filed special leave petition before this Court and ultimately leave was granted by this Court. It is useful to refer the facts and other details stated in the complaint as noted by this Court. Thomas, J. (as he then was) speaking for the Bench in paras 10 and 11 observed thus:-
10. ... ... ... In the complaint filed by the appellant before the Chief Judicial Magistrate, the Company (M/s Mohan Meakins Ltd.) has been arrayed as the first accused and the other persons who were arrayed as Accused 2 to 10 were described as the Directors of the said Company. The 11th person arrayed in the complaint as accused is described as the Manager of the Company. The averments in the complaint show that the Distillery Unit of the Company at Daliganj, Lucknow, has been discharging noxious trade effluents into River Gomti and causing continuous pollution of the river. It was further averred in the complaint that on 19-9-1982, samples of trade effluents were collected by the officers empowered in this behalf, from the drain "just outside the plant inside the factory", and from the irrigation plant out of which the effluents were pumped into the river. When the samples were analysed in the Industrial Toxicology Research Centre, Lucknow, it was revealed that the quality of effluents was beyond the standard laid down for the purpose. Therefore, it is alleged that the Company has violated Section 24 of the Act* and thereby the Company is guilty of the offence under Section 43 of the Act.
11. Where an offence under the Act has been committed by a company every person who was in charge of and was responsible to the company for the conduct of the business of the company is also made guilty of the offence by the statutory creation. Any director, manager or other officer of the company, who has consented to or connived in the commission of the said offence, is made liable for the punishment of the offence."
This Court has also noted further allegations in the complaint against Managers or Directors of the Company which are as under:-
2 1 "12. In the above context what is to be looked at during the stage of issuing process is whether there are allegations in the complaint by which the Managers or Directors of the Company can also be proceeded against, when the Company is alleged to be guilty of the offence. Para 12 of the complaint reads thus:
"That the accused persons from 2 to 11 are Directors/ Managers/ Partners of M/s Mohan Meakins Distillery, Daliganj, Lucknow, as mentioned in this complaint are responsible for constructing the proper works and plant for the treatment of their highly polluting trade effluent so as to conform to the standard laid down by the Board. Aforesaid accused persons are deliberately avoiding to abide by the provisions of Sections 24 and 26 of the aforesaid Act which are punishable respectively under Sections 43 and 44 of the aforesaid Act, for which not only the Company but its Directors, Managers, Secretary and all other responsible officers of the accused Company, responsible for the conduct of its business are also liable in accordance with the provision of Section 47 of the Act."
The appellant has further stated in para 23 of the complaint that "the Chairman, Managing Directors and Directors of the Company are the persons responsible for the act and therefore, they are liable to be proceeded against according to the law".
Taking note of the averments in the complaint against the Directors, Managers and the ingredients of Section 47 of the Act, this Court declined to accept the reasoning of the High Court and Sessions Court for quashing the complaint thereby set aside both the orders and directed the trial Court to proceed with the case in accordance with law.
20) In the case on hand which is also similar to Mohan Meakins Ltd. had commenced its journey in the year 1985, 2 2 nonetheless lapse of such long period cannot be a reason to absolve the respondents from the trial. In a matter of this nature, particularly, when it affects public health if it is ultimately proved, courts cannot afford to deal lightly with cases involving pollution of air and water. The message must go to all concerned persons whether small or big that the courts will share the parliamentary concern and legislative intent of the Act to check the escalating pollution level and restore the balance of our environment. Those who discharge noxious polluting effluents into streams, rivers or any other water bodies which inflicts on the public health at large, should be dealt with strictly de hors to the technical objections. Since escalating pollution level of our environment affects on the life and health of human beings as well as animals, the courts should not deal with the prosecution for offences under the pollution and environmental Acts in a causal or routine manner.
21) It is our endeavour to point out that the High Court has quashed the complaint arising in an environmental matter in 2 3 a casual manner by exercising power under Section 482 of the Cr.P.C. This Court has held exercise of power under Section 482 of the Code is the exception and under the rule there are three circumstances under which the inherent jurisdiction may be exercised i.e. (a) to give effect to an order of the Court;
(b) to prevent abuse of the process of the Court; (c) to otherwise secure the ends of justice. It is true that it is neither possible nor desirable to lay down any inflexible rule which would govern the exercise of inherent jurisdiction. While exercising inherent powers either on civil or criminal jurisdiction, the Court does not function as a Court of Appeal or Revision. The inherent jurisdiction though wide has to be exercised sparingly, carefully and with caution. It should be exercised to do real and substantial justice and if any attempt is made to abuse that authority so as to produce injustice, the Court has power to prevent abuse. When no offence is disclosed by the complaint, the Court may examine the question of fact. When complaint is sought to be quashed, it is permissible to look into the materials to assess what the complainant had alleged and whether any offence is made out 2 4 even if the allegations are accepted in toto. When exercising jurisdiction under Section 482 of the Code, the High Court could not ordinarily embark upon an enquiry whether the evidence in question is reliable or not or whether on a reasonable appreciation of it accusation would not be sustained. To put it clear, it is the function of the trial Judge to do so. The Court must be careful to see that its decision in exercise of its power is based on sound principles. The inherent power should not be exercised to stifle a legitimate prosecution. If the allegations set out in the complaint do not constitute offence of which cognizance has been taken by the Magistrate, it is open to the High Court to quash the same in exercise of the inherent powers under Section 482 of the Crl. Procedure Code. However, it is not necessary that there should be meticulous analysis of the case before the trial to find out whether the case would end in conviction or acquittal.
22) In the light of the above discussion and in view of the specific averments in the complaint as referred to by us in the earlier paragraphs coupled with the statutory provisions, 2 5 namely, Sections 25, 26, 44 and 47 of the Act, we are unable to share the view expressed by the High Court in quashing the complaint insofar as the first respondent herein. Accordingly, we set aside the same. The Special Judicial Magistrate (Pollution) is directed to proceed with the complaint and dispose of the same in accordance with law. If the first respondent herein applies for dispensing with his personal presence in the Court, after making the first appearance, the Special Court can exempt him from continuing to appear in the Court by imposing any condition which the Court deems fit. Subject to the above observation, we set aside the impugned judgment of the High Court and direct the Special Judicial Magistrate (Pollution) to proceed with the case in accordance with law and dispose of the same as expeditiously as possible. We make it clear that we have not expressed anything on the merits of the contents of the complaint and it is for the Special Court to decide the same in accordance with law. The Criminal appeal is allowed.
........................................CJI. 2 6 (K.G. Balakrishnan) ............................................J. (P. Sathasivam) New Delhi;
December 12, 2008.
2 7


Nicole Coto is a senior in highschool. She has a 4.3 GPA. She does all her work and usually gets A's on all her assignments. Nicole hopes to someday be in the medical field as a veternarian or a nuerologist. She is in multiple clubs but most improtanly she is president of a club name Values Matter. They help out the community including homeless people. She is the best friend of Kayla Gilchrist. They both do everything together most of time and are great people.
Here is her facebook! CLick Here


In this category we show you a group of plans that you must carry out every day to
improve your mental health. The tree will increase its height when you complete some plans and it
will lower when you don't.

When we meditate, we inject far-reaching and long-lasting benefits into our lives: We
lower our stress levels, we get to know our pain, we connect better, we improve our
focus, and we're kinder to ourselves. Let us walk you through the basics in our new
mindful guide on how to meditate.
Practicing the postures, breathing exercises and meditation makes you healthier in body,
mind and spirit. Yoga lets you tune in, chill out, shape up -- all at the same time.


W3C Web of Things
The Web of Things (WoT) seeks to counter the fragmentation of the IoT by using and extending existing, standardized Web technologies. Providing metadata and re-usable technological building blocks, W3C WoT enables easy integration across IoT platforms and application domains.
Working Group
Normative work on deliverables under W3C Patent Policy.
Interest Group
Practical evaluation, exploration, and outreach by W3C Members.
Community Group
Users, stakeholders, and open discussion for everyone.
Getting Started
Learn more through our presentations and whitepaper.
Developers
Implementations, online Things, and tools.
Calls and Meetings
Organizational information and coordination.
News Blog
Official partner organizations.
Liaisons
Official partner organizations.
See anything missing?
If you know of use cases that cannot be achieved today with Web technologies, please let us know!
To that end, you can start a new topic in the Media and Real-Time Communications category of W3C’s discourse forum or raise an issue on the Github repository of this document.