Periodically the scheduler writes a full snapshot of its state to the replicated log. To do this it needs to hold a global storage write lock while it writes out this data. In large clusters this has been observed to take up to 40 seconds. Long pauses can cause issues in the system, including delays in scheduling new tasks.
The scheduler has two optimizations to reduce the size of snapshots and thus improve snapshot performance: compression and deduplication. Most users will want to enable both compression and deduplication.
To reduce the size of the snapshot the DEFLATE algorithm can be applied to the serialized bytes of the snapshot as they are written to the stream. This reduces the total number of bytes that need to be written to the replicated log at the cost of CPU and generally reduces the amount of time a snapshot takes. Most users will want to enable both compression and deduplication.
Snapshot compression is enabled via the -deflate_snapshots
flag. This is the default since
Aurora 0.5.0. All released versions of Aurora can read both compressed and uncompressed snapshots,
so there are no backwards compatibility concerns associated with changing this flag.
Disable compression by passing -deflate_snapshots=false
.
In Aurora 0.6.0 a new snapshot format was introduced. Rather than write one configuration blob per Mesos task this format stores each configuration blob once, and each Mesos task with a pointer to its blob. This format is not backwards compatible with earlier versions of Aurora.
After upgrading Aurora to 0.6.0, enable deduplication with the -deduplicate_snapshots
flag.
After the first snapshot the cluster will be using the deduplicated format to write to the
replicated log. Snapshots are created periodically by the scheduler (according to
the -dlog_snapshot_interval
flag). An administrator can also force a snapshot operation with
aurora_admin snapshot
.
To disable deduplication, for example to rollback to Aurora, restart all of the cluster’s
schedulers with -deduplicate_snapshots=false
and either wait for a snapshot or force one
using aurora_admin snapshot
.


I am a creative React developer who's main goal is to build well designed web applications. These sites are composed of clean code that results in a smooth user experience. I am strongly proficent in utilizing webpack and Redux to improve the performance and scalability of the sites I work on.
Most of my programming career has been spent developing Front-End web applications for construction companies and restaurants. My top priority for these sites is to generate a fluid user experience and currate goals for the site that will appropriately satisfy my customers need.
View ResumeMeet your new robot friends. Robofriends is a Full-Stack web application using the React and Redux libraries. Random robots are generated from an API, you can search for your favorite robot friend and the application will filter the robots as you type.
Smart-Brain utilizes a face recognition web API that will create a box around any face within an image. The application also features users which allows us to see how many times a user has used the face recognition tool.
Lorem ipsum dolor sit, amet consectetur adipisicing elit. Excepturi neque, ipsa animi maiores repellendus distinctio aperiam earum dolor voluptatum consequatur blanditiis inventore debitis fuga numquam voluptate ex architecto itaque molestiae.
Let's build something great!
Reach Out!


| env_clone {rlang} | R Documentation |
This creates a new environment containing exactly the same objects, optionally with a new parent.
env_clone(env, parent = env_parent(env))
env |
An environment. |
parent |
The parent of the cloned environment. |
env <- env(!!! mtcars) clone <- env_clone(env) identical(env, clone) identical(env$cyl, clone$cyl)


Hundreds of years ago, horrifying creatures which resembled humans appeared. These mindless, towering giants, called "titans," proved to be an existential threat, as they preyed on whatever humans they could find in order to satisfy a seemingly unending appetite. Unable to effectively combat the titans, mankind was forced to barricade themselves within large walls surrounding what may very well be humanity's last safe haven in the world.
In the present day, life within the walls has finally found peace, since the residents have not dealt with titans for many years. Eren Yeager, Mikasa Ackerman, and Armin Arlert are three young children who dream of experiencing all that the world has to offer, having grown up hearing stories of the wonders beyond the walls. But when the state of tranquility is suddenly shattered by the attack of a massive 60-meter titan, they quickly learn just how cruel the world can be. On that day, Eren makes a promise to himself that he will do whatever it takes to eradicate every single titan off the face of the Earth, with the hope that one day, humanity will once again be able to live outside the walls without fear.
Comment:
Season 2
For centuries, humanity has been hunted by giant, mysterious predators known as the Titans. Three mighty walls—Wall Maria, Rose, and Sheena—provided peace and protection for humanity for over a hundred years. That peace, however, was shattered when the Colossus Titan and Armored Titan appeared and destroyed the outermost wall, Wall Maria. Forced to retreat behind Wall Rose, humanity waited with bated breath for the Titans to reappear and destroy their safe haven once more.
In Shingeki no Kyojin Season 2, Eren Yeager and others of the 104th Training Corps have just begun to become full members of the Survey Corps. As they ready themselves to face the Titans once again, their preparations are interrupted by the invasion of Wall Rose—but all is not as it seems as more mysteries are unraveled. As the Survey Corps races to save the wall, they uncover more about the invading Titans and the dark secrets of their own members.
Comment:
Season 3
Still threatened by the "Titans" that rob them of their freedom, mankind remains caged inside the two remaining walls. Efforts to eradicate these monsters continue; however, threats arise not only from the Titans beyond the walls, but from the humans within them as well.
After being rescued from the Colossal and Armored Titans, Eren Yaeger devotes himself to improving his Titan form. Krista Lenz struggles to accept the loss of her friend, Captain Levi chooses Eren and his friends to form his new personal squad, and Commander Erwin Smith recovers from his injuries. All seems well for the soldiers, until the government suddenly demands custody of Eren and Krista. The Survey Corps' recent successes have drawn attention, and a familiar face from Levi's past is sent to collect the wanted soldiers. Sought after by the government, Levi and his new squad must evade their adversaries in hopes of keeping Eren and Krista safe.
In Shingeki no Kyojin Season 3, Eren and his fellow soldiers are not only fighting for their survival against the terrifying Titans, but also against the terror of a far more conniving foe: humans.Seeking to restore humanity's diminishing hope, the Survey Corps embark on a mission to retake Wall Maria, where the battle against the merciless "Titans" takes the stage once again.
Returning to the tattered Shiganshina District that was once his home, Eren Yeager and the Corps find the town oddly unoccupied by Titans. Even after the outer gate is plugged, they strangely encounter no opposition. The mission progresses smoothly until Armin Arlert, highly suspicious of the enemy's absence, discovers distressing signs of a potential scheme against them.
Shingeki no Kyojin Season 3 Part 2 follows Eren as he vows to take back everything that was once his. Alongside him, the Survey Corps strive—through countless sacrifices—to carve a path towards victory and uncover the secrets locked away in the Yeager family's basement.
Comment:
Season 4
Gabii Braun and Falco Grice have been training their entire lives to inherit one of the seven titans under Marley's control and aid their nation in eradicating the Eldians on Paradis. However, just as all seems well for the two cadets, their peace is suddenly shaken by the arrival of Eren Yeager and the remaining members of the Survey Corps.
Having finally reached the Yeager family basement and learned about the dark history surrounding the titans, the Survey Corps has at long last found the answer they so desperately fought to uncover. With the truth now in their hands, the group set out for the world beyond the walls.
In Shingeki no Kyojin: The Final Season, two utterly different worlds collide as each party pursues its own agenda in the long-awaited conclusion to Paradis' fight for freedom.


Contributing¶
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
Issue Posting Process¶
Check the Issues before posting to avoid duplication.
Use the Issue Template
Pull Request Process¶
Use the Pull Request Template
2. Increase the version numbers in __init__.py to the new version that this Pull Request would represent. The versioning scheme we use is SemVer. 2. Increase the version numbers in __init__.py to the new version that this Pull Request would represent. The versioning scheme we use is SemVer. 3. You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.


RIVI
RR
Search
About US
Login
Sign Up
1914 translation by H. Rackham
The standard Lorem Ipsum passage, used since the 1500s
Previous
Next
adadsa
asdasd
adadsa
asdasd
adadsa
asdasd
adadsa
asdasd
adadsa
asdasd
adadsa
asdasd


|
| #define | MCAN_PROG_CLK_PRESCALER 1 /* /1 to /256 */ |
| |
| #define | MCAN_PROG_CLK_SELECT PMC_PCK_CSS_MCK |
| |
| #define | MCAN_PROG_CLK_FREQ_HZ ((float) 150000000 / (float) MCAN_PROG_CLK_PRESCALER) |
| |
| #define | MCAN0_BIT_RATE_BPS 500000 |
| |
| #define | MCAN0_PROP_SEG 2 |
| |
| #define | MCAN0_PHASE_SEG1 11 |
| |
| #define | MCAN0_PHASE_SEG2 11 |
| |
| #define | MCAN0_SYNC_JUMP 4 |
| |
| #define | MCAN0_FAST_BIT_RATE_BPS 2000000 |
| |
| #define | MCAN0_FAST_PROP_SEG 2 |
| |
| #define | MCAN0_FAST_PHASE_SEG1 4 |
| |
| #define | MCAN0_FAST_PHASE_SEG2 4 |
| |
| #define | MCAN0_FAST_SYNC_JUMP 2 |
| |
| #define | MCAN0_NMBR_STD_FLTS 8 /* 128 max filters */ |
| |
| #define | MCAN0_NMBR_EXT_FLTS 8 /* 64 max filters */ |
| |
| #define | MCAN0_NMBR_RX_FIFO0_ELMTS 0 /* # of elements, 64 elements max */ |
| |
| #define | MCAN0_NMBR_RX_FIFO1_ELMTS 0 /* # of elements, 64 elements max */ |
| |
| #define | MCAN0_NMBR_RX_DED_BUF_ELMTS 16 /* # of elements, 64 elements max */ |
| |
| #define | MCAN0_NMBR_TX_EVT_FIFO_ELMTS 0 /* # of elements, 32 elements max */ |
| |
| #define | MCAN0_NMBR_TX_DED_BUF_ELMTS 4 /* # of elements, 32 elements max */ |
| |
| #define | MCAN0_NMBR_TX_FIFO_Q_ELMTS 0 /* # of elements, 32 elements max */ |
| |
| #define | MCAN0_RX_FIFO0_ELMT_SZ 8 /* 8, 12, 16, 20, 24, 32, 48, 64 bytes */ |
| |
| #define | MCAN0_RX_FIFO1_ELMT_SZ 8 /* 8, 12, 16, 20, 24, 32, 48, 64 bytes */ |
| |
| #define | MCAN0_RX_BUF_ELMT_SZ 8 /* 8, 12, 16, 20, 24, 32, 48, 64 bytes */ |
| |
| #define | MCAN0_TX_BUF_ELMT_SZ 8 /* 8, 12, 16, 20, 24, 32, 48, 64 bytes */ |
| |
| #define | MCAN1_BIT_RATE_BPS 500000 |
| |
| #define | MCAN1_PROP_SEG 2 |
| |
| #define | MCAN1_PHASE_SEG1 11 |
| |
| #define | MCAN1_PHASE_SEG2 11 |
| |
| #define | MCAN1_SYNC_JUMP 4 |
| |
| #define | MCAN1_FAST_BIT_RATE_BPS 2000000 |
| |
| #define | MCAN1_FAST_PROP_SEG 2 |
| |
| #define | MCAN1_FAST_PHASE_SEG1 4 |
| |
| #define | MCAN1_FAST_PHASE_SEG2 4 |
| |
| #define | MCAN1_FAST_SYNC_JUMP 2 |
| |
| #define | MCAN1_NMBR_STD_FLTS 8 /* 128 max filters */ |
| |
| #define | MCAN1_NMBR_EXT_FLTS 8 /* 64 max filters */ |
| |
| #define | MCAN1_NMBR_RX_FIFO0_ELMTS 12 /* # of elements, 64 elements max */ |
| |
| #define | MCAN1_NMBR_RX_FIFO1_ELMTS 0 /* # of elements, 64 elements max */ |
| |
| #define | MCAN1_NMBR_RX_DED_BUF_ELMTS 4 /* # of elements, 64 elements max */ |
| |
| #define | MCAN1_NMBR_TX_EVT_FIFO_ELMTS 0 /* # of elements, 32 elements max */ |
| |
| #define | MCAN1_NMBR_TX_DED_BUF_ELMTS 4 /* # of elements, 32 elements max */ |
| |
| #define | MCAN1_NMBR_TX_FIFO_Q_ELMTS 4 /* # of elements, 32 elements max */ |
| |
| #define | MCAN1_RX_FIFO0_ELMT_SZ 8 /* 8, 12, 16, 20, 24, 32, 48, 64 bytes */ |
| |
| #define | MCAN1_RX_FIFO1_ELMT_SZ 8 /* 8, 12, 16, 20, 24, 32, 48, 64 bytes */ |
| |
| #define | MCAN1_RX_BUF_ELMT_SZ 64 /* 8, 12, 16, 20, 24, 32, 48, 64 bytes */ |
| |
| #define | MCAN1_TX_BUF_ELMT_SZ 32 /* 8, 12, 16, 20, 24, 32, 48, 64 bytes */ |
| |
Purpose
Interface for configuring and using Timer Counter (TC) peripherals.
Usage
- Optionally, use TC_FindMckDivisor() to let the program find the best TCCLKS field value automatically.
- Configure a Timer Counter in the desired mode using TC_Configure().
- Start or stop the timer clock using TC_Start() and TC_Stop().


