Note that NO TITLE WILL BE RENDERED if there isn't a title defined in the YFM of the "current" page.
# Pages Collection and Relative Helper
## Relative
Relative helper outside of the "each pages" block.
``` html
{{relative page assets}}
```
## Each Pages
``` html
From **../page.dest**, to: **this.dest**: collections-categories.html
From **../page.dest**, to: **this.dest**: collections-tags.html
From **../page.dest**, to: **this.dest**: each-pages.html
From **../page.dest**, to: **this.dest**: each-pages.html
From **../page.dest**, to: **this.dest**: pages.html
From **../page.dest**, to: **this.dest**: ../code/embed.html
From **../page.dest**, to: **this.dest**: ../code/gist.html
From **../page.dest**, to: **this.dest**: ../code/jsfiddle.html
From **../page.dest**, to: **this.dest**: ../collections/collections.html
From **../page.dest**, to: **this.dest**: ../content/copy.html
From **../page.dest**, to: **this.dest**: ../content/extract.html
From **../page.dest**, to: **this.dest**: ../content/glob-extensions.html
From **../page.dest**, to: **this.dest**: ../content/glob-sortby-content.html
From **../page.dest**, to: **this.dest**: ../content/glob-sortby-index.html
From **../page.dest**, to: **this.dest**: ../content/glob-sortby-none.html
From **../page.dest**, to: **this.dest**: ../content/glob-sortby-path.html
From **../page.dest**, to: **this.dest**: ../content/glob.html
From **../page.dest**, to: **this.dest**: ../content/include.html
From **../page.dest**, to: **this.dest**: ../content/listDocumented.html
From **../page.dest**, to: **this.dest**: ../content/listHelpers.html
From **../page.dest**, to: **this.dest**: ../content/match.html
From **../page.dest**, to: **this.dest**: ../content/partial.html
From **../page.dest**, to: **this.dest**: ../content/push-section.html
From **../page.dest**, to: **this.dest**: ../content/sections.html
From **../page.dest**, to: **this.dest**: ../content/toc.html
From **../page.dest**, to: **this.dest**: ../content/undocumented.html
From **../page.dest**, to: **this.dest**: ../converters/less.html
From **../page.dest**, to: **this.dest**: ../converters/markdown.html
From **../page.dest**, to: **this.dest**: ../converters/switch.html
From **../page.dest**, to: **this.dest**: ../converters/switch.html
From **../page.dest**, to: **this.dest**: ../html/alerts.html
From **../page.dest**, to: **this.dest**: ../html/css.html
From **../page.dest**, to: **this.dest**: ../html/exticon.html
From **../page.dest**, to: **this.dest**: ../html/js.html
From **../page.dest**, to: **this.dest**: ../html/link.html
From **../page.dest**, to: **this.dest**: ../html/lists.html
From **../page.dest**, to: **this.dest**: ../logging/expand.html
From **../page.dest**, to: **this.dest**: ../logging/inspect.html
From **../page.dest**, to: **this.dest**: ../nested/deep.html
From **../page.dest**, to: **this.dest**: ../nested/morenested/deeper.html
From **../page.dest**, to: **this.dest**: ../nested/morenested/evennesteder/deepest.html
From **../page.dest**, to: **this.dest**: ../objects/jsonld.html
From **../page.dest**, to: **this.dest**: ../objects/property.html
From **../page.dest**, to: **this.dest**: ../objects/stringify.html
From **../page.dest**, to: **this.dest**: ../objects/value.html
From **../page.dest**, to: **this.dest**: ../pages/basic.html
From **../page.dest**, to: **this.dest**: ../pages/index.html
From **../page.dest**, to: **this.dest**: ../pages/partials.html
From **../page.dest**, to: **this.dest**: ../partials/alert.html
From **../page.dest**, to: **this.dest**: ../partials/button.html
From **../page.dest**, to: **this.dest**: ../partials/hero.html
From **../page.dest**, to: **this.dest**: ../partials/nav.html
From **../page.dest**, to: **this.dest**: ../path/basename.html
From **../page.dest**, to: **this.dest**: ../path/dirname.html
From **../page.dest**, to: **this.dest**: ../path/extname.html
From **../page.dest**, to: **this.dest**: ../path/filename.html
From **../page.dest**, to: **this.dest**: ../path/relative.html
From **../page.dest**, to: **this.dest**: ../readme/authors.html
From **../page.dest**, to: **this.dest**: ../readme/gitlog.html
From **../page.dest**, to: **this.dest**: ../readme/opt.html
From **../page.dest**, to: **this.dest**: ../readme/roadmap.html
From **../page.dest**, to: **this.dest**: ../readme/travis.html
From **../page.dest**, to: **this.dest**: ../strings/hyphenate.html
From **../page.dest**, to: **this.dest**: ../strings/occurences.html
From **../page.dest**, to: **this.dest**: ../strings/replace.html
From **../page.dest**, to: **this.dest**: ../url/url-parse.html
From **../page.dest**, to: **this.dest**: ../url/url-resolve.html
```
``` html
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
From **../page.dest**, to: **assets**: ../../../../../../../assets
```
``` html
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
From **../page.dest**, to: **"output/assets"**: ../../../../output/assets
```
``` html
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
From **../page.dest**, to: **"src/content"**: ../../../../src/content
```


Menu
Home
Latest activity
Register
Forums
New posts
What's new
New posts
Latest activity
Products
Sign Up
Log in
New posts
Menu
Log in
Register
Home
Forums
Rhino Cheats
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
Customer Reviews
See what your peers think of our products.
Filters
Show only:
Loading…
Title
Replies
Views
Messages
Locked
Sticky
How to write a review for FREE SUBSCRIPTION TIME.

Cakes
May 10, 2019
Replies
5
Views
95
Cakes
May 11, 2019
W
best mw3 cheat around 100% happy with this
whipseh
Apr 22, 2019
Replies
1
Views
82
swoon
Apr 22, 2019
Rhino Cheats Review
Legend
Apr 22, 2019
Replies
1
Views
55
swoon
Apr 22, 2019
MW3 Cheat.
Izumi
Apr 11, 2019
Replies
3
Views
69
swoon
Apr 12, 2019
L
MW2 Cheat Review
lean1337
Apr 3, 2019
Replies
3
Views
140
swoon
Apr 5, 2019
M
Mw2 hack review
Mw2forlife
Feb 6, 2019
Replies
1
Views
129
Admin
Feb 6, 2019
C
MW2 Cheat Review
Cryptic
Dec 30, 2018
Replies
1
Views
115
Admin
Dec 30, 2018
D
The best cheats I ever seen before!!!!
diosy7
Dec 26, 2018
Replies
1
Views
87
swoon
Dec 26, 2018
I
[REVIEW] Best Cheats you will find. (11/10)
iTzMeAgain
Dec 18, 2018
Replies
1
Views
114
swoon
Dec 18, 2018
Rhino Cheats Review 3 Cheats.
maxwellray
Dec 18, 2018
Replies
1
Views
175
swoon
Dec 18, 2018
You must log in or register to post here.
Home
Forums
Rhino Cheats


This notice is to inform you that your proposal {{ args.proposal.title }} has been canceled.
If you have any further questions, please contact support for more information.


Dear {{ group_name }} admin,
{{ sender_name }} has sent {{ group_name }} a message:
{{ message }}
You can respond to them by replying to this email.
Thanks,
EA Hub
Feedback | Report an issue


TransformAlarmC decreases precision and/or widens an Alarm. An already widened Counter component is used to help.
See TEP102 for more details.
to_precision_tag
- A type indicating the precision of the transformed
Alarm.
to_size_type
- The type for the width of the transformed Alarm.
from_precision_tag
- A type indicating the precision of the original
Alarm.
from_size_type
- The type for the width of the original Alarm.
bit_shift_right
- Original time units will be 2 to the power
bit_shift_right
larger than transformed time units.


--- layout: page # # Goal: # 1. Integrated Swift compiler and libraries # 2. Easy to build # 3. For Windows application # --- Swift for Windows is an open source project that provides an easy-to-use development environment for Swift programming for Windows applications.
The most recent build for this project can be downloaded from SwiftForWindows-2.0.exe.
Newer release builds for Swift 5.x for Windows can be found at https://swift.org/download/#releases.
|
CURRENT |
Swift for Windows 2.0 | ||
|
DATE |
Tue Oct 9, 2018 | ||
|
DOWNLOADS |
import wx var app = wx.App() _ = wx.MessageDialog(wx.Window(), "Hello Window", "HelloWin", style:wx.OK).showModal()


Which boolean expression indicates whether the values for nodes p and q are the same? Assume that neither p nor q is null.
p.element == q.element
p == q
p.next == q.next


Welcome to my portfolio page. I'm a Web Developer with a Humanities background. My journey started in November 2017, and I never stopped learning new and exciting things since then. I like creating simple, accessible and neat designs and I'm eager to bring my skills to the next level!
Experience: 1 Year
Experience: 1 Year
Experience: 1 Year
Experience: 6 months