| fkSegments reference pages |
[overlap,rel1,rel2]=SEG_OVERLAP(a) [overlap,rel1,rel2]=SEG_OVERLAP(a,b)
[overlap,rel1,rel2]=SEG_OVERLAP(a) returns the absolute overlap and overlap fraction (relative to length of first or second segment) between all combinations of segments in a.
[overlap,rel1,rel2]=SEG_OVERLAP(a,b) returns the absolute overlap and overlap fraction (relative to length of first or second segment) between all combinations of segments in a and b.
| seg_and | Toolbox page | seg_sort |


header section
This is a heading
paragraph section
This is a paragraph.
Note:
Play with the margin property value to see how it works.


| Name |
Type |
Description |
| anchorPoint |
object |
a dictionary with properties x and y to indicate the anchor point value. anchor specifies the position by which animation should occur. center is 0.5, 0.5 |
| backgroundColor |
string |
value of the background color of the field |
| backgroundImage |
string |
the background image url of the view |
| borderColor |
string |
the border color of the view |
| borderRadius |
float |
the border radius of the view |
| borderWidth |
float |
the border width of the view |
| bottom |
float,string |
property for the view bottom position. this position is relative to the views parent. can be either a float value or a string of the width. |
| center |
object |
a dictionary with properties x and y to indicate the center of the views position relative to the parent view |
| editable |
boolean |
boolean indicating if the field is editable |
| enabled |
boolean |
boolean indicating the enabled state of the field |
| height |
float,string |
property for the view height. can be either float value or a string of the width. |
| keyboardToolbar |
array |
array of toolbar button objects to be used when the keyboard is displayed |
| keyboardToolbarColor |
string |
the color of the keyboard toolbar |
| keyboardToolbarHeight |
float |
the height of the keyboard toolbar |
| left |
float,string |
property for the view left position. this position is relative to the views parent. can be either a float value or a string of the width. |
| opacity |
float |
the opacity from 0.0-1.0 |
| right |
float,string |
property for the view right position. this position is relative to the views parent. can be either a float value or a string of the width. |
| size |
object |
the size of the view as a dictionary of width and height properties |
| top |
float,string |
property for the view top position. this position is relative to the views parent. can be either a float value or a string of the width. |
| touchEnabled |
boolean |
a boolean indicating if the view should receive touch events (true, default) or forward them to peers (false) |
| transform |
object |
the transformation matrix to apply to the view |
| value |
string |
value of the field |
| visible |
boolean |
a boolean of the visibility of the view |
| width |
float,string |
property for the view width. can either be `auto`, a float value or a string of the width. |
| zIndex |
int |
the z index position relative to other sibling views |
| Name |
Description |
| blur |
fired when the field loses focus
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| value | the value of the field upon blur |
|
| change |
fired when the field value changes
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| value | the value of the field upon change |
|
| click |
fired when the device detects a click (longer than touch) against the view
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| dblclick |
fired when the device detects a double click against the view
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| doubletap |
fired when the device detects a double tap against the view
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| focus |
fired when the field gains focus
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| value | the value of the field upon focus |
|
| return |
fired when the field return key is pressed on the keyboard
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| value | the value of the field upon return |
|
| selected |
fired when the text in the field is selected
Event properties
| range | the range of text. range is an object with the properties location and length. |
| source | the source object that fired the event |
| type | the name of the event fired |
|
| singletap |
fired when the device detects a single tap against the view
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| swipe |
fired when the device detects a swipe (left or right) against the view
Event properties
| direction | direction of the swipe - either left or right |
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| touchcancel |
fired when a touch event is interrupted by the device. this happens in circumenstances such as an incoming call to allow the UI to clean up state.
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| touchend |
fired when a touch event is completed
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| touchmove |
fired as soon as the device detects a movement of a touch
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| touchstart |
fired as soon as the device detects a gesture
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
| twofingertap |
fired when the device detects a two-finger tap against the view
Event properties
| source | the source object that fired the event |
| type | the name of the event fired |
| x | the x point of the event |
| y | the y point of the event |
|
This example created a highly customized text area.
var ta1 = Titanium.UI.createTextArea({
value:'I am a textarea',
height:70,
width:300,
top:60,
font:{fontSize:20,fontFamily:'Marker Felt', fontWeight:'bold'},
color:'#888',
textAlign:'left',
appearance:Titanium.UI.KEYBOARD_APPEARANCE_ALERT,

keyboardType:Titanium.UI.KEYBOARD_NUMBERS_PUNCTUATION,
returnKeyType:Titanium.UI.RETURNKEY_EMERGENCY_CALL,
borderWidth:2,
borderColor:'#bbb',
borderRadius:5
});
Both Text Areas and Text Fields can control the buttons displayed in a button bar above the keyboard when it's visible.
var textfield = Titanium.UI.createTextField({
color:'#336699',
value:'Focus to see keyboard w/ toolbar',
height:35,
width:300,
top:10,
borderStyle:Titanium.UI.INPUT_BORDERSTYLE_ROUNDED,
keyboardToolbar:[flexSpace,camera, flexSpace,tf,flexSpace, send,flexSpace],
keyboardToolbarColor: '#999',

keyboardToolbarHeight: 40,
});


---
layout: page
---
I am a first year Computer Science PhD. student with
Dr. Pierre-Luc Bacon at the University of Montreal and
Montreal Institute of Learning Algorithms, Mila. Previously, I was a research intern at
NNAISENSE, working at the intersection of control theory,
robotics and deep learning.
I recently graduated from ETH Zurich, with a
MSc. in Robotics, Systems and Control. I did my masters thesis with Dr. Andreas Krause
in the domain of safe policy search in high-dimensional spaces. I also worked on safe and efficient
reinforcement learning algorithms for constrained dynamical systems with Dr. Melanie Zeilinger.
I received a Bachelor of Science in Electrical Engineering from Georgia Institute of Technology with a
minor in Robotics. During my bachelors, I was a Teaching Assistant for Differential equations and a
Research Assistant with the Georgia Tech Systems Lab under Dr. Fumin Zhang. I spent three months as a
visiting student researcher in the Autonomous Systems Lab at ETH, through the
ThinkSwiss Research Scholarship.
At Georgia Tech, I completed three rotations of Robotics and Image Processing co-op at the
Food Processing Technology Division under
Georgia Tech Research Institute, where I developed autonomy algorithms for a robotic system
to monitor chickens in a poultry grow-out house.
When I'm not working with robots and computers, I love reading, hiking and
painting!
Best way to reach me is through email.


Trianz - Model Placement Paper
1. Lucia is a wonderful grandmother. Her age is between 50 and 70.Each of her sons have as many sons as they have brothers. Their combined number gives Lucia?s age. What is the age?
Ans: 64
2.There are two towers A and B. Their heights are 200ft and 150ft respectively and the foot of the towers are 250ft apart. Two birds on top of each tower fly down with the same speed and meet at the same instant on the ground to pick a grain. What is the distance between the foot of tower A and the grain?
Ans:90ft
3. There is a church tower 150 feet tall and another catholic tower at a distance of 350 feet from it which is 200 feet tall. There is one each bird sitting on top of both the towers. They fly at a constant speed and time to reach a grain in b/w the towers at the same time. At what distance from the church is the grain?
Ans: 90
4. A person wants to meet a lawyer and as that lawyer is busy he asks him to come three days after the before day of the day after tomorrow? on which day the lawyer asks the person to come?
Ans: thursday
5. Grass in lawn grows equally thick and in a uniform rate. It takes 40 days for 40 cows and 60 days for 30 cows to eat the whole of the grass. How many days does it take for 20 cows to do the same?
Ans: 120
6. A person is 80 years old in 490 and only 70 years old in 500 in which year is he born?
Ans: 470
7.Raju having some coins want to distribute to his 5 son , 5 daughter and driver in a manner that , he gave fist coin to driver and 1/5 of remaining to first son he again gave one to driver and 1/5 to 2nd son and so on.... at last he equally distributed all the coins to 5 daughters. how many coins raju initially have???
Ans:-881
8.if ravi binded his book and the binder cut the pages of the book , ravi decided to mark the pages by himself own , what he found that number of three appears 61 times find of number of pages answer
ans - 300
9. There are 10 Red, 10 Blue, 10 Green, 10 Yellow, 10 White balls in a bag.  He did not want anybody to know about them. One day, his wife asked, "How many gold coins do we have?" After pausing a moment, he replied, "Well! If I divide the coins into two unequal numbers, then 37 times the difference between the two numbers equals the difference between the squares of the two numbers." The wife looked puzzled. Can you help the merchant's wife by finding out how many gold R
Ans:37
11. There is a 5digit no. 3 pairs of sum is eleven each. Last digit is 3 times the first one. 3 rd digit is 3 less than the second.4 th digit is 4 more than the second one. Find the digit.
Ans : 25296.
12. Every day a cyclist meets a train at a particular crossing. The road is straight before the crossing and both are traveling in the same direction. The cyclist travels with a speed of 10 Kmph. One day the cyclist comes late by 25 min. and meets the train 5km before the crossing. What is the speed of the train?
Ans: 60 kmph
13. Output of the following program is
main()
{ int i=0;
for(i=0;i<20;i++)
{ switch(i)
case 0:i+=5;
case 1:i+=2;
case 5:i+=5;
default i+=4;
break;}
printf("%d,",i);
}
}
main()
{ char c=-64;
int i=-32
unsigned int u =-16;
if(c>i)
{ printf("pass1,");
if(c
printf("pass2");
else
printf("Fail2");
}
else
printf("Fail1);
if(i
printf("pass2");
else
printf("Fail2")
}


What can you do with Vicki?
Play music on your computer and control it through Alexa. Start a game or app before you get to your desk. Shutdown the computer from the comfort of your bed. Do a PowerPoint presentation and have Alexa change the slides for you. Have Alexa read aloud an article from a web page while you walk away from the screen. Lock your computer before someone else messes with it. Open that recipe you have bookmarked while you are in the middle of cooking. Navigate the Internet hands free because your hands are occupied. Dictate your next bestseller and have Alexa scribe it for you. Level up your routine by voice activating it through Alexa.
Extend Vicki with user created scripts and control any website or software through Alexa.
Write scripts to answer requests from Alexa on your browser. Here is an example.
/// ==VickiScript==
/// @name Hello World
/// @utterance Tell $invocation hello
/// ==/VickiScript==
$vs.listen(/^hello$/, async (request, response) => {
// A alexa request with utterance "hello" came in!
// Open hello world wiki page on a new tab.
const url = "https://en.wikipedia.org/wiki/%22Hello,_World!%22_program";
await browser.tabs.create({ url });
// Make Alexa say "Hello World"
response.say("Hello World").send();
});
See the Developer Guide to start developing.
1) How safe is this?
Here are the key things you should be aware of:
See technical details on security
2) Can I control multiple computers?
Yes, however each Alexa input device (echo) can only communicate with a single computer at a time. To set the preferred target computer say "Alexa, ask web browser to set my preferred vicki" and it will list all connected computers by a name. The name of each computer is listed inside the browser extension's pop up.
3) Can I control my computer from multiple echos?
Yes, when you attempt to use your 2nd echo the computer will prompt you to add the echo as a trusted device.
For any bugs or feature request, use the GitHub issues page.
For private communication, contact pavel@heyvicki.net.


Given a Skiplist, draw the search path for a given element.
Find the search path for a given element!
- Drag your mouse over the next element to add it to the search path.
- When finished, click the element to check your answer!
- Press the down arrow to move down
- Press the right arrow to move right
- Press enter to check your search path


Home
Projects
Project: ASCENSION
D
U
W
Bukkit Projects
A
U
Journey
D
W
WWT
D
W
Dependencies
Web Widget Toolkit
Dependents
Ascension: Preamble
Description
A single-file script to aid in the look and feel of a browser game. Used by Ascension: Preamble. Requires WWT
Labels
Demos Available
Work in Progress
Languages
CoffeeScript
HTML
Sass
Platforms
Browser
CommonJS


A prompt is a piece of text given as input to an AI model to generate a specific response. In the context of ChatGPT, a prompt is entered by the user and then used by the model to generate a response. The prompt can be a question, sentence, or a few words that help the model understand the context and desired outcome.
Prompt presets are pre-made text inputs that can be presented to a ChatGPT model to generate a specific type of responses. These presets can help to make ChatGPT respond in a certain way and provide specific answers. Prompt presets can, for example, be used to generate questions on a specific topic or to use a certain style or language. The use of prompt presets allows for targeted control and influence over the results of ChatGPT.
Context:
This refers to the information that the user should include in the question to help the chatbot better understand the context of the question and thus generate a more accurate answer. An example of context could be: "I tried to book a flight but the website keeps giving me an error message."Topic:
The topic describes the general subject or category of the question or problem. In relation to the context mentioned above, the topic for this question could be "Travel and flight booking."Length:
Length indicates whether the response from ChatGPT should be short, detailed or extensive.For a short answer, ChatGPT will try to answer the question with as few words as possible. The short answer may not fully answer the question.
For a detailed answer, ChatGPT will try to answer the question as detailed as possible.
For an extensive answer, ChatGPT will try to generate an answer using all known information related to the question. This may include displaying irrelevant information.


Yanik Koch
Q1) What is the general perception of India in your home country? Are those perceptions correct? In
your opinion, what are India's greatest strengths?
- We perceive India as a poor country, with a very bad economy. But after coming here, I
realised that the poverty here is same as in any other country, say my own for that matter.
- My folks believe India to be dangerous. This is one of the reasons my parents were unwilling
to send me here, and said that they would rather that I do not go for exchange. However,
now that I have experienced the actual environment here, I would say that I never once felt
unsecure during my stay. Even most of the strangers were friendly and readily helped me.
Now I feel safe even when I go out at night.
Q2) Has your experience here helped you gain an appreciation of how the world is interconnected
on all levels (environmental, socio-cultural and geopolitical)? If so, can you cite specific examples?
- Everyone is open minded and not interested in your religion, but rather they want to
connect with you on the basis of common activities and hobbies that you share.
- The behaviour of Indians is akin to Germans, as they are always ready to help out someone
in need.
- Most of the packaged products and food items available here are similar to other countries.
Q3) In your opinion, what are India's greatest strengths?
People here are friendly, good natured and open minded.
Q4) What are the biggest differences you see between the college experience here and in your
home country?
The biggest difference I want to point out is that in India, there is a very strict attendance policy,
which serves no purpose for either the students or the professors, and is rather counter intuitive.
There are way too many minors and assignments we get. This puts unnecessary pressure on us and
encourages rote learning.
Q5) What do you like the most/the least about India? What do you miss the most about your home
country?
- Indian’s are friendly and good natured people. They are well informed both on national and
international issue, and are a great source of trivia. Indian’s are really passionate about
developing their country and making it proud, which reflects in the hard work they put in.
- There are not many trees in India, and the vegetation is sparsely distributed. For example, in
Germany we have a long stretch of woods with different kinds of trees, which provides a
relaxing view as well as recreational benefits.


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface Sort
Sort, a type of Query
, provides for specifying and chaining the query predicates. The results of the sort directive are returned
as an ordered List
of byte[]
values.
Sort instances are obtained directly from the JRedis
client, by calling the eponymous method JRedis.sort(String)
, which expects
a key name as its required arguments.
[Note: this provides the pattern for all future query types: required args are specified in the method that returns the Query
form.]
As with all Query
forms,
do not forget to call Query.exec()
at the end!
Usage:
List
Sort specification elements are all optional. You could simply say:
List
Sort specification elements are also can appear in any order -- the client implementation will send them to the server in the order expected by the protocol, although it is good form to specify the predicates in natural order:
List
| Method Summary | |
|---|---|
Sort |
ALPHA()
sort is be default numeric -- use this to indicate lexiographic alphanumeric sort |
Sort |
BY(java.lang.String pattern)
species the BY clause |
Sort |
DESC()
default sort is ASCending -- use this in your sort to specify DESC sort |
Sort |
GET(java.lang.String pattern)
specifies the GET clause |
Sort |
LIMIT(long from,
long count)
specifies the LIMIT class: from is the intial index, count is the number of results |
| Methods inherited from interface org.jredis.Query |
|---|
exec |
| Method Detail |
|---|
Sort BY(java.lang.String pattern)
Sort GET(java.lang.String pattern)
Sort LIMIT(long from, long count)
Sort DESC()
Sort ALPHA()
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Home
About
Contact
Portfolio
▼
To-do App
Stylist
Quiz
Drop me a word or two
Full name:
Email:
Company:
Message:
Or find me at the following social medias