Vuef sources
Request For Comments on Vue3 Function-based Component API
where API stands for
Application Programming Interface
"Composition API" renamed from "Function-based Component API"
Plugin for Vue function-based API
Examples of Vue function-based API
Program With Erik: Vue 3 Function API Plugin First Look.


CSS has properties for specifying the padding for each side of an element: padding-top padding-right padding-bottom padding-left All the padding properties can have the following values: length - specifies a padding in px, pt, cm, etc. % - specifies a padding in % of the width of the containing element inherit - specifies that the padding should be inherited from the parent element Note: Negative values are not allowed.


If you are seeing this chances are you got everything working.
To see more of the demo:
Visit this page to execute the helloworld.py file
Visit this invalid page to get a 404


Test 1 - Find products
**** image of the product ****Are you affected?
Check the name of your product, its UPC and its "Best before date" to see if you are affected.
| Brand | Product | Best before | UPC |
|---|---|---|---|
| Culinary Creations Gourmet | Beef & Cheddar Onion Bun |<PHONE_NUMBER>9 | APR-16 April 23, 2018 |
| Culinary Creations Gourmet | Roast Beef Sandwich |<PHONE_NUMBER>31 | APR-16 April 23, 2018 |
| Culinary Creations Gourmet | Beef & Swiss Submarine ½ |<PHONE_NUMBER>9 | April 16, 2018 April 17, 2018April 18, 2018April 21, 2018April 23, 2018April 24, 2018 |
| Culinary Creations Gourmet | Beef & Swiss Submarine Long |<PHONE_NUMBER>79 | APR-17 April 21, 2018 |
| Denny's Express | Beef & Swiss Submarine |<PHONE_NUMBER>30 | Julian date 0718 |
| Brand | Product | Size | UPC | Best before |
|---|---|---|---|---|
| Culinary Creations Gourmet | Beef & Cheddar Onion Bun | 190 g |<PHONE_NUMBER>9 | April 16, 2018/br> April 23, 2018 |
| Culinary Creations Gourmet | Roast Beef Sandwich | 155 g |<PHONE_NUMBER>31 | April 16, 2018April 23, 2018 |
| Culinary Creations Gourmet | Beef & Swiss Submarine ½ | 250 g |<PHONE_NUMBER>9 | April 16, 2018 April 17, 2018April 18, 2018April 21, 2018April 23, 2018April 24, 2018 |
| Culinary Creations Gourmet | Beef & Swiss Submarine Long | 250 g |<PHONE_NUMBER>79 | April 17, 2018April 21, 2018 |
| Denny's Express | Beef & Swiss Submarine | 250 g |<PHONE_NUMBER>30 | Julian date 0718 |


{{ partial "head.html" . }}
404 Not Found
Back to Home
{{ partial "footer.html" . }} {{- partial "footer.html" . -}}


# coding=utf-8
# !/usr/bin/env python
"""
:mod:"serial_labware" -- Generic base class for communicating with lab equipment via serial connection
===================================
.. module:: serial_labware
:platform: Windows
:synopsis: Generic base class to control lab equipment via serial.
.. moduleauthor:: Cronin Group 2017
(c) 2017 The Cronin Group, University of Glasgow
This provides a generic python class for safe serial communication
with various lab equipment over serial interfaces (RS232, RS485, USB)
by sending command strings. This parent class handles establishing
a connection as well as sending and receiving commands.
Based on code originally developed by the Cronin Group.
For style guide used see http://xkcd.com/1513/
"""
# system imports
import platform
import threading
import re
from queue import Queue
from functools import wraps
from time import time, sleep
# additional module imports
import serial
import logging
[docs]def command(func):
"""
Decorator for command_set execution. Checks if the method is called in the same thread as the class instance,
if so enqueues the command_set and waits for a reply in the reply queue. Else it concludes it must be the command
handler thread and actually executes the method. This way methods in the child classes need to be written
just once and decorated accordingly.
:return: decorated method
"""
@wraps(func)
def wrapper(*args, **kwargs):
device_instance = args[0]
if threading.get_ident() == device_instance.current_thread:
command_set = [func, args, kwargs]
device_instance.command_queue.put(command_set)
while True:
if not device_instance.reply_queue.empty():
return device_instance.reply_queue.get()
else:
return func(*args, **kwargs)
return wrapper
[docs]class SerialDevice:
"""
This is a generic parent class handling serial communication with lab equipment. It provides
methods for opening and closing connections as well as a keepalive. It works by spawning a
daemon thread which periodically checks a queue for commands. If no commands are enqueued,
a keepalive method is executed periodically. Replies are put in their own reply queue where
they can be retrieved at any time.
"""
def __init__(self, port=None, device_name=None, soft_fail_for_testing=False):
"""
Initializer of the SerialDevice class
:param str port: The port name/number of the serial device
:param str device_name: A descriptive name for the device, used mainly in debug prints.
:param bool soft_fail_for_testing: (optional) determines if an invalid serial port raises an error or merely
logs a message. Default: Off
"""
# note down current thread number
self.current_thread = threading.get_ident()
# implement class logger
self.logger = logging.getLogger("main_logger.serial_device_logger")
# spawn queues
self.command_queue = Queue()
self.reply_queue = Queue()
# DEBUG testing switch, to allow soft-fails instead of exceptions
self.__soft_fail_for_testing = soft_fail_for_testing
# check if the port passed is of the correct format
if platform.system() == "Windows":
try:
if port[0:3] == "COM" and int(port[3:]) > 0:
self.port = port
else:
# allowing for soft fail in test modes, this will allow an outer script to continue, even if an
# invalid port was passed
if not self.__soft_fail_for_testing:
# in normal use raise an exception to make surrounding python scrips stop
raise (ValueError("The port number ({0}) is not a valid serial port!".format(port)))
else:
# soft-fail error message
self.logger.debug("ERROR: The specified serial port is not valid: {0}".format(port))
except (AttributeError, ValueError) as e:
# self.logger.debug a more descriptive error message before re-raising the exception
self.logger.debug("ERROR: The specified serial port is not valid: {0}".format(e))
# raising the exception again so the surrounding script is aware that this failed
raise # raises the last exception again
else:
# TODO ADD port consistency checks for posix operating systems
raise (OSError(
"You are running a currently unsupported operating system: \"{0}\"".format(platform.system())
))
# device name
self.device_name = device_name
# syntax of a returned answer, to be overridden by child classes
self.answer_pattern = re.compile("(.*)") # any number of any character, in one group
# initialise last time (for non blocking wait
self.last_time = time()
# serial parameters, to be overridden by child classes
self.__connection = None
self.command_termination = '\r\n'
self.standard_encoding = 'UTF-8'
self.baudrate = 9600
self.bytesize = serial.EIGHTBITS
self.parity = serial.PARITY_NONE
self.stopbits = serial.STOPBITS_ONE
self.timeout = 1
self.xonxoff = False
self.rtscts = False
self.write_timeout = None
self.dsrdtr = False
self.inter_byte_timeout = None
self.write_delay = 0 # delay in seconds before sending a command
self.read_delay = 0 # delay in seconds after sending a command
def __command_handler_daemon(self):
"""
Daemon thread for relaying any commands to the device. The "possession" of the serial port and therefore
any actual communication with the device is relegated to its own thread, partially to free up the main
thread for more important stuff, partially to allow for implementation of watchdog keepalive calls,
which would be tremendously tricky to do from the main thread.
This private function polls the command_queue for any commands to send. If no commands are queued,
a keepalive method is executed. Any replies received from the device are enqueued into reply_queue for
further processing.
"""
while True:
try:
if not self.command_queue.empty():
command_item = self.command_queue.get()
method = command_item[0]
arguments = command_item[1]
keywordarguments = command_item[2]
reply = method(*arguments, **keywordarguments)
self.reply_queue.put(reply)
else:
self.keepalive()
except ValueError as e:
# workaround if something goes wrong with the serial connection
# future me will certainly not hate past me for this...
self.logger.critical(e)
self.__connection.flush()
# thread-safe purging of both queues
while not self.command_queue.empty():
self.command_queue.get()
while not self.reply_queue.empty():
self.reply_queue.get()
[docs] def launch_command_handler(self):
command_handler = threading.Thread(target=self.__command_handler_daemon, name="{0}_command_handler".format(self.device_name), daemon=True)
command_handler.start()
[docs] @command
def open_connection(self):
"""
Opens the serial connection to the device.
If a connection is already open it is closed and then a connection is re-established with the current settings
"""
if self.__connection is not None and self.__connection.isOpen():
self.logger.debug("Already connected. Closing connection and re-establishing with parameters given.")
self.close_connection()
self.__connection = None
try:
self.__connection = serial.Serial(
port=self.port,
baudrate=self.baudrate,
bytesize=self.bytesize,
parity=self.parity,
stopbits=self.stopbits,
timeout=self.timeout,
xonxoff=self.xonxoff,
rtscts=self.rtscts,
write_timeout=self.write_timeout,
dsrdtr=self.dsrdtr,
inter_byte_timeout=self.inter_byte_timeout
)
return True # announce success
except (AttributeError, FileNotFoundError, serial.SerialException) as e:
# allowing for soft fail in test modes, this will allow an outer script to continue, even if an
# invalid port was passed
if not self.__soft_fail_for_testing:
# in normal use just raise exception again
raise
else:
# soft-fail error message
self.logger.debug("ERROR: The connection to the serial device could not be established: {0}".format(e))
return False # announce failure
[docs] @command
def close_connection(self):
"""
Attempts to close the serial connection if one is open.
"""
if self.__connection is not None:
self.__connection.close()
return True # announce success
else:
return False # announce failure
[docs] def send_message(self, message, get_return=False, return_pattern=None, multiline=False):
"""
Method for sending messages to the device. This method needs to be publicly accessible, otherwise
child classes can't use it. This method does not do a consistency check on the arguments passed to it,
since they may vary wildly. Therefore such a check must be performed before calling send_message!
Args:
message (str): The message string. No checks are performed on the message and it is just passed on
get_return (bool): Are you expecting a return message?
return_pattern (_sre.SRE_Pattern): Passes on a regex pattern to check the returned message against
multiline (bool): Are you expecting a return message spanning multiple lines?
(not evaluated if get_return is False)
Returns:
(conditional)
- returns "True" if no message is expected back
- does a call back to "__receive_message" and passes on "the return pattern"
- returns -1 if send message fails
"""
# send the message and encode it according to the standard settings found in __init__
# Hint: "{}".format(message) auto converts message to string in case it was something else, so no type checking
if self.__connection is not None:
try:
sleep(self.write_delay)
# self.__connection.flush() # get rid of shite from the last transmission
self.__connection.write(
"{0}{1}".format(message, self.command_termination).encode(self.standard_encoding)
)
sleep(self.read_delay)
except Exception as e:
if not self.__soft_fail_for_testing:
# just raise the exception again when not in test mode
raise
else:
self.logger.debug("Error: Unexpected error while writing to serial. Error Message: {0}".format(e))
# if the user specified that a return message is expected
if get_return:
# call back to __receive_message and passing on of the expected regex pattern
return self.__receive_message(return_pattern=return_pattern, multiline=multiline)
else:
# just return True of no response is expected
return True
else:
self.logger.debug("Could not send message: no connection to serial device established.")
return -1
def __receive_message(self, return_pattern=None, multiline=False):
"""
Protected member function that is the sole responsible for actually receiving messages from the device.
This isn't exactly the pythonic way of doing thing (protected member functions should be _ not __).
However, two leading __ actually prevents the function to be called from the outside (as opposed to just
raising a flag says "you're accessing a protected member function".
Pro-Tip: (due to Python weirdness) A savvy user can still gain access to thus protected functions via
{InstanceName}._{ClassName}__{FunctionName}
Args:
return_pattern (_sre.SRE_Pattern): Passes on a regex pattern to check the returned message against
multiline (bool): Are you expecting a return message spanning multiple lines?
Returns:
answer (str or list of str): If no return pattern is specified, the stripped answer string is returned. If
a pattern is passed, a list of the captured groups is returned instead
"""
try:
# checking if a connection is there
if self.__connection is not None:
# if multiple lines are expected, keep reading lines until no more lines come in
if multiline:
answer = ""
while True:
line = self.__connection.readline()
if line:
answer += line.decode(self.standard_encoding)
else:
break
# if just one line is expected, just read one line (faster than always waiting for the timeout)
else:
answer = self.__connection.readline()
# decoding the answer using the standard settings from __init__
answer = answer.decode(self.standard_encoding)
# if the user wants a code check performed
if return_pattern is not None:
if type(return_pattern).__name__ != "SRE_Pattern":
raise ValueError(
"The return code you specified was not a valid regular expression: {0}".format(return_pattern)
)
if re.fullmatch(pattern=return_pattern, string=answer):
# if the answer matches the desired pattern return the read value
return re.match(pattern=return_pattern, string=answer).groups()
else:
self.logger.critical(
"Value Error. Serial device did not return correct return code. Send: \"{0}\". "
"Received: \"{1}\".".format(return_pattern, answer)
)
if self.__soft_fail_for_testing:
return answer.strip()
else:
raise ValueError(
"Value Error. Serial device did not return correct return code. Send: \"{0}\". "
"Received: \"{1}\".".format(return_pattern, answer)
)
else:
# if no return code checking was requested, just return the read value
return answer.strip()
else:
raise Exception("Error. No connection to the device")
except Exception as e:
# This is not very elegant, but lets the user know that the device failed while retaining the error
# information
raise Exception("Serial device message receive failed. Error Message: {0}\n{1}".format(e, e.__traceback__))
[docs] def non_blocking_wait(self, callback, interval):
"""
Simple non-blocking wait function crafted after the Arduino Blink Without Delay example. Checks whether the
time elapsed since the last callback is greater than or equal to the interval. If so, the callback method
is returned and the time updated.
:param callback: function or method to be executed
:param int interval: wait time in seconds
:return: callback if interval has elapsed, None otherwise
"""
if time() >= (self.last_time + interval):
self.last_time = time()
return callback()
else:
return None
[docs] def keepalive(self):
"""
Dummy keepalive method. This is just a stand-in for whatever keepalive operation needs to be performed
on the device, meant to be overridden in the actual child class.
"""
pass


In City Press Business: SAA on brink of collapse; Dubai wants to boost trade with Africa
SAA on the brink of collapse
Regardless of the bailout from government, the national carrier may not be able to avoid being placed under business rescue.
Following a crippling R50m a day strike this week, the airline is facing a challenge from Solidarity which seeks to place the airline in rescue.
Where to save R600 a month?
If you have the cash to spare, there are several options open to grow your money. Maya Fisher-French answers this and other reader questions.
Dubai wants to boost trade with Africa
We all know that China and Russia have vested interest in large infrastructure projects in Africa. The United Arab Emirates have also expressed a willingness to invest on the continent – but in smaller enterprises to grow their exposure to the world.
Saving water in silos
As the country gets deeper into the grip of drought, Aqua Silos wants to turn those ubiquitous grain silos into purification and storage facilities to lift the pressure from small towns.


Please read the documentation (starting with the General Instructions) before asking questions. I'm happy to help out, but it's so much nicer when folks read the documentation.
| Function Name | Short Description | Introduced | Certification |
|---|---|---|---|
| $().SPServices | This is the core function of the library, which you can use to make Ajax calls to the SharePoint Web Services. Note: As of version 2013.01, all calls return a jQuery deferred object aka a promise. | 0.2.3 | See individual Web Services |
| $().SPServices.defaults | With this defaults function, you can set the defaults for the remainder of the page life. This can be useful if you'd like to make many calls into the library for a single list or site. | 0.2.4 | NA |
| $().SPServices.Version | Returns the current version of SPServices as a string, e.g., "0.7.2" | 0.7.2 | NA |
| Function Name | Short Description | Introduced | SharePoint 2010 |
|---|---|---|---|
| $().SPServices.SPCascadeDropdowns | This is the first function we implemented which allows you to take advantage of the Web Services calls in a meaningful way. It allows you to easily set up cascading dropdowns on a list form. (What we mean by cascading dropdowns is the situation where the available options for one column depend on the value you select in another column.) | 0.2.6 | |
| $().SPServices.SPDisplayRelatedInfo | This function lets you display related information on forms when an option in a dropdown is chosen. | 0.2.9 | |
| $().SPServices.SPLookupAddNew | This function allows you to provide a link in forms for Lookup columns so that the user can add new values to the Lookup list easily. It is based on a blog post by Waldek Mastykarz. (see Credits) | 0.3.2 | |
| $().SPServices.SPRedirectWithID | This function allows you to redirect to a another page from a new item form with the new item's ID. This allows chaining of forms from item creation onward. | 0.4.0 | |
| $().SPServices.SPRequireUnique | Checks to see if the value for a column on the form is unique in the list. | 0.4.0 | |
| $().SPServices.SPSetMultiSelectSizes | Sets the size of the boxes in a multi-select picker based on the values they contain. | 0.4.8 | |
| $().SPServices.SPArrangeChoices | Rearranges radio buttons or checkboxes in a form from vertical to horizontal display to save page real estate. | 0.5.0 | |
| $().SPServices.SPAutocomplete | The SPAutocomplete lets you provide values for a Single line of text column from values in a SharePoint list. The function is highly configurable and can enhance the user experience with forms. | 0.5.4 | |
| $().SPServices.SPUpdateMultipleListItems | SPUpdateMultipleListItems allows you to update multiple items in a list based upon some common characteristic or metadata criteria. | 0.5.8 | |
| $().SPServices.SPFilterDropdown | The SPFilterDropdown function allows you to filter the values available in a Lookup column using CAML against the Lookup column's source list. | 0.6.1 | |
| $().SPServices.SPComplexToSimpleDropdown | Converts a "complex" dropdown (which SharePoint displays if there are 20+ options) to a "simple" dropdown (select). | 0.6.2 | |
| $().SPServices.SPFindPeoplePicker | The SPFindPeoplePicker function helps you find and set People Picker column values. | 0.7.2 | |
| $().SPServices.SPFindMMSPicker | The SPFindMMSPicker function helps you find an MMS Picker's values. | 2013.01 |
| Function Name | Short Description | Introduced | SharePoint 2010 |
|---|---|---|---|
| $().SPServices.SPGetCurrentSite | This utility function, which is also publicly available, simply returns the current site's URL. It mirrors the functionality of the WebUrlFromPageUrl operation. | 0.2.4 | |
| $().SPServices.SPDebugXMLHttpResult | This function displays the XMLHttpResult from an Ajax call formatted for easy debugging. You can call it manually as part of your completefunc. | 0.2.10 | |
| $().SPServices.SPGetCurrentUser | This function returns information about the current user. It is based on an insightful trick from Einar Otto Stangvik (see Credits). | 0.3.1 | |
| $().SPServices.SPGetLastItemId | Function to return the ID of the last item created on a list by a specific user. Useful for maintaining parent/child relationships. | 0.4.0 | |
| $().SPServices.SPGetDisplayFromStatic | This function returns the DisplayName for a column based on the StaticName. | 0.4.0 | |
| $().SPServices.SPGetStaticFromDisplay | This function returns the StaticName for a column based on the DisplayName. | 0.5.4 | |
| $().SPServices.SPScriptAudit | The SPScriptAudit function allows you to run an auditing report showing where scripting is in use in a site. | 0.4.8 | |
| $().SPServices.SPGetQueryString | The SPGetQueryString function returns an array containing the Query String parameters and their values. | 0.5.1 | |
| $().SPServices.SPListNameFromUrl | Returns the current list's GUID if called in the context of a list, meaning that the URL is within the list, like /DocLib or /Lists/ListName. | 0.5.7 | |
| $().SPFilterNode | Can be used to find namespaced elements in returned XML, such as rs:data or z:row from GetListItems. | 0.7.0 | |
| $().SPXmlToJson | SPXmlToJson is a function to convert XML data into JSON for client-side processing. | 0.7.1 | |
| $().SPServices.SPConvertDateToISO | Convert a JavaScript date to the ISO 8601 format required by SharePoint to update list items. | 2013.01 | |
| $().SPServices.SPGetListItemsJson | SPGetListItemsJson combines several SPServices capabilities into one powerful function. By calling GetListItemChangesSinceToken.aspx), parsing the list schema, and passing the resulting mapping and data to SPXmlToJson automagically, we have a one-stop shop for retrieving SharePoint list data in JSON format. No manual mapping required! | 2014.01 | |
| $().SPServices.SPDropdownCtl | The function finds a dropdown in a form based on the name of the column (either the DisplayName or the StaticName) and returns an object you can use in your own functions. | 2014.01 |