First we will discuss the sentiment rating scale and then the annotation process.
1) Sentiment Rating Scale and Examples
1.1 - The Scale
The Sentiment Rating tool has a scale that ranges from -100 to 100 (negative to positive sentiment).
To facilitate annotation, there are also seven (7) main Steps on the scale. These Steps are displayed on the tool itself.
Each Step corresponds to a certain score on the -100 – 100 scale:
| Step | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| Score | -95 | -64 | -34 | 0 | 34 | 64 | 95 |
| ← More Negative | Neutral | More Positive → |
As you can see, the lowest and highest score you can give using using the 7-step scale is -95 (1) and 95 (7) respectively.
You can use the mouse or the keyboard arrow keys (← and →) to adjust it to the maximum on either side (-100, or 100).
In most cases, the 7-step scale should be enough for your sentiment annotation task, and you will not need to make fine adjustments.
1.2 - Some Examples
The table below shows some examples and the score/rating that might be assigned to them.| Score | Step | Example | From corpus | Compositional |
|---|---|---|---|---|
| 95 | 7 | fantastic | perfect, splendidly | very good |
| 64 | 6 | good | soothing, pleasure | |
| 34 | 5 | ok | easy, interesting | sort of good, not bad |
| 0 | 4 | bread | puff, dig, top-knot | sliced bread |
| -34 | 3 | poor | rumour, cripple | kind of bad, not good |
| -64 | 2 | bad | hideous, death | |
| -95 | 1 | awful | deadly, foul play, horror-stricken | very bad |
The compositional examples are for illustrative purposes, this guide does not show you how to tag chunks consisting of multiple concepts.
2) Sentiment Annotation
This section will walk you through the process of using the sentiment rating tool.
This guide assumes you already know how to log-in and that you are familiar with the general layout of the annotation interface.
You can check out the annotation Quick Start Guide for Projects 1 and 2 for a refresher.
2.1 - Preliminaries (What Should Be Done)
You need to annotate words in the text for their sentiment. You will determine whether a word is positive or negative (polarity), to what degree it is positive or negative (magnitude), and thereafter give it a sentiment score/rating.
Unlike sense tagging, you do not have to annotate every word. Most words are neutral for sentiment.
What should be annotated for sentiment?
- You should annotate concepts that show clear positive or negative sentiment, such as:
- Happy, sad, angry
- These can include multi-word expressions (MWE):
- fed up
- break down
- As with sense tagging, you should give the sentiment rating to the MWE (More Info)
- You should not tag modifiers such as very, not, etc
- The remaining words should be left as-is
Other points to take note:
- The sentiment score/rating should be based on the concept used to tag that word
- It will be useful to look at, and base your decision on, the definition and example(s) of the concept (ie, synset)
- Your annotation should be context independent
- As with sense annotating, do not overthink!
- Make use of the Comments box.
2.2 - Annotating
- To begin, click on the word you wish to annotate for sentiment.
- The word will be highlighted in yellow, and its available senses loaded on the right panel.
- This should already be familiar to all of you who have worked on Projects 1 and 2.
- Unlike in previous projects, we will be using the Sentiment Rating tool towards the bottom of the screen, as illustrated below:
- The Rating tool contains seven (7) main Steps, for scores ranging from -100 to 100.
- 1 being Very Negative
- 7 being Very Positive
- 4 being Neutral
- The other numbers {2, 3; 5, 6} being of lesser magnitudes than their extremes
- There are two ways to set the sentiment score:
- Using the keyboard, press Z + [Step Number] and the tool's meter will be changed accordingly. (Eg: To give it a rating of 3, press Z + 3 on the keyboard)
- Using the mouse, drag the meter's slider to where you want it to be
- We recommend using the keyboard for coarser ratings, and then adjusting using the mouse for finer sentiment.*
- (Alternatively, the ← and → keys can also be used for fine adjustments. You need to click on the slider — to bring it into focus — before you can use the arrow keys)
* In most cases, the 7-step scale should be enough for your sentiment annotation task, and you will not need to make fine adjustments.
- As illustrated above, I have selected malodorous to rate for sentiment. It is a negative word, and so I choose to give it a rating of 2.
To do this, I press Z + 2 on the keyboard.
The sentiment rating tool's slider shifts accordingly to 2: - The rating is automatically saved.
- A confirmation message (The sentiment score of the concept [# (sid:#####)] was updated to -64 by USERNAME) should appear at the bottom of the interface to indicate the rating was performed successfully.
- The number indicated in the confirmation message is the numerical score, not the Step. (Find out more about the sentiment scale)
- In the text, the rating is reflected for malodorous, and it now has a red underline below its normal underline, like so: malodorous
- You will have to click on another word to see the second underline (for sentiment).
- Let's take a look at another word: friend
- Friend is a rather positive word, and should therefore be given a rather positive rating.
- Let's give it a rating of 5.
- To do this, I press Z + 5 on the keyboard.
- The slider shifts accordingly:
- Again, a confirmation message should appear at the bottom of the interface to indicate the rating was performed successfully.
- In the text, the sentiment rating is reflected for friend, and it now has a green underline below its normal underline, like so: friend
NOTE: Words which were tagged as "x" will not have a Sentiment Rating tool.
See Sentiment Scale and Examples for more information on the scale and some example words and their ratings.
If, by accident, you gave a sentiment rating to a word that should not have a sentiment, you can reset it by changing its sentiment rating to Neutral (4) by pressing Z + 4 on your keyboard.
Avoid using the mouse to drag the slider when neutral-ising.
Neutral-ised words will no longer have the second underline.
Multi-word Expressions?
A Multi-word Expression (MWE) should be tagged as a whole for sentiment.
If you have previously tagged the individual words in an MWE with "x" (as you should!) then only the MWE itself would have a Sentiment Rating tool available for it, as shown below:
As you can see, the MWE as good as one's word is the only one with a Sentiment Rating tool. The smaller parts of the MWE (good and good word) were correctly tagged with "x".
If you see multiple Sentiment Rating tools, then it is likely the individual words or phrases within an MWE were not tagged as "x" during sense-tagging.
Fix this by retagging these smaller components with "x" (see the sense tagging Quick Start Guide on what to do for MWEs, if you need a refresher).
References:
- Francis Bond, Tomoko Ohkuma, Luis Morgado da Costa, Yasuhide Miura, Rachel Chen, Takayuki Kuribayashi, and Wenjie Wang (2016) A multilingual sentiment corpus for Chinese, English and Japanese. In Proceedings of the LREC 2016 Workshop “Emotion and Sentiment Analysis”, Portorož. pp 59–62
- Francis Bond, Arkadiusz Janz and Maciej Piasecki (2019) A Comparison of Sense-level Sentiment Scores Proceedings of the 10th Global Wordnet Conference pp 363–372


WordiZ Weekly – 15 September 2013
15/Sep 2013
As every Sunday, we’ll share the articles we enjoyed reading about content marketing, blogging or inbound marketing. If you miss one of them during the week, now you have time to read the most important post of the week. This time we share articles about the Content Marketing World 2013, a list of 10 content leaders, advices on how to create quality content and a recipe for your future inbound strategy.
Happy social reading and** be active** and leave a comment.
Creating an inbound marketing strategy
by Luke Summerfield (September 11th 2013)
Luke writes a very complete review about how to plan and set up a very efficient inbound marketing strategy to attract and convert visitors into clients. He talks about buyer personnas, the customer buying cycle how to funnel your visitors through different steps and finally how to improve your SEO. It is the article you should have read this week.
What Exactly Does Google Consider High Quality Marketing Content?
by Bill Faeth (September 5th 2013)
When you start writing a piece of content you need to think of your readers in the first place but also to search engines like Google or Bing. Here Bill explains how we can create quality content both for humans and Google. A great resource for those who care about SEO when doing content creation.
10 Leaders Changing The Content Landscape
by John Hall (September 8th 2013)
Content creation landscape can be very fuzzy and finding influencers out there is not a trivial task. That is what we aim for at WordiZ, but before opening our beta to the world we should mention this very interesting piece of writing from John Hall for Forbes.
He lists 10 major leaders in the world of content creation including LinkedIn, HubSpot, American Express or The Huffington Post among others. An original post that is worth reading to get ideas.
Content Marketing World 2013 Wrap-Up
by Devin Harper (September 5th 2013)
Last week in Cleveland Ohio, a very important meeting for content marketer was live : the Content Marketing World 2013. Devin writes here a very nice review about these three days of event, full with inspiring talks.


Seedbit is a Proof of Stake Cryptocurrency. The first couple of days after release will consist of Proof of Work period.
Coin Generation: Pure Proof of Stake with Proof of Work period on release
Proof of Work Algorithm: Quark
PoW Block Reward: 1000 SED reducing to 0
PoW Blocks: 3000
PoW Target Blocktime: 90 seconds
RPC Port: 25581
Port: 25579
Time to Maturity: 80 Confirmations
Proof of Stake Reward: 50 per block initially, reducing to 0.1 SED + 1% pa per block
Minimum Coin Stake Age: 3 - 24 hours


Your privacy is very important to us, especially when it is related to the clipboard service which might be one of the most private services on your devices. So we started thinking about how we can make it right at the very beginning of design and development time. Thanks to the open technologies like UIkit and pioneer companies like Apple, we've got a better solution: We do not collect, use, disclose, transfer or store any of your data on our servers.
Data Backend
Copies service is based on macOS, and it is accessible through the web on other platforms. In order to make the service robust while not compromising on privacy information, we use CloudKit as the only backend which is not only the technology that powers many of Apple's own cloud services but also a service already trusted by millions of customers. You sign in with Apple ID to start, sign out to stop. Since we do not store any of your data, as long as you keep the iCloud account in safe place, your data is well protected.
Data Transfer
We use the latest SSL/TLS encryption for all the information that is being transmitted, to make sure data transfer is safe.
Website Cookie
When you use Copies on the web, the browser will save the successful sign-in session as secure cookies on the device. This kind of cookie is safe, however you can disable and delete it at any time in browser settings.
Last modified: 30th Nov, 2016


I left school at the age of 16 to pursue what I wanted to do in life. I had ambitious dreams. But throughout the years I learnt to be conscious of my naivety and ignorance. I understand that it is perfectly normal if it turns out that all this time I have been living in a delusional state. So far every project I started had failed. Things have not once gone as planned.
 So I was greatly surprised when I learnt that 30 thousand people had visited my website in a day because of something I wrote. The link to the essay had got good number of upvotes on both Reddit and HackerNews. Some commented and told me it was good. Certainly this was nothing comparing to, say, getting into MIT, but I think I had never been this happy in my life before. The joy I felt - that could not be described in words.
Once again, thank you all for the support.  And with a positive mind, gradually, I made the decision to be less of a shut-in and start going for meet-ups and conferences. I got to know many cool people and made some new friends.
At the moment I’m busy with a couple of projects. I’m still reading up on general topology and working on the essay, 0a explains: general topology. At some point in time I decided to have set theory, one of its segments initially, to be in a separate essay instead. And just to make things more interesting, I figured I should dive in a bit deeper and give an axiomatic view for some of the concepts.
So here it is. Enjoy!
Prologue for 0a explains: Set Theory and Axiomatic Systems
by Archy
The artwork is Untitled (Lettres) by Moon-Pil Shim, 1998.


Alone with Death is a post apocalyptic zombie top-down view shooter.
In action mode your purpose is to survive from 5 waves of zombies. With each wave zombies become stronger and faster than other one. At start Player has only a pistol and some ammo. From time to time there will be generated more different guns and ammo.
(In development) Also called "relax mode", where you are given an open world with full free of action. Player has 4 stats – health, hunger, endurance and cold. The Purpose – take a pleasure in survival process.
There are 4 types of gun. At start you have a piston. With time new gun will be generated on a map.
pistol
AK-47
M4A1
AWP
Occasionally ammo for weapon, aid kits and flak jacket will be generated on a map. Don't miss them. To activate aid kit just switch to its inventory cell.
pistol
AK-47
M4A1
AWP
standart aid kit
extended aid kit
Use these ones to switch between inventory cells
Use left mouse click or space to make shot
Use these ones to move a player
R for reload a gun
Use T to open your backpack
M to open a minimap
Use shift to run away from zombies
Those who created this game
RS School student
RS School student


[gatherings]
Search
About
Blog
More
Filter by location, host, subject, date, daytime:
Location
Host
Subject
Initial Date
Final Date
Daytime
Choose...
Day
Night
Search
Clear Filter
Search Result Found 7 [gatherings] Nearby.
go to [gathering] example
go to [gathering] example
go to [gathering] example


Before Change
def launch_command(self):
super().launch_command()
run_opts = ["-B"%s:%s"" % mp for mp in self.mount_points]
if self.with_cuda:
run_opts.append("--nv")
run_opts += self.options
run_cmd = "singularity exec %s %s bash -c " % (" ".join(run_opts),
self.image)
return run_cmd + """ + " ".join(
["cd " + self.workdir] + self.commands) + """
class ContainerPlatformField(fields.TypedField):
def __init__(self, *other_types):
After Change
run_opts += self.options
workdir_cmd = f"--workdir="{self.workdir}" " if self.workdir else ""
if self.command:
return (f"singularity exec {workdir_cmd}{" ".join(run_opts)} "
f"{self.image} {self.command}")
return (f"singularity run {workdir_cmd}{" ".join(run_opts)} "
f"{self.image}")


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 CIVIL APPELLATE JURISDICTION CIVIL APPEAL NOS.4616-4617 OF 2009 VASANT CHEMICALS LIMITED ….Appellant VERSUS THE MANAGING DIRECTOR, HYDERABAD METROPOLITIAN WATER SUPPLY AND SEWERAGE BOARD AND OTHERS …Respondents With CIVIL APPEAL NOS.4618-4619 OF 2009 VASANT CHEMICALS LIMITED ….Appellant VERSUS M. D., HYDERABAD METRO W.S. & S. BOARD & OTHERS …Respondents JUDGMENT
R. BANUMATHI, J.
These appeals arise out of the judgment dated 29.10.2003 passed in the Writ Petition Nos.4917 and 5044 of 2000 and order dated 29.12.2003 passed in review petition by the High Court of Andhra Pradesh at Hyderabad dismissing the writ petitions as well as the review petitions holding that the levy of sewerage cess Signature Not Verified Digitally signed by levied on the appellant by the respondent-Board is in accordance MAHABIR SINGH Date: 2019.02.13 16:52:38 IST Reason:
with Section 55 of the Hyderabad Metropolitan Water Supply and 1 Sewerage Act, 1989 (HMWS&S Act) and Clause 16 of the agreement entered into between the appellant and the Board.
2. The facts giving rise to these appeals are that the appellant- M/s Vasant Chemicals Limited which is an amalgamation of three companies is engaged in the manufacture and export of dye intermediates and other organic chemicals in their units at Jeedimetla Industrial Estate, Ranga Reddy District, Hyderabad. The effluents of the appellant industry and other industries were not of acceptable standards to be let into the sewer line of the Board and required treatment and therefore, the industrial units in Jeedimetla Estate decided to establish the Common Effluent Treatment Plant (CETP). Hence, under the joint efforts of all the chemical units and other industries including the appellant, a company was formed namely M/s Jeedimetla Effluents Treatment Limited (JETL) in the year 1987 to get the effluents treated at their own cost to bring the quality of the effluents to an acceptable level. The appellant and the other industrial units made investment by way of shares in the said company towards its capital. According to the appellant, it has invested to the extent of more than 29% of the shares in JETL towards its equity.
3. After treating the effluents to sewer standards as prescribed under the Water (Prevention and Control of Pollution) Act, 1974 (Water Act, 1974) and the Environment (Protection) Act, 1986 (Environment Act, 1986) between 1988 and 1995, JETL was 2 discharging the treated waste water/effluents into the open drains/nalas in Jeedimetla Area. After discussion with Hyderabad Metropolitan Water Supply and Sewerage Board (HMWS&SB-the Board) and the Government of Andhra Pradesh and APPCB, a dedicated pipeline was laid from the premises of JETL to connect to the sewerage system of HMWS&SB which is located at a distance of about 10.38 kilometers at Balanagar at an estimated cost of Rs.346 lakhs. For the said dedicated pipeline, JETL paid an amount of Rs.75,00,000/- as its contribution and the balance amount was contributed by the Board and the Government of Andhra Pradesh. The pipeline became operational on 31.01.1998. As per the direction of APPCB, the industries in IDA Jeedimetla are discharging their industrial effluents to JETL, which in turn partially treat effluents and let into the dedicated pipeline connecting JETL and sewer line at Board’s sewer at Kukatpalli, Balanagar and then carried to Sewerage Treatment Plant (STP) at Amberpet.
4. The appellant has obtained bulk water supply connection from the respondent-HMWS&S Board and the Board accorded sanction for supply of 36,200 gallons water per day @ Rs.12 per kilo litre to the appellant-Industry. An agreement was entered into by the appellant with the respondent-Board on 27.04.1995 stipulating the terms and conditions of supply of water and the payments required to be made in terms thereto. The agreement provides that HMWS&SB will supply water to the appellant industry 3 and water charges will be levied for the supply of water as per the agreement. Clause 16 of the agreement inter alia provided for payment of sewerage cess and that the appellant is liable to pay a sewerage cess in accordance with Section 55 of the HMWS&S Act. Clause 17 of the agreement obligates the appellant to avail the sewer facility provided by the HMWS&SB if the premises of the appellant is located at a distance of less than thirty-five meters from the sewer line of the HMWS&SB.
5. The appellant made representations between 1998 and February, 2000 stating that levy of sewerage cess was illegal and contrary to the provisions of HMWS&S Act as the appellant is not discharging its effluents into the sewerage system of the Board. According to the appellant, the Board insisted upon payment of the arrears and sought payment of the sewerage cess for the period January, 1998 to March, 2000 and sought certain amount towards water cess from 1st January, 1998 to February, 2000 vide two notices dated 25.01.2000. Aggrieved thereby, the appellant filed writ petitions in WP(C) No.4917/2000 and WP(C) No.5044/2000 challenging the notices levying of water cess and sewerage cess respectively. The writ petitions were dismissed by the High Court by the common judgment dated 29.10.2003 upholding the levy of sewerage cess by holding that such levy is in terms of Section 55 of HMWS&S Act. The High Court held that though the appellant’s premises is not directly connected to the 4 sewer line of the Board, the industrial effluents of the appellant are being carried to JETL and after partial treatment at JETL, the same is let into the sewerage system of the Board. It was further observed that as per Section 55 of the HMWS&S Act, the occupier of the premises from where the sewerage or effluents are let into the sewer facility provided by the Board by any means, has to pay the sewerage cess irrespective of the fact that whether or not the area is served by sewerage system of the Board. The High Court pointed out that this statutory liability is incorporated in Clause 16 of the agreement as per which the appellant has to pay sewerage cess along with water cess @ 20% of the water charges. The High Court dismissed the writ petitions vide judgement dated 29.10.2003 holding that the demand notices are not arbitrary and that do not suffer from any legal infirmities.
6. The appellant filed review petitions being Review MP No.33154/2003 in WP(C) No.4917/2000 and Review MP No.33158/2003 in WP(C) No.5044/2000 before the High Court which came to be dismissed vide order dated 29.12.2003 on the ground that the judgment dated 29.10.2003 does not suffer from any error apparent on the face of the record.
7. Mr. V. Giri, learned senior counsel for the appellant submitted that since the premises of the appellant industry is situated in the area not served by the sewage system of the Board and in terms of proviso to Section 55 of the HMWS&S Act, no sewerage cess is 5 leviable. It was contended that since the appellant is covered under proviso to Section 55 of the HMWS&S Act, the statutory liability cannot be imposed on the appellant on the basis of Clause 16 of the agreement. Without prejudice to the above contentions, it was urged that under the agreement dated 31.08.2000 between the JETL and the Board, various charges are levied on JETL which are in effect sewerage cess and therefore, there cannot be double levy for the same service/same taxable event which is impermissible under the law. It was contended that the various documents produced and the contentions raised by the parties in the review petitions were not considered by the High Court and the High Court erred in dismissing the review petitions.
8. Reiterating the above submissions, on behalf of JETL, Mr. Guru Krishna Kumar, learned senior counsel submitted that under the agreement dated 31.08.2000, five different kinds of charges are levied on JETL by the Board namely:- (i) capital contribution (clause 4); (ii) sewerage connection charges (clause 4); (iii) charges towards maintenance of sewer line (clause 28); (iv) sewerage maintenance and sewerage treatment charges (clause
28); and (v) sewerage surcharge for effluents above a certain level (clause 29) and those charges though not christened as sewerage cess, they are in effect sewerage cess in terms of Section 55 of HMWS&S Act. It was further contended that various charges levied on JETL by virtue of the agreement dated 31.08.2000 correspond to 6 the sewerage cess under Section 55 of HMWS&S Act and levy of sewerage cess on the appellant for the same act of discharging of the same sewage, would therefore amount to a double levy on the industrial units.
9. On behalf of the respondent Board, learned senior counsel Mr. Gourab Banerji submitted that the appellant industry, obtaining bulk water supply from the Board and discharging sewage into the sewer line of the Board, is liable to pay sewerage cess under Section 55 of the HMWS&S Act. It was submitted that since after partial treatment at JETL, the effluents are let into the sewer line of the Board through which the effluents are carried to Sewerage Treatment Plant (STP) at Amberpet for further treatment, the appellant is connected to the sewerage system of the Board and is liable to pay sewerage cess under Section 55 of the HMWS&S Act. It was contended that Clause 16 of the agreement incorporates the levy under Section 55 of the HMWS&S Act and the Rules and Regulations thereunder and as per the terms of the agreement also, the appellants are liable to pay sewerage cess. Insofar as the plea of double taxation, it was submitted that the JETL was not a party to the writ petitions filed by the appellant and the subsequent writ petition in WP(C) No.17381/2004 filed by the JETL inter alia challenging the sewerage surcharge under various agreements was already dismissed for default by the High Court. 7
10. We have carefully considered the submissions and perused the impugned judgment and materials on record. The following points arise for determination in these appeals:-
(i) Whether the appellant is right in contending that the appellant unit is not connected to the sewerage system of the Board and so the levy of sewerage cess on the appellant under Section 55 of HMWS&S Act is not sustainable?
(ii) Whether the appellant is right in contending that since the appellant’s unit is not served by a sewerage system of the Board, as per proviso to Section 55 of HMWS&S Act, no sewerage cess can be levied?
(iii) Whether the charges collected from JETL under the agreement dated 31.08.2000 is in effect, sewerage cess in terms of Section 55 of HMWS&S Act, thereby amounting to double levy of sewerage cess/charge for the same service/same taxable amount?
Appellant’s statutory liability to pay sewerage cess and Re: contention: Appellant is covered by the proviso to Section 55 of the Act
11. Section 55 of the HMWS&S Act contemplates levy of sewerage cess on the occupier of the premises from where the sewage or industrial effluents, as the case may be, are let into the sewer facility provided by the Board by any means whatsoever irrespective of fact whether or not the area is served by sewerage system of the Board. Section 55 of HMWS&S Act reads as under:-
“55. Charges towards the use of sewerage cess--- 8 Every occupier of both domestic and non-domestic premises shall pay to the Board at the rate not exceeding thirty five percent of the bill charging for the water consumed or at such rate as may be prescribed by rules, to defray the capital cost of sewerage and sewage treatment works undertaken by the Board and the operation and maintenance of the sewerage system from time to time:
Provided that no such charges shall be levied in any premises situated in the areas which are not served by the sewerage system of the Board.”
12. Admittedly, the appellant industry has obtained sanction for bulk water supply connection from the Board for the supply of 36,200 gallons of water per day @ Rs.12/- per kilo litre for the manufacture of dye and other chemicals. In terms of the sanction of water supply to the appellant, an agreement was entered into with the respondent-Board on 27.04.1995 stipulating the conditions and the payments required to be made in terms thereto. The agreement provides for payment of sewerage cess in accordance with Section 55 of the HMWS&S Act. Clause 16 of the agreement mandates the Board to collect sewerage cess from the appellant-industry in terms of Section 55 of the HMWS&S Act. Clause 17 of the agreement makes it obligatory on the part of the appellant to avail the facility of the Board if it is located within thirty-five meters from the Board’s sewerage system. Clauses 16 and 17 read as under:-
“Clause 16. In accordance with the provisions of Section 55 of the HMWSSA Act, 1989, the consumer shall pay 9 sewerage cess along with water charges at the rate of 20% of the water charges or such other rates as may be prescribed and determined by the Board from time to time. Clause 17. It shall be obligatory on the part of the consumer to avail the sewers facility provided by the Board if the premises of the consumers are located at a distance less than 35 metres away from the Board sewer line to any point of the boundary of the consumer premises.”
13. Appellant industry and other industrial units are producing chemicals, bulk pharmaceuticals and dye intermediates causing heavy pollution. In order to comply with the provisions of Water Act, 1974, the industrial effluents discharged by the appellant industry and others are to be treated otherwise the industrial units will be violating various laws governing the treatment and disposal of sewage including protection of environment. The issue pertaining to pollution, discharge of effluents in the State of Andhra Pradesh including the industrial region of Jeedimetla was the subject matter of a proceeding before this Hon’ble Court being Writ Petition (C) No.1056 of 1990, in the matter of Indian Council for Enviro/legal Action and Others. In the said proceedings, a joint action plan was proposed by the CPCB, New Delhi and APPCB and a common effluent treatment plant was ordered to be set up. As the industries were sending their untreated effluents into the sewer, directions were given that the A.P. Pollution Control Board would not accept the effluents unless these conform to the standards prescribed by the Board vide Indian Council for Enviro Legal 10 Action and others v. Union of India and others , (1998) 9 SCC
580. Similar problem arose in the case of World Saviors v. Union of India and others (1998) 9 SCC 247. In order to comply with the provisions of the Water Act, 1974 and the Environment Act, 1986 and in order to carry the industrial sewage to the Board’s sewer trunk, a dedicated pipeline to the extent of 10.38 kilo meters from JETL to Kukatpally and Sanathnagar Main Line was laid. The cost of laying the pipeline is stated to be Rs.346 lakhs out of which contribution of the JETL was Rs.75 lakhs and the balance amount was contributed by the Board and the Government of Andhra Pradesh. This dedicated pipeline became operational from 31.01.1998. The pipeline from JETL to Balanagar is a dedicated pipeline used exclusively by the JETL. As per the agreement entered into with the Board, the management of the JETL pays the amount to the Board towards surcharge for discharging partially treated effluents from JETL into Board sewer and also for maintenance of the sewerage system. After the industrial effluents are partly treated at JETL, the industrial effluents are let into the dedicated pipeline belonging to the Board system at Balanagar and from there, the sewage is let into 1000 mm diameter sewage trunk main belonging to the Board through which the effluents are carried to Sewerage Treatment Plant (STP) at Amberpet.
14. “A ‘trunk sewer’ is one which bears the same relation to an entire sewer system that the trunk of a tree bears to its branches, 11 or the main stream of a river bears to its tributaries. It is sometimes called a ‘trunk line sewer,’ an ‘intercepting sewer,’ or a ‘trunk line intercepting sewer”. “Ref: Environmental & Pollution laws in India by Justice T. S. Doabia (2 nd Edition-2010) published by LexisNexis Butterworths Wadhwa, Volume 1 at page no.1054 .” Graphic description of the sewerage connection is as under:-
STP, Amberpet 18.90 kms 1000 mm sewage Trunk Disposal of Treated Wastewater Through Dedicated Pipeline/Pipeline Hyderabad Metropolitan laid by the Board part contribution by Water Supply & JETL Sewerage Board, Kukatpalli/Balanagar Water Supply 10.38 kms 1.2 kms…. No pipeline Vasant Chemicals Jeedimetla Effluent Private Limited Industrial Wastewater & Domestic Treatment Limited (JETL) Sewage taken by tankers for Treatment & Disposal
15. As per Section 55 of the HMWS&S Act, the following essential ingredients are to be satisfied for levy of sewerage cess:-
1. There has to be an occupier domestic or non-domestic premise;
2. There should be consumption of water by such occupier;
3. The rate to be charged would be up to 35% of bill for water consumed or at such rate as may be prescribed by rules; and
4. The amount collected is towards:- (a) defraying capital cost of sewerage and sewerage treatment works 12 undertaken by the Board; and (b) for operation and maintenance of sewerage system from time to time.
16. The appellant being an occupier of a “non-domestic premise” having bulk water supply connection from the Board and “a consumer of water” and eventually discharging sewage effluents into the sewer line of the Board, the essential ingredients of Section 55 are thus satisfied. The levy of sewage cess by the respondent is a statutory levy which the appellant is liable to pay under Section 55 of HMWS&S Act. Clause 16 of the agreement provides for payment of sewerage cess in terms of Section 55 of the Act which inter alia stipulates that the appellant is required to pay sewerage cess in accordance with Section 55 of the Act. The sewerage cess of 35% levied by the Board for carrying the sewage of the acceptable quality through its transmission system is thus both statutory and in terms of the agreement between the appellant and JETL.
17. Contention of the appellant is that it is not liable to pay sewerage cess to the Board as it is not letting out the sewage effluents to the sewage system of the Board but is carrying the effluents in the tanker, lorries and letting it out in the effluent treatment of JETL and thus is not connected with the sewage line of the Board. Mr. V. Giri, learned senior counsel for the appellant contended that the appellant industry is not connected with sewerage system of the Board and therefore, levy of sewerage 13 cess under Section 55 of the HMWS&S Act is not sustainable. Drawing our attention to the finding of the High Court “that there is no sewerage line of HMWS&SB connecting the appellant’s premises to the sewerage system of HMWS&SB…..”, the learned senior counsel for the appellant submitted that since there is no sewer or drainage line connecting the appellant industry, proviso to Section 55 of the HMWS&S Act applies and no sewerage cess is leviable. It was further submitted that even assuming that the dedicated pipeline from JETL for carrying its treated effluents to the sewerage system of the Board at Balanagar is a “sewerage system of the Board” which is more than two kilo meters from the premises of the appellant industry, JETL is separately paying the surcharge and the appellant is not connected with the sewerage system and therefore, there cannot be levy of sewerage cess on the appellant under Section 55 of the HMWS&S Act.
18. As pointed out earlier, admittedly, the appellant has obtained bulk water supply connection from the Board for supply of 36,200 gallons of water per day @ Rs.12/- per kilo litre. It is also admitted that the appellant is discharging its industrial effluents into the Board sewer line. The appellant being an occupier of the premises who is consuming water and discharging sewage into the sewerage system of the Board, in terms of Section 55 of the HMWS&S Act, is liable to pay sewerage cess. Though the pipeline from JETL to Kukutpally/Balanagar is stated to be the dedicated pipeline, as 14 pointed out earlier, this was laid at the cost of Rs.346 lakhs, out of which, JETL has paid only Rs.75 lakhs. The rest of the cost was borne by the Board and the Government of Andhra Pradesh. It is pertinent to note that Clause 4 of the agreement dated 31.01.1998 between JETL and the Board categorically stipulates that the dedicated pipeline from JETL to Kukutpally/Balanagar belongs to the Board.
19. As per Section 54 of the Act, sewage which is likely to damage or interfere with the free maintenance of the sewerage system of the Board cannot be passed into the Board sewer and sewage treatment works. In terms of Section 54 of HMWS&S Act, Clause 19 is also incorporated in the agreement dated 27.04.1995 between the appellant industry and HMWS&SB. As per Clause 19 of the agreement, no effluents shall be discharged into the Board’s sewerage system unless such effluents are treated in accordance with the provisions of the Water Act, 1974. Clause 19 reads as under:-
“19. No effluent shall be discharged into the Board sewer unless such effluent is treated in accordance with the provisions of Water (Prevention and Control of Pollution) Act, 1974 relating to discharge and disposal of industrial effluents and other objectionable effluents. Further, the treatment shall also conform to the IS specification laid down from time to time for disposal of effluent into the domestic sewer of the Board.” 15 Admittedly, JETL is neither a consumer of bulk water supply nor generating any sewage/industrial effluents of its own. The effluents of the appellant industry are not of acceptable standards for transmission system of the Board. Before the effluents of the appellant industry are to be let into the sewer line of the Board, the appellant industry has to get the effluents treated at its own cost to bring the quality of the effluents to an acceptable level. After getting partial treatment from JETL, the effluents are let into the said dedicated pipeline which belongs to the Board at Kukutpally/Balanagar and then they are let into 1000 mm diameter sewage trunk belonging to the Board through which the effluents are carried to Sewerage Treatment Plant (STP) at Amberpet measuring a distance of 18.90 kilo meters. The length of the pipeline from JETL to Amberpet is 29.28 kilo meters. Though the appellant’s unit is not directly connected with the Board sewer line, the industrial effluents of the appellant unit partially treated at JETL are ultimately let into the Board sewer line which is finally carried to STP at Amberpet. In the light of this admitted factual position, the appellant is liable to pay sewerage cess under Section 55 of the Act. Proviso to Section 55 of the Act contemplates that the sewerage cess shall not be levied on the occupier of the premises if such premises is stated to be in an area which is not served by the sewerage system of the Board. The proviso implies that the occupier of such premises cannot use the Board sewer by any 16 means whatsoever. Therefore, the contention of the appellant that it is not liable to pay sewerage cess to the Board as it is not directly letting out sewage effluents into the sewage line of the Board and that it is carrying its effluents in the tanker, lorries and letting out in the effluent treatment plant of JETL and thus not connected with the sewage system of the Board, in our view, is wholly untenable. Since the sewage of the appellant is ultimately let into the sewer line of the Board, the appellant cannot contend that it is not covered under Section 55 of the Act and that it is covered under proviso to Section 55 of the Act.
20. Placing reliance upon Ultra Tech Cement Ltd. v. State of Maharashtra and another, (2011) 13 SCC 497, learned senior counsel for the appellant contended that when a particular cess is leviable under an enactment and the said enactment exempts a specific class of persons from paying the said cess, the State Government cannot make the lessee liable to pay the said cess on the ground that the agreement was entered into under a different enactment. Placing reliance upon paras (12) and (20) of the said judgment, it was contended that there is no sewer or drainage line connecting the appellant’s units or any other industry in Jeedimetla Effluent Treatment Limited to the sewerage system of HMWS&SB and neither the appellant nor other industries discharge their sewage into the sewer line of the Board and, therefore, the appellant’s unit is covered under proviso to Section 55 of the 17 HMWS&S Act. The learned senior counsel further contended that any fiscal extraction is required to be constructed strictly in accordance with the provisions of the charging section and even if a clause for such payment is incorporated into the agreement as the agreement is subject to the provision of the relevant charging section.
21. The above argument proceeds on the presumptive footing as if the appellant’s unit is covered under proviso to Section 55 of the HMWS&S Act. Proviso to Section 55 of HMWS&S Act states that no charge would be levied in any premises situated outside the sewage system/not served by the sewerage system of the Board. It has to be seen whether the appellant is right in contending that the appellant industry is not connected with the sewerage line of the Board and that no sewage of the appellant is let into the sewerage system of the Board and therefore, the appellant is covered under proviso to Section 55 of HMWS&S Act.
22. In the process of letting out effluents, two things are involved namely – (i) the treatment of industrial effluents to bring down the contents of the effluents to an agreed specification on one part; and (ii) the transmission of those partially treated industrial effluents through the sewerage system of the Board. Parties have entered into various agreements and there are three sets of agreements which are as under:-
18
S. No. Parties Date of Agreement 1. M/s. Vasant Chemicals Ltd. and 27.04.1995 HMWS&S Board 2. M/s. Vasant Chemicals Ltd. and 22.01.1996 Jeedimetla Effluent Treatment Ltd. (JETL)
3. Jeedimetla Effluent Treatment Ltd. 31.01.1998 (JETL) and HMWS&S Board and 31.08.2000
23. Let us now consider the effect of the agreement between the appellant and JETL on the statutory liability of the appellant under Section 55 of the Act. The agreement between the appellant and JETL for partial treatment of appellant’s industrial effluents is the internal contractual agreement between JETL and the appellant. The appellant unit is to treat and process the industrial effluents and bring them down to permissible standard limits in accordance with the provisions of Water Act, 1974 and Environment Act, 1986 relating to discharge and disposal of industrial effluents and other objectionable effluents into sewers before discharging of the effluents into the Board sewer. The treated effluents should also have to conform to the IS specification laid down from time to time for disposal of effluent into the domestic sewer of the Board. To discharge their contractual obligation in bringing the industrial effluents to permissible standard limits, the appellant unit entered into an agreement dated 22.01.1996 with JETL engaging it to treat its industrial effluents in accordance with the environmental laws in force. The appellant instead of treating the effluents at its 19 premises at its own cost engaged JETL for treating its effluents. Thus, for its convenience, the appellant unit has entered into an agreement with JETL for treating its effluents and the charges paid by them to JETL are towards the treatment of effluents and bring it to permissible standards. Therefore, the function of JETL is that of an intermediary with whose assistance, the appellant is discharging its statutory obligation.
24. Admittedly, the appellant’s industrial effluents are carried to JETL in closed tankers and after partial treatment at JETL, let into the Board’s sewer line. Admittedly, the effluents of the appellant’s unit are not of acceptable standards for transmission through the sewer line of the Board and therefore, the appellant’s industry and other industries have to get the effluents treated at their own cost to bring the quality of the effluents to an acceptable level by treating the same to some extent. The sewerage cess of 35% levied by the Board is for carrying the sewerage of acceptable quality through its sewer line and further treating it at STP at Amberpet.
25. The sewerage cess aims to recover the cost of treating the effluents of strength stronger than domestic sewage and to make the effluents of acceptable quality. In addition to partial treatment at JETL, the effluents require further treatment and their transmission to Sewer Treatment Plant (STP) at Amberpet situated 20 at 18.90 kms from Bala Nagar which requires huge finance. The maintenance of sewer line is highly essential for proper transmission of the effluents from JETL to Board’s sewer system at Amperpet where the Board brings down the industrial effluents to the tolerance limits. It requires huge amount to maintain the STP treatment of industrial effluents. Further, it requires high demand of energy, STP personnel to operate and maintain the system, skilled and unskilled workers for proper maintenance of the plant. The respondent-Board unless it collects sewerage cess and other charges cannot meet the heavy expenditure on the operation and maintenance of sewerage system. The liability of the appellant to pay sewerage cess to the Board arises from the Statute and also by way of an agreement which was agreed upon by the appellant. There is no merit in the contention of the appellant unit that its liability has ended upon transferring the industrial effluents to the respondent-JETL and that it is not connected to the Board’s sewer line. As discussed earlier, the partially treated effluents of the appellant’s unit are ultimately let into the sewer line provided by the Board which is being carried to Amberpet STP for further treatment and discharge. After partial treatment at JETL, when appellant’s effluents are let into the Board’s sewage system, the appellant is not justified in contending that it is not connected to the sewer line of the Board and hence, covered under the proviso to Section 55 of the Act.
21
26. It is well-settled that the normal function of a proviso is to except something out of the enactment. While considering the interpretation of the proviso, in Romesh Kumar Sharma v. Union of India and others, (2006) 6 SCC 510, this Court held as under:-
“12. “10. The normal function of a proviso is to except something out of the enactment or to qualify something enacted therein which but for the proviso would be within the purview of the enactment. As was stated in Mullins v.
Treasurer of Surrey (1880) 5 QBD 170 (referred to in Shah Bhojraj Kuverji Oil Mills and Ginning Factory v. Subbash Chandra Yograj Sinha AIR 1961 SC 1596 and Calcutta Tramways Co. Ltd. v. Corpn. of Calcutta AIR 1965 SC 1728 , when one finds a proviso to a section the natural presumption is that, but for the proviso, the enacting part of the section would have included the subject-matter of the proviso. The proper function of a proviso is to except and to deal with a case which would otherwise fall within the general language of the main enactment and its effect is confined to that case. It is a qualification of the preceding enactment which is expressed in terms too general to be quite accurate. As a general rule, a proviso is added to an enactment to qualify or create an exception to what is in the enactment and ordinarily, a proviso is not interpreted as stating a general rule. ‘If the language of the enacting part of the statute does not contain the provisions which are said to occur in it you cannot derive these provisions by implication from a proviso. …’ said Lord Watson in West Derby Union v. Metropolitan Life Assurance Society 1897 AC 647. Normally, a proviso does not travel beyond the provision to which it is a proviso. It carves out 22 an exception to the main provision to which it has been enacted as a proviso and to no other……”
27. The sewerage cess levied under Section 55 of the HMWS&S Act is a statutory levy on the appellant as it satisfies the essential requirements of Section 55 of the Act. The agreement/contract between the appellant’s unit and JETL does not take away the appellant from the network of the Board’s sewer line and its “ use and treatment of sewerage” of the Board’s sewerage system. Where the appellant’s effluents are being eventually sent to the Board’s sewer, the contention of the appellant that its premises are not served with a sewer line by the Board defies logic and runs contrary to the object of the Act. The appellant, being an occupier of non-domestic premises, is consuming the water provided by the Board, generating the industrial effluents and using the Board’s sewer to release them after partial treatment. In such an admitted position, the appellant cannot escape from the statutory levy by taking a technical approach and interpreting the proviso as a general rule where it is merely a qualifying one. As the appellant eventually lets out its effluents to the Board’s sewerage system, the appellant is not right in contending that it is covered under proviso to Section 55 of the Act.
28. Re: Contention – Levy of double taxation:- Learned senior counsel for the appellant contended that even assuming that the dedicated pipeline of JETL which connects to the sewerage 23 system of the Board at Balanagar is construed to be “Sewer”, any levy of sewerage cess is applicable only to JETL and JETL under its agreement with HMWS&SB, is paying surcharges and sewerage charges to HMWS&SB by collecting the said amount from the appellants and other industries for the said taxable event. It was submitted that under Section 55 of HMWS&S Act, the sewerage cess is collected for the – (i) to defray capital cost of sewerage; (ii) for sewage treatment works undertaken by the Board; and (iii) for operation and maintenance of the sewerage system. It is contended that under its agreement dated 31.08.2000 with the Board, JETL is paying various charges like - (i) sewerage connection charges; (ii) charges towards maintenance of sewer line; (iii) sewerage maintenance and water treatment charges; and
(iv) sewerage surcharge for effluents above a certain level. It was contended that various charges paid by JETL to the Board is in essence “sewerage cess”, though it is collected under different head “sewerage surcharge”.
29. Taking us through Clause 4 of the agreement with Board dated 31.08.2000, Mr. Guru Krishna Kumar, learned senior counsel appearing for JETL submitted that under agreement dated 31.08.2000, various charges are collected and it additionally provides for levy of surcharge also. It is contended that even though these charges may not be christened as a sewerage cess, they are in effect correspond to the essentials of “sewerage cess” 24 in Section 55 and a levy of cess from the appellant for the same act of disposal of the sewage would therefore amount to a double levy on the industrial units. The learned senior counsel submitted that sewerage cess cannot be exacted from the appellant because it is already been paid by JETL. It was urged that various charges levied on JETL are excessive arbitrary apart from the fact that there is a double levy.
30. As rightly contended by learned senior counsel for the respondent-Board, the plea of double payment of sewerage cess was never raised in the writ petition filed by the appellant; but it was raised by way of oral submission before the High Court and thereafter, by way of review petition. The plea of double levy was rightly rejected by the High Court inter alia holding that “even assuming for a moment that the petitioner-company is paying some amounts to the JETL, it cannot be said that it is towards sewerage cess”.
31. As pointed out by the learned senior counsel for the respondent-Board, JETL never sought to implead itself as a party respondent in the writ petition filed by the Board. It is also pertinent to point out that one Mr. G.K.B. Chowdary who was then the Managing Director of the appellant-group of companies, was also the Managing Director of JETL. It passes one’s comprehension as to why JETL whose Managing Director is the same as the 25 Managing Director of the appellant Group of Companies had not taken any step to get themselves impleaded in the writ petition before the High Court and raise the plea of double taxation.
32. In the Supreme Court, notice was ordered on 07.07.2004 and permitted the appellant to implead JETL as party respondent. It was thereafter, JETL filed writ petition in WP(C) No.17381/2004 (24.09.2004) inter alia for various reliefs:- (i) That clauses 28 and 29 of the agreement dated 10.06.2003 between the petitioner company Jeedimetla Effluent Treatment Limited and HMWS&SB as shylockin and unconscionable, usurious, exorbitant, unconstitutional, ultra vires the powers of the HMWS&SB; and (ii) That the action of the HMWS&SB in collecting various charges under Clause 4 of the agreement and other charges levied upon JETL. The said writ petition that kept pending for many years came to be dismissed by the High Court’s order dated 21.12.2015 for non-prosecution. JETL has also filed WP(C) No.20117/2017 challenging the enhancement of sewerage surcharge and the said writ petition is also said to have been dismissed on 25.06.2014.
33. Since, elaborate arguments were advanced regarding “excessive and arbitrary levy on JETL” as well as the plea of “double levy of sewerage cess”, we have also considered the matter on merits. Based on three sets of agreements between the parties, there are three kinds of payments as under:- 26
a) Payment of sewerage cess by the appellant to the Board in terms of Section 55 of the HMWS&S Act and Clause 16 of the agreement dated 27.04.1995;
b) Payment of treatment and processing service charges by the appellant unit to JETL as stipulated in Clause 19 of the agreement between the appellant and JETL dated 01.04.2000; and
c) Various charges paid by JETL to the Board pursuant to the agreement dated 31.08.2000 and the earlier agreements. So far as the payment by the appellant unit to the Board, it is the statutory liability of payment of sewerage cess in terms of Section 55 of HMWS&S Act and Clause 16 of the agreement which obligates the appellant unit to pay the sewerage cess in terms of Section 55 of the HMWS&S Act. The appellant having bulk water supply connection from the Board and being “consumer of water” and discharging sewage/effluents into the sewer line of the Board, the payment of sewerage cess by the appellant unit is the statutory liability under Section 55 of the HMWS&S Act and Clause 16 of the agreement.
34. Insofar as the charges paid by the appellant to JETL for the treatment and processing of its effluents, it is purely contractual pursuant to the agreement entered into between the appellant unit and JETL dated 01.04.2000 and the earlier agreement dated 22.01.1996. As pointed out earlier, the appellant unit is obligated to treat and process the industrial effluents and bring them down to permissible standard limits in accordance with the provisions of 27 the Water Act, 1974 and Environment Act, 1986 before they are let into the sewer line of the Board. To discharge its statutory as well as contractual obligation, the appellant unit has entered into agreement with JETL for the treatment and processing of appellant’s effluents before being let into Board’s sewer line. Payment of charges by the appellant to JETL is purely contractual between the parties and the same cannot be considered to be in deference to the statutory cess/statutory charge which can only be levied by the Board. In this regard, the High Court has rightly observed that assuming that the appellant is paying some amount to JETL, the same cannot be termed as “sewerage cess”.
35. So far as payment of charges by JETL to the respondent Board, the same is governed by the terms and conditions of the agreement between JETL and the Board dated 31.08.2000. JETL’s contention is two fold: - (i) levy of various charges under the agreement is arbitrary and exorbitant; and (ii) double levy of sewerage cess. The gist of the terms and conditions of the contract dated 31.08.2000 between JETL and the Board and various charges levied are as under:-
1. Clause 4 specifically stipulated that JETL shall be charged towards overall proportionate sewerage maintenance and sewerage treatment charges being incurred by the Board from time to time on the overall sewerage system of the Board;
28
2. In terms of Clause 4, the Board has levied sewerage connection charges @ Rs.4/- per litre for the discharge into the Board sewer (6 equal installments of Rs.23.34 lakhs each by 10th of each month) – Total Rs.140.04 lakhs;
3. Clause 18 stipulates that no treated effluent shall be discharged by JETL unless the same is treated in accordance with the provisions of the Water and the Air Acts and the various upper limits of the parameters of the treated industrial effluents shall be within the permissible standard limits prescribed; Further, Clauses 22 to 24 give the Board the right to reject effluents of JETL if they are not found to be consistent with the prescribed parameters;
4. In terms of Clause 28, an amount of rupees one lakh per month is to be paid by JETL towards maintenance of the sewer line. Additionally, JETL has to pay sewerage maintenance and sewerage treatment charges @ Rs.6 per thousand litres of treated effluents;
5. Further, as per Clause 29, a surcharge was also levied on JETL for permitting industrial effluents beyond the limits prescribed on two important parameters viz. Chemical Oxygen Demand (COD) and Total Dissolved Solids (TDS); Each parameter/COD and TDS will be considered independent for levy the surcharge.
36. In terms of Rule 4 of Sewerage Rules, the Board shall charge on the applicants seeking to discharge the trade or industrial effluents etc. Rule 4 reads as under:-
“Sewerage and Industrial Effluents-
4. The Board shall charge on applicants seeking to discharge their trade or industrial effluents, sullage drain, sewer (other than storm sewer or combined sewer) of a private party, State Government, Central Government, or 29 local body or local authority, into Board sewers, towards the special treatment cost of such sewage and the charges shall be as fixed by the Board from time to time, depending upon the nature of such sewage and cost of treatment involved to bring the same within tolerance limits of effluent standards etc. The installation and maintenance of required meters for measuring the volume of effluents shall be insisted at the cost of the applicants, by the board.” Subject to the provisions of Water Act, 1974 and Environment Act, 1986 and subject to the restrictions of Section 54 of HMWS&S Act and in terms of Rule 4 and other terms and conditions, Board has the right to permit the ‘applicants’ seeking to discharge their trade or industrial effluents into the Board’s sewer system and Sewerage Treatment Plant subject to the imposition of costs. The treatment for letting the trade or industrial effluents into the Board’s sewer shall be subject to such terms and conditions and in such form of agreement as may be prescribed in the regulations made by the Board in accordance with these rules. Having entered into the agreement with the Board on 31.08.2000 and on prior dates, JETL cannot turn around and challenge the terms and conditions imposed upon it by virtue of the agreement.
37. So far as the various payments made by JETL to the Board, levy is in terms of Rule 4 of the Sewerage Rules and as per the contract and is purely contractual between JETL and the respondent Board for letting partially treated the industrial 30 effluents of the appellant and other units into the Board’s sewer. Likewise, charges paid by JETL to the Board cannot be said to be in lieu of the sewerage cess that the appellant unit is liable to pay which is a statutory liability. It is pertinent to note that many industries about fifty units, apart from the appellant unit, discharge their effluents to the CETP/JETL. The agreement dated 31.08.2000 and the earlier agreements between JETL and the Board are purely contractual consciously entered into between the parties.
38. JETL lets partially treated effluents into the Board’s sewerage system for further treatment. As discussed earlier, for further treatment of sewerage, the effluents are to be taken to Sewerage Treatment Plant (STP) at Amberpet which is situated at the distance of 08.30 kilometres from Balanagar. It requires huge amount for transmission of the effluents to Board’s sewer system at Amberpet where the Board brings down the industrial effluents to tolerance limits. As pointed out earlier, the treatment of industrial effluents requires high demand of energy, personnel to operate the system and skilled workers for maintenance of the plant. Unless the Board collects sewerage charge/sewerage surcharge, the Board cannot meet the heavy expenditure on the operation and maintenance of sewerage system. Various other members of JETL who discharge sewage into JETL which is ultimately let into Board sewer line, may or may not be consumers of water supply by the Board. That apart, members of JETL may 31 have their own source of water supply or they may supplement the supply of water from the Board through different sources either by extraction of ground water or supply through tankers which cannot be quantified by the Board. In pursuance of the provisions of the HMWS&S Act and the Sewerage Rules and pursuant to the agreement dated 31.08.2000, the charges are levied on JETL who in turn collects the charges from its member industrial units who discharge their effluents into JETL. Therefore, the payments made by JETL to the Board and the charges in turn collected by JETL from the appellant and other member units, cannot absolve the appellant unit from its statutory liability to pay the sewerage cess. We find no merit in the contention that there is double levy of sewerage cess.
39. Levy of sewerage cess being a statutory levy in terms of Section 55 of HMWS&S Act and Clause 16 of the agreement which incorporates the statutory levy under Section 55 of HMWS&S Act, the learned Single Judge and the Division Bench rightly recorded concurrent findings upholding the levy. Observing that the appellant being occupier of the premises, though not directly connected to the sewer line of the Board, is ultimately letting into the sewerage system of the Board after partial treatment at JETL, the High Court was right in holding that the levy of sewerage cess is in accordance with Section 55 of HMWS&S Act. The payment of sewerage surcharges and the other charges by JETL cannot take 32 away the statutory liability of sewerage cess levied on the occupier of the premises who consumes water and lets out the sewage into the Board sewer system. The payment of sewerage surcharge and other charges by JETL to the respondent-Board will not amount to double levy and the High Court rightly dismissed the writ petitions and also the review petitions filed by the appellant. The impugned order does not suffer from any infirmity warranting interference.
40. In the result, these appeals are dismissed. The arrears of sewerage cess, if any, to be paid by the appellant within a period of eight weeks from today with 6% interest with effect from the date cess fell due. If the arrears are not paid within the stipulated period of eight weeks, it shall carry interest at the rate of 12% thereafter.
..……………………….J.
[R. BANUMATHI] ...………………………..J.
[INDIRA BANERJEE] New Delhi;
February 13, 2019 33