Welcome to BasicDev
My name is Cliff Richard Anfone. For more inquiries, please email me at
anfone.cliff@gmail.com


Coastal Inundation Forecast Demostration Project (CIFDP)
High Resolution
Inundation
Forecast
click me, I make a modal
×
© 2021 Geoscience, Energy and Maritime Division, Pacific Community (SPC)


Problems Pool
- Share a Coding Interview problem
- To enter blocks of code place your code between ``` Block Code ```
- Ask any question Computer Science related
Select a Tag
Strings
Arrays
Lists
Stacks
Queues
Trees
Graphs
Dynamic Programming
Divide and Conquer
Loading...


Simplify to lowest terms.
\dfrac{NUM}{DENOM}
NUM / DENOM
There are several ways to tackle this problem.
What is the greatest common factor (GCD) of NUM and DENOM?
NUM = getPrimeFactorization( NUM ).join( "\\cdot" )
DENOM = getPrimeFactorization( DENOM ).join( "\\cdot" )
\mbox{GCD}(NUM, DENOM) = GCD_FACTORS.join( "\\cdot" ) = GCD
\dfrac{NUM}{DENOM}
= \dfrac{NUM / GCD \cdot GCD}{ DENOM / GCD\cdot GCD}
\hphantom{\dfrac{NUM}{DENOM}}
= \dfrac{NUM / GCD}{DENOM / GCD} \cdot \dfrac{GCD}{GCD}
\hphantom{\dfrac{NUM}{DENOM}}
= \dfrac{NUM / GCD}{DENOM / GCD} \cdot 1
\hphantom{\dfrac{NUM}{DENOM}}
= \dfrac{NUM / GCD}{DENOM / GCD}
You can also solve this problem by repeatedly breaking the numerator and denominator into common factors.
For example:
HINT


--- # jekyll header --- {% include header.html %} {% include container-start.html %}
| AdverseEvent | {% include qicore-adverseevent-ex.html %} |
| AllergyIntolerance | {% include qicore-allergyintolerance-ex.html %} |
| BodySite | {% include qicore-bodysite-ex.html %} |
| Claim | {% include qicore-claim-ex.html %} |
| Communication | {% include qicore-communication-ex.html %} |
| CommunicationRequest | {% include qicore-communicationrequest-ex.html %} |
| Condition | {% include qicore-condition-ex.html %} |
| Coverage | {% include qicore-coverage-ex.html %} |
| Device | {% include qicore-device-ex.html %} |
| DeviceUseStatement | {% include qicore-deviceusestatement-ex.html %} |
| DiagnosticReport | {% include qicore-diagnosticreport-ex.html %} |
| Encounter | {% include qicore-encounter-ex.html %} |
| FamilyMemberHistory | {% include qicore-familymemberhistory-ex.html %} |
| Flag | {% include qicore-flag-ex.html %} |
| Goal | {% include qicore-goal-ex.html %} |
| ImagingStudy | {% include qicore-imagingstudy-ex.html %} |
| Immunization | |
| ImmunizationRecommendation | {% include qicore-immunizationrec-ex.html %} |
| Medication | {% include qicore-medication-ex.html %} |
| MedicationAdministration | {% include qicore-medicationadministration-ex.html %} |
| MedicationDispense | {% include qicore-medicationdispense-ex.html %} |
| MedicationRequest | {% include qicore-medicationrequest-ex.html %} |
| MedicationStatement | {% include qicore-medicationstatement-ex.html %} |
| Observation | {% include qicore-observation-ex.html %} |
| Organization | {% include qicore-organization-ex.html %} |
| Patient | {% include qicore-patient-ex.html %} |
| Practitioner | {% include qicore-practitioner-ex.html %} |
| Procedure | {% include qicore-procedure-ex.html %} |
| ProcedureRequest | {% include qicore-procedurerequest-ex.html %} |
| ReferralRequest | {% include qicore-referralrequest-ex.html %} |
| RelatedPerson | {% include qicore-relatedperson-ex.html %} |
| Specimen | {% include qicore-specimen-ex.html %} |
| Substance | {% include qicore-substance-ex.html %} |


/**
* Implements a new Storage type that has the same api as Storage (local, session) except for key().
* Due to compatibility issues with IE, the size property is implemented instead of length.
*
* @summary server-environment
* @version 1.0.0
* @author Arian Khosravi<EMAIL_ADDRESS>* @memberof module:aofl-js/cache-manager-package
*/
class MemoryStorage {
/**
* The clear() method of the Storage interface, when invoked, clears all stored keys.
*/
static clear() {
for (const key in MemoryStorage) {
/* istanbul ignore else */
if (MemoryStorage.hasOwnProperty(key)) {
MemoryStorage.removeItem(key);
}
}
}
/**
* The length read-only property of the Storage interface returns an integer representing the
* number of data items stored in the Storage object.
*
* @readonly
*/
static get size() {
let length = 0;
for (const key in MemoryStorage) {
/* istanbul ignore else */
if (MemoryStorage.hasOwnProperty(key)) {
length++;
}
}
return length;
}
/**
* The getItem() method of the Storage interface, when passed a key name, will return that key's
* value or null if the key does not exist.
*
* @param {String} key The name of the key you want to retrieve the value of.
* @return {*}
*/
static getItem(key) {
/* istanbul ignore else */
if (MemoryStorage.hasOwnProperty(key)) {
return MemoryStorage[key];
}
return null;
}
/**
* The setItem() method of the Storage interface, when passed a key name and value, will add
* that key to the storage, or update that key's value if it already exists.
*
* @param {*} key The name of the key you want to create/update.
* @param {*} value The value you want to give the key you are creating/updating.
*/
static setItem(key, value) {
MemoryStorage[key] = value;
}
/**
* The removeItem() method of the Storage interface, when passed a key name, will remove that key
* from the storage if it exists. If there is no item associated with the given key, this method
* will do nothing.
*
* @param {String} key The name of the key you want to remove.
*/
static removeItem(key) {
MemoryStorage[key] = null;
delete MemoryStorage[key];
}
};
export default MemoryStorage;
|


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.
BEFORE THE NATIONAL GREEN TRIBUNAL EASTERN ZONE BENCH:KOLKATA ------------- APPLICATION NO.60 OF 2012 AND M.A.NO.73 OF 2013 In the matter of: Murli Manohar Sharma S/O Tarachand Sharma PO./PS. Barbil ,Distt.Keonjhar ,Odisha ---------- Applicant VERSUS 1. Union of India Represented through the Secretary Ministry of Environment and Forests C.G.O.Complex ,Lodhi Road New Delhi-110510 2. State of Odisha Represented through its Principal Secretary Water Resource Department Secretariate Building ,Bhubaneswar Distt. Khurdha- 751001 3. Collector-cum-District Magistrate ,Keojhar PO/Distt. Keonjhar ,Odisha-758001 1 4. M/S Brahmani River Pellets Ltd. IPICOL Annex Building ,5 & 6th Floor Janpath ,Bhubaneswar Distt. Khurdha ,Odisha-751002 5. M/S Essar Steel Orissa Ltd. 5-B/2 ,Fortune Tower ,Chandrasekharpur Bhubaneswar ,Distt.Khurdha Odisha -751016 6. M/S Jindal Steel and Power Ltd. Jindal Centre 12,Bhicaji Cama Place New Delhi- 110066 ----------- Respondents Counsel for Applicant Mr.Raj Panjwani ,Mr.G.Pujari ,Mr.Bibhu Prasad Tripathy , Mr.Sanjay Upadhaya and Ms Manisha Badoni - Advocates Counsel for Respondent Ms.Neelam Rathore , Mr.Vikramjeet ,Ms.Syed Ambar ,Mr.Vikash Malhotra and Mr.M.P.Sahay - Advocates for Respondent 1 2 Mr.Abhisek Sharma ,Mrs C.K.Sucharita ,Mr.Ashok Kumar Panigrahi ,Mr.Surjit,Mr.S.K.Das and Mr. Ashmi Mohan - Advocates for Respondent 2 Mr.Ashok Kumar Panda ,Mr.S.Panda ,Mr.L.Sarangi and Mr.S.K.Das - Advocates for Respondent 3 Mr.P.S.Narsimha ,Mr.Amar Gupta ,Mr.Gyaneswar ,Mr.Apoorva Mishra , Mr.Vishrov Mukheerjee and Ms.Vandana Ananda -Advocates for Respondent 4 JUDGMENT
PRESENT Hon'ble Mr. Justice Dr.P.Jyothimani (Judicial Member) Hon'ble Prof.(Dr.) P.C.Mishra (Expert Member) __________________________________________________________ Dated 5th August 2014 _________________________________________________________ JUSTICE DR. P. JYOTHIMANI (JUDICIAL MEMBER)
1. The applicant who is stated to be a public spirited person ,has filed the present application,praying for a declaration that the changing of natural flow and course of Baitarani River by respondents 4 to 6 is illegal with a further direction to the State Govt. to ensure that the 3 natural flow of water in the above-said river is not obstructed by any one including the said respondents. That apart ,he has also asked for setting aside the letters issued by the 2nd respondent no 4231 dt 11-02-2009, no.34127 dt 24-12-2009 & no.28834 dt 26-8-2008 in favour of respondents 3 to 6 respectively. It is the case of the applicant that Baitarani river originates from Guptaganga hills in Keonjhar District of Odisha. The Baitarani ,along with Mahanadi and the Brahmani forms the Middle Coastal Plain. According to the applicant,Baitarani is the only robust source of water in the district, providing 95% of drainage of the district and the lifeline of the people, land and its ecology.
2. It is further the case of the applicant that the water of Baitarani is required for various projects like the Kanupur Major Irrigation roject for irrigation of 48000 acres of lands, Anandapur Irrigation Barrage to irrigate 150,000 acres of lands in the north Odisha coastal areas, many minor irrigation projects, domestic water supplies to 8 urban complexes apart from many water-based industries.While so, the 4th respondent ,M/S Baitarani River pellets Ltd. proposed to construct 4 .0 MTPA iron ore beneficiation plant at Tanto village and a tailing dam at Nalda in Barbil Tahsil of Keonjhar District. A joint venture agreement was entered with government of Odisha on 15-03-2007.The beneficiation plant will be connected by 220 km underground slurry pipes to a 4 million tonnes per annum pellet plant under construction at Kalinga Nagar in Jajpur District, where the ore slurry will be balled 4 and fired in to pellets.
3. Likewise according to the applicant, the 5th respondent (M/S Essar Steel Orissa Ltd. with a view to establish customized steel plants, has proposed to set up a 10.7 MTPA capacity iron ore beneficiation plant and tailing pond at Dubuna of Joda in Keojhar District. Likewise ,the 6th respondent also proposed a pellet plant of 10.00 MTPA at Deojhar of District Keonjhar. An MOU is also stated to have been entered with the government of Odisha.
4. Similarly , the Respondent 6 , M/S Jindal Steel and Power has proposed a Pellet Plant of 10.0 MTPA capacity at Deojhar of Barbil Tahasil in the Distrct Keonjhar ,odisha along with a 9.0 MTPA beneficiation Plant .MOU for such projects was signed between the Respondent 6 and the Government of Odisha on 3.11.2005
5. It is stated by the applicant that the 2nd respondent has allowed the Respondents 4 to 6 to draw water from Baitarani River for their plants.By the impugned letter dt11-02-2009,the 4th respondent was allowed to draw 4.70 cusecs of water ,while respondent 5&6were allowed 11.77 & 8.33 cusecs under the impugned letters dt.24-12-2009 & 26-08-2008.
6. According to the applicant, the EIA report of the 4th respondent shows that the minimum flow of water in river Baitarani during lean season namely,December ,February,March ,April is less than 0.5m3/s ,while 5 respondent 4 proposes to draw water @ 0.134m3/s for its beneficiaton plant and 0.087m3/s for tailing plant for the project.In addition to that, water intake well and pumping station are to be provided on the banks of the said river and it is transported through 220 km long underground slurry pipe line to the beneficiation plant.As per the MOU, the water requirement of the 4th respondent is 480 m3/hr(0.134m3/s) as per EIA Report. Likewise, in respect of the 5th respondent,as per its EIA Report the water requirement is 731m3/hr.i.e 6403560 m3/year. Out of this 666m3/hr will be sent to Paradeep Beneficiation Plant in the form of underground slurry pipeline of 260 km.Again in respect of the 6 th respondent as per its EIA Report,the total water requirement of water is 350kl/hr . According to EIA report of Respondent 6 the average water flow in the lean months is around 4.56m3/s where as EIA report of Respondent 4 states as 0.5 m3/s.
7. According to the applicant ,the EIA reports of the respondents 4 to 6 are not uniform and contradictory and can not be trusted.Further,as per the the EIA Notification of the Ministry of Environment and Forests dated 14-09-2006,the projects being treated under category A of the Schedule , it requires prior Environmental Clearance. Therefore, the conduct of the respondent no 4&5 in unauthorizedly laying pipe lines in the reserve forest is illegal.The said illegal conduct has been deprecated by the District Collector who,by his letter dated 04-08-2012,has directed the said respondents to stop further laying of pipe lines. The applicant also relies upon a study conducted by Arnaud Cauchois and 6 Asian Development Bank on Baitarani River Basin, which has estimated dependable flow of water from surface water at 5149.47 million cubic meters out of which 46% are used for irrigation, drinking and industrial purposes and therefore the scarcity of water is bound to increase and in such circumstances it is not advisable for the respondents to permit further release of water to respondents 4 to6. It is also the case of the applicant that even as per the Odisha State Water Policy,2007, in case there is public-private participation in water resource development care will be taken to ensure that the riparian and traditional rights of the local communities are adequately protected .He would submit that the public hearing held on 25-03-2008 at Barbil has failed to consider about the riparian rights of the local people.It is also the case of the applicant that in the public hearing ,sufficient number of people have not participated except 96 persons and therefore public hearing was only a farce. It is also stated that the Zilla Parishad ,in the meeting held on 01-02-2010 has opposed the drawal of water by any company from upstream of the river.
8. Thus ,the applicant questioned the rights given to the said respondents on various grounds including the followings, i. that the drawal of such water will affect its natural flow and affect the steady supply of water to the villagers ii. that the conduct of respondents 4&5 in laying pipelines even before grant of permission is illegal 7 iii. that by excess drawal of water ,there is a possibility alteration of the natural flow of the river water iv. that the state government has failed to adhere to its water policy v that there was no consultation the Baitarani RBO for conflict resolution vi. that the common heritage of the people was ignored and that it involves public interest.
9. Before adverting to the reply by the respondents, it is relevant to note that when the matter came up for admission, this Tribunal in the order dated 21-11-2012 has recorded the statement of the learned counsel for the Applicant, Mr Tripathi that he is restricting in this case only against the 4th respondent,as he has realized that one application is not maintainable against all the respondents 4 to 6 as cause of action are different.. Accordingly,in the said order, the names of respondent no 5&6 are directed to be deleted. Therefore in this case admittedly we are dealing with only respondent no. 4 as the project proponent.
10. The 1st respondent MoEF,in its reply, has stated that the EIA report in respect of the 4th respondent has been prepared by the project proponent in accordance with the EIA Notification 2006 and the Terms of Reference (TOR) prescribed by the MoEF. It is also stated that the EIA Report was prepared by the accredited EIA (Environment Impact Appraisal) Consultant , for consideration for the issuance of Environmental Clearance. According to the first respondent, the 8 Environmental Appraisal Committee (EAC) has unanimously recommended for issuance of Environmental Clearance for the 4th respondent. It is also stated that the permission for drawal of water is granted by the Department of Water Resources of the State Government.The MoEF is only concerned about the monitoring and protection of riparian system, if the quantity of drawal of water is huge.The MoEF,states that Environmental Clearance was granted to the 4th respondent on 19-02-2009 imposing certain specific conditions. It is the further case of the 1st respondent, that there was no complaint received against the 4th respondent of any violation of EC conditions. The MoEF is also monitoring the 4th respondent through its Regional Office and in case of any violation action under Environment Protection Act 1986 will be initiated.It is also stated by the 1st respondent that as per conditions of clearance, if there is a proposal for diversion of forest land, necessary permission must be obtained under the Forest (Conservation) Act 1980 . As the environment clearance in this case has been granted as early as on 19-02-2009, which is much before the coming in to force of the National Green Tribunal Act 2010 which is effective from 18-10-2010,the issue can not be raised before this Tribunal.
11. The respondent no. 2,State of Odisha, through its Chief Engineer, has filed its reply stating that the procedure for allocation of water has been strictly followed as laid down by the Odisha Irrigation(Amendment) Rules 2010.It is stated that the fourth 9 respondent Company has applied to the Government, the Dept. Of Water Resources ,for allocation of water in the prescribed form along with the processing fees and security deposit.The application was sent to the Water Allocation Committee(WAC) which after careful consideration of the views of the Chief Engineer and the Basin Manager has recommended the case and accordingly the engineer-in -chief, Water Resources recommended to the Government for allocation of water for the fourth respondent plant.Accordingly, the fourth respondent has entered an agreement in the prescribed form with the concerned Executive Engineer for drawal of water. It is also the case of the second respondent Government of Odisha that in Keonjhar District there are about 151 minor irrigation projects with the CCA of 27,553Ha (68,056Ac) and about 592 Lift Irrigation points with annual irrigation of 8680 Ha (21,440 Ac) and the total CCA is 36,233 Ha(89496Ac). It is further stated that Baitarani Basin provides domestic water supply to about 15 Urban Complexes, in addition to riparian rights along its 360 Km length.It is stated that the transportation of Iron Ores in the form of slurry through pipelines reduces pollution . It is the categoric stand of the second respondent that the fourth respondent has not constructed any '' intake wall" till date ,except installing one movable JIB crane near the bank of river Baitarani at the intake point to help drawing water from the river.It is also stated that three pounds of 37KW, two working and one standby with the discharge capacity of 250 cum have been fixed to the JIB crane to deliver the approved drawal of 480 Cum. Thus the State Govt denies the allegation that it has 10 failed to adhere to the concept of water-plan. It is stated that action is being taken for effective, efficient, equitable and sustainable management of water resources of the State.
12. The third respondent, the District Collector, in his reply, while denying the allegation raised by the applicant and adopting the reply filed by the State Government has admitted that by a letter dated 4.08.2011 the fourth respondent was directed to stop laying of slurry pipelines and the construction work of beneficiation plant over non-forest land till final order is obtained under the Forest (Conservation)Act. The Central Government has granted 1st stage clearance to the fourth respondent on 2.11.2011 followed by the stage-II Forest Clearance on 9.07.2012. It is stated that on 17.08.2012 permission was granted to lay pipeline and the State Pollution Control Board has issued consent to operate to the fourth respondent on 24.11.2012.It is also the case of the third respondent that for establishing the plant by the fourth respondent ,hearing is mandatory, By a notification dated 19.02.2008, the Odisha State Pollution Control Board, Bhubaneswar has issued a public notice for a public hearing relating to the establishment of beneficiation plant of 4.08 Million Tonne per annum capacity at village-Tanto and Tailing Dam at Nalda under Barbil Tahsil of Keonjhar District, Odisha. It is stated that public hearing was held on 25.03.2008 at Vikas Mahal, Barbil of Keonjhar and the proceedings were released. In the said meeting, large number of local people have participated and given opinion about the fourth respondent's project 11 which were highly favourable to the plant, except some local people who required certain facilities like drinking water, medical facilities, educational facilities, employment, peripheral development , vocational training etc. in the village-Nalda.In accordance with the said public hearing. Government of India, Ministry of Forest and Environment has also issued Environment Clearance on 19.02.2009.
13. The fourth respondent project proponent, in its reply while admitting the project of the said respondent, has stated that the proposal of the project to process iron-ore fines, which are low grade iron ore fines which otherwise cannot be used in the steel industry , can be converted to high grade concentrate and used only for pelletization for further use in the steel making process. The project envisage use of unusable materials into usable products with the benefits of better utilization of mineral resources in India and facilitate mineral conservation, reduce high grade iron-ore mining which benefits the environment and that it reduces environmental impact. It is the further case of the project proponent that many environmental friendly measures relating to the projects for conservation of water have been taken including use of underground slurry pipeline instead of road and rail transport and there is totally negligible pollution and therefore the project is pollution free, that the transportation of slurry comprising of 70% solids creates no noise, no dust, no smell, that the transportation of slurry does not involve use of diesel, that the water drawn by the beneficiation plan is recycled for re-use in the slurry pumping and that water from river 12 Baitarani will be used only during the non-lean period and for the remaining period water is used from the reservoir built up by the fourth respondent itself.
14. It is stated by the fourth respondent that as per the Memorandum of Understanding entered between the Government and the project proponent dated 15.03.2007, the second respondent has to identify suitable water-source from river Baitarani for drawal of water to meet the requirement of the project. And in-principle approval was granted to the project proponent for laying iron-ore slurry pipeline on 13.06.2007.The Odisha Infrastructure Development Corporation, a Govt. of Odisha Undertaking applied to the Chief Conservator of Forests, Odisha on 5.07.2007 on behalf of the project proponent for diversion of
27. 098 Ha of forest land for establishing the beneficiation plant.It is stated that on 19.07.2007, the project proponent obtained permission for laying pipeline along the State Highway. The State Pollution Control Board has granted consent to establish on 29.08.2007. On 7.12.2007 the Chief Engineer, National Highways granted permission for laying pipeline along NH-215. The Dept. of Water Resources of the State Govt has allocated 4.70 cusecs of water from river Baitarani on 11.02.2009 with various conditions. On 19.02.2009, the Ministry of Environment and Forests, Government of India granted environment clearance with various conditions. On 18.03.2009, the project proponent has resubmitted its proposal for diversion of forest land.An agreement was entered by the project proponent and the Governor of 13 Odisha through the Executive Engineer on 14.10.2009 to draw 4.70 cu-secs of water from river Baitarani. The Forest Range Officer, Barbil has sent a notice on 27.06.2011 to the project proponent to stop work in and around forest area till forest clearance is received for diversion of forest land.The Government of India has granted stage-I Forest Clearance on 2-11-2011 followed by the stage-II clearance for the beneficiation plant on 09.07.2012 and for the pipeline on 17.08.2012.Thereafter the State Pollution Control Board has issued consent to operate on 24.11.2012. It is further stated that on 07.12.2012 the agreement for supply of water from the river was renewed for a further period of 3 years.
15. The Fourth respondent has raised a preliminary objection about the maintainability of the application. It is their case that the order challenged by the applicant in so far as it relates to the fourth respondent dated 11.02.2009 which is prior to the coming into force of the National Green Tribunal 2010. Further the issue involved do not pertain to any of the Statutes enumerated in Schedule I of the NGT Act. That apart ,the application is barred by limitation and is without merit, filed only to coerce the fourth respondent. The water permitted to be drawn from the river by the State Government is as per the Orissa Irrigation Act, 1959. Even otherwise according to the applicant, an order passed on 11.02.2009 is challenged in November 2012 which is even beyond the permissible discretionary power of the Tribunal to condone the delay. In addition to that it is the case of the project 14 proponent that the applicant has admitted about his knowledge of the project even as early as 2010-11 when his brother was arrested for arson and destruction of property belonging to the contractor who was carrying on work on the spot of the project carried on behalf of the project proponent. Further the applicant has given many statements about the project which show that even in the year 2010, he was aware of this project and in-spite of it, he has not explained as to why he has chosen to approach the Tribunal in November 2012 .The NGT Act, has come into existence on 18.10.2010 while the second respondent has granted permission to draw water from river Baitarani on 11.02.2009. According to the applicant, even if the said order has to be challenged, the same can be only as an appeal u/s. 16 of the Act and therefore the said application is not maintainable.It is further stated that the matter which is directly and substantially in issue in the present application is already pending in the Writ Petition No. 9118/2010 before the Orissa High Court. Therefore this application is not maintainable.The project proponent while denying all other allegations raised by the applicant would state that the project proponent has followed all the procedures established by law and environmental clearance has been obtained after following every steps formulated by EIA regulation, 2006 framed by the Ministry of Environment and Forests, Government of India apart from obtaining consent to operate from the State Pollution Control Board. Therefore the project proponent prays for dismissal of the Main Application NO. 60 of 2012.
1516. Before adverting to the submission made by the learned counsel, it is relevant to mention a few of the facts which mostly relate to the order passed by this Tribunal. On 21-11-2012,while directing the deletion of the 5th and 6th respondent as stated earlier in this order,the Tribunal has directed the 4th respondent not to go ahead with construction of the project without obtaining environment clearance. It was on 04-02-2013,the applicant has filed M.A.No13 and 14/2013 for a direction to the Collector to ensure the compliance of the said order and to punish the 4th respondent for disobeyance of the order.On 04-03-2013, this Tribunal,on a representation of of the learned counsel for the applicant has dismissed M.A.No14/2013 as withdrawn with liberty. The order is as follows:
"M.A. No. 14 of 2013 in Application No.60 of 2012 Learned counsel appearing for Respondent No. 4 Submits that he has preliminary objections as regards the limitation as well as maintainability of this Application.
Liberty is granted to raise objections to the appropriate Application when the said Application is called for hearing. List this matter on 18th March,2013.
The matter shall be heard on the next date of hearing.'
17. In pursuant to the said order, the applicant has filed M.A.No73 of 2013 ,on14-03-2013 ,praying for amending the prayer in the original application, seeking for a direction to the 4th respondent not to obstruct the natural flow of water in the river,to set aside the letter dated 16 11-02-2009 and a subsequent letter dated 28-01-2013,renewing the water agreement, to direct the 4th respondent to reconstitute the natural flow of water in Baitarani River,to direct the 2nd respondent to consult with Baitarani RBO regarding conflict resolution and consensus building and riparian rights of local people,to set aside the Forest Clearance granted by respondent no. 1 dated09-07-2012 and 17-08-2012 in favour of the 4th respondent. This application was opposed by the project proponent in its reply ,stating that ,while the main application itself is not maintainable, there is no question of taking up the amendment application at this stage,that by virtue of the proposed amendment,the applicant attempt to change the entire cause of action raised by him in the original application,that even if the applicant wants to challenge the Forest Clearance ,the same can be only by way of appeal, which is also hopelessly time barred and that this Tribunal has no jurisdiction to condone such a large number of days delay.
18. The 4th respondent , project proponent has also filed M.A.No229 of 2012 ,to dismiss the Application No.60 of 2012 or in the alternative ,to clarify the order dated 21-11-2012 to the effect that the said order does not prevent the project proponent to carry on the project of the beneficiation plant in accordance with law. As the maintainability of the original application itself is in question, we have heard all the respective counsel on all issues.
19. According to the submission of the learned counsel for the 4 th 17 respondent,who has raised the question relating to the maintainability of the Original Application,while the permission to draw water for the project of the 4th respondent was on11-02-2009 and all other prayers are linked to that order. According to him ,virtually the applicant has challenged that order of the 2nd respondent which was passed before the commencement of the National Green Tribunal Act 2010,which came into effect from 18-10-2010 and the susequent order of the 2nd respondent dated 28-01-2013 was only the continuation of the earlier order dated 11-02-2009 extending the period of agreement and therefore this Tribunal has no jurisdiction.He would further contend that the permission granted to the project proponent to draw water is not under any of the seven statutes mentioned in the Schedule I to the NGT Act.It was the decision taken by the State Government which is not within the purview of the Act.His further contention is that, when an exactly similar matter is pending adjudication before the Hon'ble High Court of Orissa , it may not be proper for for the fora to take independent decisions.He would finally submit that even otherwise the main application is totally barred by limitation even as per the Act and therefore liable to be dismissed.Further ,he submitted that when the applicant's own brother was involved in offences committed in the project site he can not disown his knowledge. According to him there is absolutely no cause of action and he would also rely upon the judgment of the Hon'ble Supreme Court in (2004)2 SCC 579. Insofar as it relates to the amendment application, it his submission that even on merit of the said application ,it is on a total and different cause of 18 action which cannot be raised in this main application.Mere liberty given to the applicant to file appropriate application does not mean that it should be allowed without considering its merit.It is his vehement contention that the applicant having known that now he cannot maintain any appeal against the Forest Clearance ,as it barred by limitation,has chosen to file this application and therefore it is liable to be dismissed. He is categoric that the project proponent is not putting up any intake well.
20. Per contra, it is the contention of the learned counsel for the original application that the entire issue relates to the preservation and regular flow of water in the Baitarani River which cannot be said to be outside the jurisdiction of this Tribunal.According to him, technicality can not stand in the way of rendering substantial justice.It is his further submission that the Writ Petition ,stated to have been filed in the High Court is not known to him and the applicant is not a party .In any event,there is no bar for this Tribunal to decide the issue if it is within its purview.
21. We heard in detail the learned counsel for the applicant as well as the respondents, particularly the 4th respondent ,project proponent and having referred to all the papers filed and on application of our minds, we formulate the following issues for our consideration and decision thereon:
19A.Whether the applicant is entitled for the relief of setting aside the order of the respondent no.2 dated11-02-2009 and other prayers made by him?
B.Whether the Original Application is maintainable?
C.Whether the application for amendment of the Original Application can be entertained?
22. As all the three issues are interconnected,we propose to consider all the issues together. On the admitted facts explained in detail above, we will now proceed to examine the maintainability of the main application.As stated above, the relief claimed by the applicant not only relates to the maintainance of the natural flow of River Baitarani but also challenging the letter of the 2nd respondent permitting withdrawal of water by the 4th respondent project proponent from Baitarani River to be used for the project of the iron ore beneficiation plant.In fact, it that letter impugned in this application which relates to the 4th respondent about which we are concerned in this application , that gives the cause of action for the main application itself.The said order dated 11-02-2009, has been issued by the Additional Secretary to Government of Orissa permitted the 4th respondent to draw 4.70 cusecs of water from river Baitarani for the proposed beneficiation plant at Tonto, Barbil District of Keonjhar for a period of two years subject to availability of water and 20 subject to various conditions. Therefore it is clear that the said order of permission has been passed by the State Government of Odisha.Clause no.8 of the impugned order makes it abundantly clear that the said order has been passed as per the powers conferred on the State under 'Orissa Irrigation Act 1959 and Rules1961.The said clause reads as follows:
'8. The drawal of water is in accordance with the provision of Orissa Irrigation Acts 1959 and Rules,1961 and amendments made from time to time.' Therefore it is crystal clear from the very contents of the order impugned that ,the order challenged herein is not one passed under any one of the seven Acts enumerated in the Schedule 1 of the National Green Tribunal Act 2010 namely,The Water(Prevention and Control of Pollution) Act,1974,The Water (Prevention and Control of Pollution)Cess Act,1977,The Forest (Conservation ) Act,1980,The Air(Prevention and Control of Pollution) Act1981,The Environment(Protection)Act 1986,The Public Liability Insurance ACT, 1991 and The Biological Diversity Act,2002.
23. Section 14 of the National Green Tribunal Act 2010, clearly states that, '14.Tribunal to settle disputes.--(1)The Tribunal shall have the jurisdiction over all civil cases where a substantial 21 question (including enforcement of any legal right relating to environment), is involved and such question arises out of the enactments Specified in Schedule I.' In the light of the specific provision in the Act, which has created this Tribunal,restricting its jurisdiction only in respect of certain Acts,we are of the view that we have no jurisdiction in the matter.
24. But the next question is in the light of the objects of the Act ,which is very wide as stated in the Preamble as, 'An Act to provide for establishment of a National Green Tribunal for the effective and expeditious disposal of cases relating to environmental protection and conservation of forests and other natural resources including enforcement a any legal right relating to environment and giving relief and compensation for damages to persons and property and for matters connected therewith or incidental thereto.' Can this Tribunal act as a passive spectator ,when a complaint is made that natural flow of running water in a river is being illegally directed, especially when The Water (Prevention and Control of Pollution) Act 1974, in its Preamble uses the word 'restoring of wholesomeness of water',as the object? The answer in our view is in the negative. But on the facts of this case ,it is the catagoric stand of the MoEF in its 22 reply that it has not only given environment clearance to the project of the 4th respondent but there are no complaint from any one about the breach of conditions by the project proponent.Moreover, the impugned order itself has made sufficient safeguards saying, "7.The Industry will not disturb the normal flow of water so that riparian rights in the down stream will be affected and the industry shall have no claim on that account.' Therefore it is always open to the applicant or any other person to obtain adequate remedy. We are fully satisfied that as on date there is no issue of environment by the conduct of the 4th respondent.
25. There is one other issue ,as submitted by the learned counsel for the 4th respondent namely, the order impugned is dated11-02-2009, which is before the NGT Act came in to existence which is on 18-10-2010. On this score also we cannot entertain this application.Even otherwise ,there is a question of limitation.An order passed in 2009 cannot allowed to be questioned in 2012.Apart from the fact that this Tribunal has no jurisdiction, even as per the NGT Act the Tribunal can entertain only if an application is made within six months from the date of cause of action. However ,in the event of sufficient cause shown by the applicant that he has been prevented for sufficient reasons to approach the Tribunal, a further period of sixty days can be condoned. Beyond that period the Tribunal itself has no powers to entertain any application for any reason,which is a settled law. That is also the purport of the proviso to section 14(3) 23 which states:
'Provided that the Tribunal may,if it is satisfied that the applicant was prevented by sufficient cause from filing the application within the said period ,allow it to be filed within a further period not exceeding sixty days.' As held by the Hon'bls Supreme Court in N.C. Dhoundial Vs Union of India and others ,in the context of the jurisdiction of National Human Rights Commission, under the Protection of Human Rights Act,the period of limitation which is basically procedural in nature,it can also operate as fetters of jurisdiction.
26. Therefore , looking into any angle we are unable to accept the contention of the learned counsel for the applicant,except observing that it shall be the duty of the project proponent to scrupulously follow the conditions contemplated under the order of the 2 nd respondent dated11-02-2009 as subsequently extended as well as the conditions laid down in the environment clearance granted by the MoEF dated 19-02-2009. Further,in addition to the catagoric stand of the project proponent in the reply stating that the project proponent is no constructing any intake well,the learned counsel for the project proponent on behalf of his client has made a statement that his client has not made any intake wall and has no plan of making the same in future also. The said statement is recorded and it is expected of the authorities concerned to ensure the strict compliance of the same. It is also relevant 24 to point out at this juncture that the applicant has also not chosen to question the EC.
27. Now,coming to the application for amendment filed by the applicant, at the outset ,as we have already concluded that the main application is not maintainable, it goes without saying that the amendment application is also not maintainable and hence liable to be dismissed.Even otherwise, we fail to understand as to how the issuance of Forest Clearance by some other authority under a different law can be even remotely connected with the issuance of permission to draw water for the project of the 4th respondent . As correctly submitted by the learned counsel for the project proponent,not only the entire cause of action is sought to be changed by the proposed amendment,but also the applicant is actually seeking to introduce a new case.If the applicant desires to challenge the Forest Clearance granted to the 4th respondent,the same has to be by a different process even if it is in the same forum.An appeal under the NGT Act is different from an application.An appeal and an application can be heard together,if the subject matter is the same.An application may even be converted to an Appeal in the interest of rendering substantial justice.Here,the case of the applicant cannot come anywhere near the said concepts.The applicant can not disown knowledge about this project from 2009, especially when there are records to show that his own brother was involved in a criminal case of riot in place of the project proponent and F I R has also been registered.
2528. For the reasons stated supra, we dismiss both Original Application No. 60 of 2012 and M.A .No 73 of 2013. As the main application and amendment application are dismissed, M.A.No. 229 of 2012 and M.A.No.13 of 2013 filed by the project proponent is dismissed as nothing survives.We leave the Parties to bear their own cost.
Justice Dr P.Jyothimani (J.M.)
Prof. Dr. P.C,Mishra (E.M.)
Dated 5th August 2014.
26


Here we’ll review the creation of dates and times, the components that make up dates and times, time spans, and time zones in R.1 See the RStudio Dates and Times Cheat Sheet for a condensed reference.
There are three types of data that refer to an instant in time: dates, times, and date-times. You can retrieve the current date with date()
and the current date-time with now()
.
We will use the following three packages in this post:
Creating Dates and Times
1. Create dates and times from strings
Use a function containing y, m, d
and h, m, s
to turn a string or series of numbers into a date or date-time.
2. Create dates and times from other types of data
Use as_date()
and as_time()
to convert an object to a date or a date-time.
3. Create dates and times from components spread across multiple columns in a table
Use make_datetime()
to create a date-time if your data is spread out across multiple columns in a table. For example, in the nycflights13 dataset, there are separate columns for year, month, day, departure hour, and departure minute. We can create a new date-time column for departure time, and use this new column to visualize the distribution of flights on any day.
Retrieve and Edit Date and Time Components
Retrieve date and time components from a date or date-time with the following functions:
year()
returns the yearmonth(..., label = TRUE)
returns the month; set label = TRUE to return abbreviated month namewday(..., label = TRUE, abbr = FALSE)
returns the day of the week; set abbr = FALSE to return full namemday()
returns the day of the monthyday()
returns the day of the yearhour()
returns the hourminute()
returns the minutesecond
returns the second
Edit date and time components with the following functions:
update(<DATE>, year = ..., month = ..., mday = ..., hour = ...)
updates dates manuallyround_date()
rounds to the nearest specified unit (minute, hour, day, week, month, year, etc.)floor_date()
rounds down to the nearest specified unitceiling_date()
rounds up to the nearest specified unit
Tip: Set larger components of a date to a constant to explore patterns in the smaller components. For example, in nycflights13, we can set the flight day to a constant to view the distribution of flights across the course of the day for every day of the year:
Time Spans: Durations, Periods and Intervals
If you subtract two dates in R regularly, you get a “difftime” object that records a time span in seconds, minutes, hours, days, or weeks, which isn’t great because the units aren’t consistent. Time spans are better measured in these three ways:
- Durations, which represent an exact number of seconds
- Periods, which represent human units of time, i.e. weeks, months, and years
- Intervals, which are durations with a starting and ending point
1. Durations
Durations measure time in seconds. They can be added to each other, multiplied by a constant, and added or subtracted from dates and times.
Note: When adding or subtracting durations to dates, be aware of time discrepancies such as daylight savings time.
2. Periods
Periods measure time in human units, such as weeks and months. This takes into account time discrepancies such as daylight savings time with adding or subtracting from dates or times.
3. Intervals
Intervals are durations with starting an ending points, and are represented by %--%
. They are useful when trying to determine how long a specific period is, sice you want to include all time discrepancies for that period.
For example, you may want to know the number of days between today and the same day next year – this calculation depends on whether it’s a leap year or not, so we should use intervals.
Time Zones
Time zones are complicated, but here are a couple of basic functions that are useful to know:
Sys.timezone()
returns the time zone of your workstation, according to Rwith_tz(<DATETIME>, tzone = "America/Detroit")
changes time zone while keeping the instant in timeforce_tz(<DATETIME>, tzone = "America/Detroit")
changes time zone and changes the instant in time
-
This post is meant for a person who is looking for a refresher on dates and times in R, and the content in this post is based on chapter sixteen of R for Data Science by Hadley Wickham & Garrett Grolemund. ⤴


Reading this article on RESTful routing, comments, and marking things as spam, the author suggests the following.
Given a couple of commentable resources like these:
map.resources :bookmarks, :has_many => [:comments] map.resources :posts, :has_many => [:comments]
You will find yourself writing helpers like this:
def spam_comment_url(comment) case o = comment.commentable when Post spam_post_comment_url(o, comment) when Bookmark spam_bookmark_comment_url(o, comment) end end end
Which they claim is evidence of the fact that you need a new top-level resource with an additional non-REStful action:
# First define the top-level comment resource map.resources :comments, :member => {:spam=>:post} # then add a shallow collection under each of the commentables map.resources :bookmarks do |bookmarks| bookmarks.resources :comments, :shallow=>true end map.resources :posts do |posts| posts.resources :comments, :shallow=>true end
I'm inclined to think that the additional action probably isn't required but it could definitely make some things a little bit cleaner and easier, so it's something to think about.
Comments are now closed for this issue.


Discover Events
- Business
- Charity
- Film
- Others
- Class
- Conference
- Seminar
- Expo
- Today
- Tomorrow
- This Week
- Next Week
Events
Event Name
by Organiser Name
July 21,2014 at 8PM
Worli,Mumbai MH
Event Name
by Organiser Name
July 21,2014 at 8PM
Worli,Mumbai MH
Event Name
by Organiser Name
July 21,2014 at 8PM
Worli,Mumbai MH
Event Name
by Organiser Name
July 21,2014 at 8PM
Worli,Mumbai MH


Clipboard {: .doctitle}
Clipboard
is an abstraction of clipboard for Windows, Linux and Mac.
Synopsis
// get the system clipboard
var clipboard = nw.Clipboard.get();
// Read from clipboard
var text = clipboard.get('text');
console.log(text);
// Or write something
clipboard.set('I love NW.js :)', 'text');
// And clear it!
clipboard.clear();
Clipboard.get()
- Returns
{Clipboard}
the clipboard object
Note
The Selection Clipboard in X11 is not supported.
clip.set(data, [type])
data
{String}
the data to write to the clipboardtype
{String}
Optional the type of the data. Currently only"text"
(plain text) is support. By default,type
is set to"text"
.
Write data
of type
to the clipboard.
clip.get([type])
type
{String}
Optional the type of the data. Currently only"text"
(plain text) is support. By default,type
is set to"text"
.- Returns
{String}
the data retrieved from the clipboard
Get the data of type
from clipboard.
clip.clear()
Clear the clipboard.