Before you submit this form, please ensure you have Google Authenticator installed on your smartphone, as you will need it to complete your registration. Download from
iTunes |
Google Play
Add user!
{{ wtf.quick_form(form) }}
Note: The next page will show sensitive information. Make sure nobody can see your screen before pressing the Register button.


{{$return "This string was returned from PowerShell at $([DateTime]::Now.ToString())"$}}
{{$return @((New-Object -TypeName PSObject -Property @{This="was";Script="also"}),(New-Object -TypeName PSObject -Property @{This="returned in";Script="powershell"}))$}}


Talks
September 12, 2019: Madison Python Meetup (Madison, WI)
Accelerating Numerical Python with Numba [ GitHub repo ]
July 31, 2019: Data-Driven Wisconsin (Milwaukee, WI)
Parallel Computing in Python with Dask [ GitHub repo ]
Febuary 7, 2019: Madison Python Meetup (Madison, WI)
Parallel Computing in Python with Dask [ GitHub repo ]
October 30, 2018: WIPAC X-meeting (Madison, WI)
Parallel Computing with Dask [ GitHub repo ]
April 24, 2018: Big Data Madison Meetup (Madison, WI)
Getting started with machine learning using scikit-learn [ Slides ] [ GitHub repo ]
March 8, 2018: Madison Python meetup (Madison, WI)
Supervised machine learning in Python with scikit-learn [ Slides ] [ GitHub repo ]
December 5, 2017: WIPAC X-meeting (Madison, WI)
Reproducible Research with Python [ Slides ]
May 4, 2015: Phenomenology 2015 Symposium (Pittsburgh, PA)
Dark Matter Searches with a Mono-Z’ Jet