cViewport describes a two-dimensional window for rendering an OpenGL scene. Basically this class encapsulates an OpenGL rendering context. Creating a window is left to the application programmer, since that will depend on the development environment that you're using. Once you have a window handle, use this class to bind it to an OpenGL context. More...
#include <CViewport.h>
Public Member Functions | |
| cViewport (HWND a_winHandle, cCamera *a_camera, const bool a_stereoEnabled=false, PIXELFORMATDESCRIPTOR *a_pixelFormat=0) | |
| Constructor of cViewport. | |
| ~cViewport () | |
| Destructor of cViewport. | |
| unsigned int | getHeight () const |
| Get height of active viewport area. | |
| unsigned int | getWidth () const |
| Get width of active viewport area. | |
| void | setCamera (cCamera *a_camera) |
| Set the camera through which this viewport will be rendered. | |
| cCamera * | getCamera () const |
| Get the camera through which this viewport is being rendered. | |
| void | setEnabled (const bool &a_enabled) |
| Enable or disable rendering of this viewport. | |
| bool | getEnabled () const |
| Get the rendering status of this viewport. | |
| void | setStereoOn (bool a_stereoEnabled) |
| Enable or disable stereo rendering. | |
| bool | getStereoOn () const |
| Is stereo rendering enabled? | |
| bool | select (const unsigned int a_windowPosX, const unsigned int a_windowPosY, cCollisionSettings *a_collisionSettings=NULL) |
| Tell the viewport to figure out whether the (x,y) viewport coordinate is within a visible object. | |
| cGenericObject * | getLastSelectedObject () |
| Get last selected mesh. | |
| cTriangle * | getLastSelectedTriangle () |
| Get last selected triangle. | |
| cVector3d | getLastSelectedPoint (void) |
| Get last selected point position. | |
| cVector3d | getLastSelectedPointNormal (void) |
| Get last selected point normal. | |
| double | getLastSelectedDistance (void) |
| Get distance to last selected object. | |
| bool | render (const int imageIndex=CHAI_STEREO_DEFAULT) |
| Call this method to render the scene in OpenGL. | |
| virtual void | onDisplayReset () |
| HDC | getGLDC () |
| Return a direct handle to the OpenGL viewing context. | |
| const PIXELFORMATDESCRIPTOR * | getPixelFormat () |
| Returns the pixel format used by this viewport. | |
| bool | update (bool resizeOnly=false) |
| Reconfigures the display context. | |
| void | setPostRenderCallback (cGenericObject *a_postRenderCallback) |
| Set post-render callback... the object you supply here will be rendered _after_ all other rendering. | |
| cGenericObject * | getPostRenderCallback () const |
| Get post-render callback. | |
| void | setRenderArea (RECT &r) |
| void | getRenderArea (RECT &r) |
| Read the rendering area. | |
| cVector3d | projectPoint (cVector3d &a_point) |
Static Public Member Functions | |
| static cViewport * | getLastActiveViewport () |
| Return the last activated viewport. (Last Viewport for which the render() function was called). | |
Public Attributes | |
| cCollisionRecorder | m_collisionRecorder |
| Last collision events with mouse. | |
| int | m_glViewport [4] |
| It's useful to store the last viewport transformation, for gluProject'ing things. | |
Protected Member Functions | |
| bool | cleanup () |
| Clean up the current rendering context. | |
| virtual bool | renderView (const int a_imageIndex) |
| Render the scene in OpenGL. Nukes the contents of the GL buffers. | |
Protected Attributes | |
| cCamera * | m_camera |
| Virtual camera connected to this viewport. | |
| bool | m_enabled |
| Status of viewport. | |
| bool | m_stereoEnabled |
| Stereo status. | |
| HWND | m_winHandle |
| Handle to window display. | |
| HGLRC | m_glContext |
| OpenGL display context. | |
| HDC | m_glDC |
| display context. | |
| bool | m_glReady |
| GL Status. | |
| RECT | m_activeRenderingArea |
| RECT | m_forceRenderArea |
| PIXELFORMATDESCRIPTOR | m_pixelFormat |
| Descriptor of the context opened for OpenGL rendering. | |
| cGenericObject * | m_postRenderCallback |
Static Protected Attributes | |
| static cViewport * | lastActiveViewport = 0 |
cViewport describes a two-dimensional window for rendering an OpenGL scene. Basically this class encapsulates an OpenGL rendering context. Creating a window is left to the application programmer, since that will depend on the development environment that you're using. Once you have a window handle, use this class to bind it to an OpenGL context.
Typically a cViewport is connected to a cCamera for rendering, and a cCamera is typically connected to a cWorld, where objects actually live.
| cViewport::cViewport | ( | HWND | a_winHandle, | |
| cCamera * | a_camera, | |||
| const bool | a_stereoEnabled = false , |
|||
| PIXELFORMATDESCRIPTOR * | a_pixelFormat = 0 | |||
| ) |
Constructor of cViewport.
Constructor of cViewport.
| a_winHandle | Handle to the actual win32 window. | |
| a_camera | The camera through which this viewport should be rendered. | |
| a_stereoEnabled | If true, a stereo rendering context is created. | |
| a_pixelFormat | If non-zero, this custom pixel format is used to initialize the viewport. |
| void cViewport::onDisplayReset | ( | ) | [virtual] |
Clients should call this when the scene associated wit this viewport may need re-initialization, e.g. after a switch to or from fullscreen.
Clients should call this when the scene associated with this viewport may need re-initialization, e.g. after a switch to or from fullscreen. Automatically called from update() when the viewport creates a new GL context.
Project a world-space point from 3D to 2D, using my viewport xform, my camera's projection matrix, and his world's modelview matrix.
Project a world-space point from 3D to 2D, using my viewport xform, my camera's projection matrix, and his world's modelview matrix.
| a_point | The point to transform |
| bool cViewport::render | ( | const int | imageIndex = CHAI_STEREO_DEFAULT |
) |
Call this method to render the scene in OpenGL.
Call this method to render the OpenGL world inside the viewport.
The default rendering option (CHAI_STEREO_DEFAULT) tells the viewport to decide whether it's rendering in stereo, and - if so - to render a full stereo pair. The other rendering options let you specify a specific image index (mono, left, or right).
The actual rendering is done in the renderView() function, once this function decides which frame to render.
Usually you want to use CHAI_STEREO_DEFAULT. The best reasons not to are:
(1) I have a stereo context, but sometimes I want to render in mono for a while. Alternatively, I could just disable stereo rendering temporarily.
(2) I have a stereo context, but I have a lot of computation to do and I want to get control back between the left and right frames.
| imageIndex | Either CHAI_STEREO_DEFAULT, CHAI_MONO, CHAI_STEREO_LEFT, or CHAI_STEREO_RIGHT |
| bool cViewport::renderView | ( | const int | a_imageIndex | ) | [protected, virtual] |
Render the scene in OpenGL. Nukes the contents of the GL buffers.
Renders the OpenGL scene in the buffer specified by imageIndex.
| a_imageIndex | CHAI_MONO, CHAI_STEREO_LEFT or CHAI_STEREO_RIGHT |
| bool cViewport::select | ( | const unsigned int | a_windowPosX, | |
| const unsigned int | a_windowPosY, | |||
| cCollisionSettings * | a_collisionSettings = NULL | |||
| ) |
Tell the viewport to figure out whether the (x,y) viewport coordinate is within a visible object.
Select an object on displayed in the viewport. This method casts a virtual ray through the viewport and asks the world for the first object hit by that ray.
It's most useful if you want to allow the user to use the mouse to click on objects in your virtual scene.
Use getLastSelectedObject(), getLastSelectedTriangle(), and getLastSelectedPoint() to extract information about the results of this operation.
| a_windowPosX | X coordinate position of mouse click. | |
| a_windowPosY | Y coordinate position of mouse click. | |
| a_collisionSettings | Settings used for performing collision detection. |
| void cViewport::setCamera | ( | cCamera * | a_camera | ) |
Set the camera through which this viewport will be rendered.
Set camera. The viewport will now display the image filmed by this virtual camera.
| a_camera | Virtual camera in world. |
| void cViewport::setRenderArea | ( | RECT & | r | ) |
You can use this to specify a specific rectangle to which you want this viewport to render within the window. Supply -1 for each coordinate to return to the default behavior (rendering to the whole window). The _positive_ y axis goes _up_.
You can use this to specify a specific rectangle to which you want this viewport to render within the window. Supply -1 for each coordinate to return to the default behavior (rendering to the whole window). The _positive_ y axis goes _up_.
| r | The rendering area within the GL context |
| void cViewport::setStereoOn | ( | bool | a_stereoEnabled | ) |
Enable or disable stereo rendering.
Enable or disable stereo rendering on this viewport.
Note that it is not possible to change the pixel format of a window in Windows, so if you create a viewport that doesn't have stereo support, you can't enable stereo rendering without creating a new window/viewport.
| bool cViewport::update | ( | bool | resizeOnly = false |
) |
Reconfigures the display context.
If the window has been modified, or just created, call this function to update the OpenGL display context.
| resizeOnly | If false (default), reinitializes the GL context. |
cViewport * cViewport::lastActiveViewport = 0 [static, protected] |
The most recent viewport to initiate rendering; useful for finding global opengl state information
RECT cViewport::m_activeRenderingArea [protected] |
The rectangle to which we're rendering within the GL window, equal to the window size by default. The _positive_ y axis goes _up_.
RECT cViewport::m_forceRenderArea [protected] |
If we're forcing rendering to a particular rectangle within the viewport, this rectangle contains those coordinates. Otherwise all coordinates are -1, which tells cViewport to use the whole window. The _positive_ y axis goes _up_.
cGenericObject* cViewport::m_postRenderCallback [protected] |
If non-zero, this object will get rendered immediately before the GL buffer is swapped out, after all other.


|
|
| PowerJumpControl (const std::string &name) |
| |
|
void | init (const double &step) |
| |
|
virtual const std::string & | getClassName (void) const |
| |
|
|
SignalPtr< dg::Vector, int > | leg_lengthSIN |
| |
|
SignalPtr< dg::Vector, int > | cnt_sensorSIN |
| |
|
SignalPtr< dg::Vector, int > | leg_length_triggerSIN |
| |
|
SignalPtr< dg::Vector, int > | leg_length_airSIN |
| |
|
SignalPtr< dg::Vector, int > | des_fffSIN |
| |
|
SignalPtr< dg::Vector, int > | des_weight_fffSIN |
| |
|
SignalPtr< dg::Vector, int > | kp_groundSIN |
| |
|
SignalPtr< dg::Vector, int > | kp_airSIN |
| |
|
SignalTimeDependent< dg::Vector, int > | return_des_posSOUT |
| |
|
SignalTimeDependent< dg::Vector, int > | return_des_forceSOUT |
| |
|
SignalTimeDependent< dg::Vector, int > | return_des_kpSOUT |
| |
|
|
static const double | TIME_STEP_DEFAULT |
| |
|
static const std::string | CLASS_NAME |
| |
|
|
double | TimeStep |
| |
|
int | pos_trigger_flag_ |
| |
|
int | force_trigger_flag_ |
| |
|
int | kp_trigger_flag_ |
| |
| dynamicgraph::Vector & PowerJumpControl::return_des_force |
( |
dg::Vector & |
des_force, |
|
|
int |
t |
|
) |
| |
|
protected |
This method computes desired forces depending on state of the teststand
| dynamicgraph::Vector & PowerJumpControl::return_des_kp |
( |
dg::Vector & |
des_kp, |
|
|
int |
t |
|
) |
| |
|
protected |
This method computes desired kp gain depending on state of the teststand
| dynamicgraph::Vector & PowerJumpControl::return_des_pos |
( |
dg::Vector & |
des_pos, |
|
|
int |
t |
|
) |
| |
|
protected |
This method computes desired position depending on state of the teststand
The documentation for this class was generated from the following files:
- include/dg_tools/test_stand_control/power_jump.hpp
- src/test_stand_control/power_jump.cpp


Asset Monitoring Configuration
Gateway: {{gatewayMac}}
Version: {{gatewayVersion}}
Enter Rest Server Url:
Enter timeout (ms) :
3500
5500
7500
8500
Submit
Reset Gateway
Signing in... Please wait.
{{data}}


This website is very much in beta form. Please Please Please dont rely on it to actually keep track of your time.


--- layout: tweet ---
Happy square root day! http://tinyurl.com/6yrl2m
3/3/2009, 9:00:56 AM
Favs: 0
Retweets: 0


|
Intel(R) Threading Building Blocks Doxygen Documentation
version 4.2.3
|
Modules | |
| Collection Control | |
| Threads | |
| Synchronization | |
| Events | |
| Memory Accesses | |
| Thread and Object States | |
| Frames | |
group of functions is used for correctness checking tools | |
| void ITTAPI | __itt_fsync_prepare (void *addr) |
| Fast synchronization which does no require spinning. More... | |
| void ITTAPI | __itt_fsync_cancel (void *addr) |
| Fast synchronization which does no require spinning. More... | |
| void ITTAPI | __itt_fsync_acquired (void *addr) |
| Fast synchronization which does no require spinning. More... | |
| void ITTAPI | __itt_fsync_releasing (void *addr) |
| Fast synchronization which does no require spinning. More... | |
Fast synchronization which does no require spinning.
- This special function is to be used by TBB and OpenMP libraries only when they know there is no spin but they need to suppress TC warnings about shared variable modifications.
Fast synchronization which does no require spinning.
- This special function is to be used by TBB and OpenMP libraries only when they know there is no spin but they need to suppress TC warnings about shared variable modifications.
Fast synchronization which does no require spinning.
- This special function is to be used by TBB and OpenMP libraries only when they know there is no spin but they need to suppress TC warnings about shared variable modifications.
Fast synchronization which does no require spinning.
- This special function is to be used by TBB and OpenMP libraries only when they know there is no spin but they need to suppress TC warnings about shared variable modifications.


Preparation time
less than 30 mins
Cooking time
10 to 30 mins
Serves
Serves 4
This is a super speedy beef stroganoff but still packs a flavour punch, serve with chips or noodles.
Season the beef fillets with salt and pepper and set aside.
Heat the butter in a large frying pan. Add the onions and sauté for 2 minutes then add the mushrooms, cook until both are soft. Add the mustard and stir it into the vegetables, coating thoroughly. Pour over the stock and leave to simmer until the liquid has reduced by about half. Stir in the crème fraiche and set aside for a few minutes.
In another large frying pan heat the vegetable oil. When it is smoking, add the beef cubes. Stir constantly – until the meat is browned on all sides. You only want it to cook for 1 minute, at the most.
If you want to flambé the beef, put the brandy in a ladle and heat it over the gas. When it starts to burn off (you will see the fumes), tip it very gently towards the flame and it will ignite (CAUTION: Keep your face and hair away from the flames.). Immediately pour this over the beef and give it a quick stir.
Return the onion and mushroom sauce to the heat and add the beef to the pan. Season to taste, sprinkle over the parsley and serve.


{{video.description}}
{{nextvideo.duration}}
Product : {{nextvideo.displayProductName}}
{{nextvideo.duration}}
Product : {{nextvideo.displayProductName}}
Have co-workers who will be using {{studentcourse.displayProductName}}? Enter their e-mail to add them to your training portal.


Logarithm Axis
LiveCharts mappers makes this easy, all you need to do is configure the scale in your mapper,
as you normally configure any other chart.
To keep this example always up to date it is directly pulled from the Github repository, the
repo for simplicity uses the UserControl class to wrap every example, but you can use any
container for your plots.
Code Behind
XAML


Kim Kardashian West breaks silence on Caitlyn Jenner’s I’m A Celebrity stint
Kim Kardashian West has broken her silence on Caitlyn Jenner taking part in this year’s I’m A Celebrity… Get Me Out Of Here!.
She is the first of Jenner’s famous family members to publicly acknowledge her appearance in the jungle in the British TV series.
She shared a clip of Jenner waking up the other stars in the camp by crying out: “Let’s go team. Not just another day, another day to excel, another day to be great. Rise and shine.”
Sharing the TV show’s official Twitter account post, Kardashian West wrote: “I literally recorded this and set this as my alarm a few weeks ago!”
The unique wake-up call from Jenner, 70, was a take on her daughter Kylie Jenner’s greeting to her baby Stormi that went viral.
Fans of I’m A Celebrity have noted that while Jenner has discussed her relatives in the jungle, they have appeared to be silent in supporting her.
Jenner was born Bruce and was an Olympic gold medal-winning decathlete.
She came out as a trans woman in April 2015 when she was in her late 60s, changing her name to Caitlyn.
Jenner was married to the family matriarch Kris, the mother of Kim, Kourtney, Khloe and Rob Kardashian, from 1991 until 2015.
Together they had daughters Kendall and Kylie, and Jenner also has four children from previous marriages.


Michael Jackson’s son Prince channels father’s epic style with sister Paris
Michael Jackson’s eldest son Prince has sweetly remembered his late dad recently, as he channelled the late King Of Pop on the red carpet.
Over 10 years after Michael’s sudden death, Prince and his little sister Paris represented Michael at Motown’s 60th-anniversary celebration in Paris and it was a walk down nostalgic style lane.
Wanting to bring a little of their dad into the wardrobes, both Prince and Paris revealed they still continue to work with their father’s stylist Rushka Bergman.
Which explained Prince’s blinging jacket he wore, we suppose. Very MJ.
Keeping his dad’s memory alive in subtle ways through how he dresses on the red carpet, Prince revealed a sweet throwback to watching his superstar father get ready with Rushka.
‘I remember Rushka was my dad’s stylist.
‘So when I came in yesterday to look at the jacket, it was almost nostalgic.
Advertisement Advertisement
‘It was very cool that to see that I am like, not really being put in the same shoes, but almost doing a very similar thing.’
Prince added that everything felt it was coming ‘full circle’.
Sharing a sweet snap to social media with his sister, Prince later wrote: ‘I don’t always dress up…but when I do it’s with my gorgeous sister @parisjackson. Stay classy my friends.’
 ‘I love that we get to do these things together and so excited for what’s to come!! love you. [sic].’
Recently, Prince – who is a budding YouTube film critic – revealed he feels his dad’s ‘guidance’.
The King Of Pop died 10 years ago however his 22-year-old son has said he often feels his late father is helping steer him in the right direction.
Last month Prince told Extra: ‘My dad was always a strong believer in going for what you want and “go follow your dreams and chase your dreams…”
‘So for us to be able to kind of sit there and hopefully make a career about talking about film and looking at film – my brother wants to be a director, I love producing…’
Advertisement Advertisement
He continued: ‘It’s just, it’s definitely, there’s some form of guidance there that kind of is ushering us into the next generation.’
Prince, who also has brother Blanket, revealed the goal for the channel on the video-sharing platform is to ‘bring an educated yet family-friendly vibe’ for viewers tuning in.
He explained: ‘Right now, it’s just me, my brother, and my cousin Taj, one camera in a room in our house, and we’re really focused on reviewing movies and current movies as they come out.
‘We’re hoping to bring an educated yet family-friendly vibe into the movie-watching arena… We’re hoping to be in other forms of visual media — video games, virtual stuff like that.’
Got a showbiz story?
If you've got a story, video or pictures get in touch with the Metro.co.uk Entertainment team by emailing us<EMAIL_ADDRESS>calling 020 3615 2145 or by visiting our Submit Stuff page - we'd love to hear from you.


I am a product designer (UI/UX) with a Computer Engineering background and a creative geek obsessed with creating and designing eye candy solutions for web and mobile apps.
With my avid interest in UI design and education in computer engineering, as well as my skills in communication, team collaboration, creativity and a strong work ethic, I feel confident that I would significantly benefit your organization. Furthermore, my communication and organizational abilities position me ready to thrive in this field and I am more than prepared to put my knowledge and abilities to work for you.
Figma, Adobe XD, HTML5, CSS3, Javascript, Photoshop, Bootstrap Studio.


Topographic maps are medium-scale maps that are frequently used by Geography students. The map scale on South African topographic maps is ALWAYS 1 : 50 000. This means that 1 cm on the map represents 0,5 km on the ground. Each topographic map shows 15 minutes of latitude by 15 minutes of longitude (an area of about 640 km²). The actual map sheet is approximately 60 cm by 90 cm.
Pan around the reduced topographic map of Moorreesburg and identify the following features:
Also note that symbols showing vegetation are green, water features are blue and constructed features are grey, black, brown or red.


|
RVL
1.0
|
Affine Injection operator. More...
#include <blockop.hh>
Public Member Functions | |
| InjectOp (std::shared_ptr< Vector< Scalar > > _ref, int _icomp) | |
| InjectOp (std::shared_ptr< Vector< Scalar > > _ref, std::vector< int > _icvec) | |
| InjectOp (InjectOp< Scalar > const &f) | |
| ~InjectOp () | |
| Space< Scalar > const & | getDomain () const |
| Space< Scalar > const & | getRange () const |
| ostream & | write (ostream &str) const |
| Public Member Functions inherited from RVL::Operator< Scalar > | |
| Operator () | |
| Operator (const Operator< Scalar > &) | |
| virtual | ~Operator () |
| virtual ScalarFieldTraits< Scalar >::AbsType | getMaxStep (const Vector< Scalar > &, const Vector< Scalar > &) const |
| can be overridden to express distance to boundary of domain for operators whose domains are not the whole space. More... | |
| Public Member Functions inherited from RVL::Writeable | |
| virtual | ~Writeable () |
| void | write (RVLException &e) const |
| Report state of object to RVLException. More... | |
Protected Member Functions | |
| void | apply (Vector< Scalar > const &x, Vector< Scalar > &y) const |
| void | applyDeriv (Vector< Scalar > const &x, Vector< Scalar > const &dx, Vector< Scalar > &dy) const |
| void | applyAdjDeriv (Vector< Scalar > const &x, Vector< Scalar > const &dy, Vector< Scalar > &dx) const |
| Operator< Scalar > * | clone () const |
| Protected Member Functions inherited from RVL::Operator< Scalar > | |
| virtual void | apply (const Vector< Scalar > &x, Vector< Scalar > &y) const =0 |
| 1-jet at a point, accessible only through OperatorEvaluation and subclasses. More... | |
| virtual void | applyDeriv (const Vector< Scalar > &x, const Vector< Scalar > &dx, Vector< Scalar > &dy) const =0 |
| More... | |
| virtual void | applyAdjDeriv (const Vector< Scalar > &x, const Vector< Scalar > &dy, Vector< Scalar > &dx) const =0 |
| More... | |
| virtual void | applyDeriv2 (const Vector< Scalar > &, const Vector< Scalar > &, const Vector< Scalar > &, Vector< Scalar > &) const |
| virtual void | applyAdjDeriv2 (const Vector< Scalar > &, const Vector< Scalar > &, const Vector< Scalar > &, Vector< Scalar > &) const |
| , defined so that . More... | |
| void * | operator new (size_t size) |
| operator new - not available to general public, but available to children who will use it to define clone More... | |
| DerivEvaluation< Scalar > * | createDerivEvaluation (OperatorEvaluation< Scalar > &opeval) const |
| Virtual derivative constructor. More... | |
| Deriv2Evaluation< Scalar > * | createDeriv2Evaluation (OperatorEvaluation< Scalar > &opeval) const |
| Virtual 2nd derivative constructor. More... | |
Additional Inherited Members | |
| Static Public Member Functions inherited from RVL::Operator< Scalar > | |
| static std::shared_ptr< Operator< Scalar > > | clonePtr (Operator< Scalar > const &op) |
| safe dynamic copy construction More... | |
| Static Protected Member Functions inherited from RVL::Operator< Scalar > | |
| static void | export_apply (Operator< Scalar > const &f, const Vector< Scalar > &x, Vector< Scalar > &y) |
| The export-apply methods make the protected apply methods of any Operator subclass instance available to other Operator subclass instances. More... | |
| static void | export_applyDeriv (Operator< Scalar > const &f, const Vector< Scalar > &x, const Vector< Scalar > &dx, Vector< Scalar > &dy) |
| static void | export_applyAdjDeriv (Operator< Scalar > const &f, const Vector< Scalar > &x, const Vector< Scalar > &dy, Vector< Scalar > &dx) |
| static void | export_applyDeriv2 (Operator< Scalar > const &f, const Vector< Scalar > &x, const Vector< Scalar > &dx0, const Vector< Scalar > &dx1, Vector< Scalar > &dy) |
| static void | export_applyAdjDeriv2 (Operator< Scalar > const &f, const Vector< Scalar > &x, const Vector< Scalar > &dx0, const Vector< Scalar > &dy, Vector< Scalar > &dx1) |
| static Operator< Scalar > * | export_clone (Operator< Scalar > const &op) |
| export version of clone More... | |
Affine Injection operator.
Takes vector in a product of component (sub)spaces as input, replaces corresponding components of output with input. Replaces all other components with constant data members.
Usual linear injection and projection operators are the derivative and adjoint deriv of this op.
For convenience of definition, takes a const reference to a vector in the product range space as arg to constructor, initializes a copy as data member. The apply method copies this vector to the output, then replaces the indicated components with corresponding input components.
Relies on error trapping in component subspace operations - implements no additional traps.
NOTE added 04.09.15 WWS: because of the current limitations of ProductSpace construction, number of components limited to 4, with clunky constructor interfaces.
Definition at line 1137 of file blockop.hh.
| RVL::InjectOp< Scalar >::InjectOp | ( | std::shared_ptr< Vector< Scalar > > | _ref, |
| int | _icomp | ||
| ) |
Definition at line 1200 of file blockop.hh.
| RVL::InjectOp< Scalar >::InjectOp | ( | std::shared_ptr< Vector< Scalar > > | _ref, |
| std::vector< int > | _icvec | ||
| ) |
Definition at line 1206 of file blockop.hh.
| RVL::InjectOp< Scalar >::InjectOp | ( | InjectOp< Scalar > const & | f | ) |
Definition at line 1213 of file blockop.hh.
| RVL::InjectOp< Scalar >::~InjectOp | ( | ) |
Definition at line 1216 of file blockop.hh.
|
protected |
Definition at line 1148 of file blockop.hh.
|
protected |
Definition at line 1165 of file blockop.hh.
|
protected |
Definition at line 1181 of file blockop.hh.
|
protectedvirtual |
Implements RVL::Operator< Scalar >.
Definition at line 1196 of file blockop.hh.
|
virtual |
Implements RVL::Operator< Scalar >.
Definition at line 1218 of file blockop.hh.
|
virtual |
Implements RVL::Operator< Scalar >.
Definition at line 1219 of file blockop.hh.
|
virtual |
Implements RVL::Writeable.
Definition at line 1223 of file blockop.hh.


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.
Appeal Nos. 75 & 69 of 2015 IN THE APPELLATE TRIBUNAL FOR ELECTRICITY, AT NEW DELHI (APPELLATE JURISDICTION) APPEAL NO. 75 OF 2015 & APPEAL NO. 69 OF 2015 & IA NO. 105 OF 2015 Dated: 2nd February, 2016 Present: Hon'ble Mrs. Justice Ranjana P. Desai, Chairperson Hon'ble Mr. I.J. Kapoor, Technical Member APPEAL NO. 75 OF 2015 In the matter of:- Chhattisgarh State Power Distribution Co. Ltd. ...Appellant(s) Versus Chhattisgarh State Electricity Regulatory Commission & Ors. ...Respondent(s) APPEAL NO. 69 OF 2015 & IA NO. 105 OF 2015 In the matter of:- Chhattisgarh State Power Transmission Co. Ltd. ...Appellant(s) Versus Chhattisgarh State Electricity Regulatory Commission & Ors. ...Respondent(s) Counsel for the Appellant(s) : Ms. Suparna Srivastava Ms. Anushka Arora Counsel for the Respondent(s) : Mr. C.K. Rai Mr. Paramhans for R-1 Mr. Sanjay Sen, Sr. Adv. Ms. Divya Chaturvedi Mr. Snehal Kakrania Mr. S. Chauhan for R-2 Page 1 of 29 Appeal Nos. 75 & 69 of 2015 JUDGEMENT
PER HON'BLE MR. I.J. KAPOOR, TECHNICAL MEMBER Chhattisgarh State Power Distribution Company Limited, Raipur is the Appellant in the present Appeal No. 75 of 2015 filed under section 111 of the Electricity Act, 2003 against the Impugned Order dated 02.01.2015 passed by the Chhattisgarh State Electricity Regulatory Commission (hereinafter referred to as "State Commission"- Respondent No. 1) in Petition No. 77/2013(D) whereby the State Commission has adjudicated upon the claim of Jindal Power and Steel Limited (hereinafter referred to as "Respondent No.2") as regards captive status of its 4x135 MW power plant situated at Raigarh.
2. The Appellant is the distribution company in the State of Chhattisgarh. In this Appeal, Chhattisgarh State Power Distribution Company Limited being the State Transmission Utility in Chhattisgarh is Respondent No. 3.
3. In another Appeal No. 69 of 2015 filed under Section 111 of the Electricity Act, 2003 against the same Impugned Order dated 02.01.2015 dealing with the same issue as that of Appeal No. 75 of 2015 filed by the Appellant, the State Transmission Utility of Page 2 of 29 Appeal Nos. 75 & 69 of 2015 Chhattisgarh and in this Appeal, the Respondent No. 1, Respondent No.2 are the same as that in the case of Appeal No. 75 of 2015, however, Chhattisgarh State Power Distribution Company Limited is the Respondent No.3.
4. Since the issues involved in both the Appeals are same and against the same Impugned Order dated 02.01.2015 passed by the State Commission, we shall be deciding both the above appeals by the Appellants by the common order.
Respondent No.2 has set up a power plant consisting of 4 units of 135 MW each i.e. 540 MW situated at Dongamahua, Raigarh (Chhattisgarh) (hereinafter referred to as "DCPP") which is claimed to be captive in entirety.
5. Respondent No.2 is engaged in the business of manufacture of steel and has steel plant in Raigarh alongwith a captive power plant of 286 MW capacity for meeting the power requirement of its steel plant and has been availing power import connection from the Appellant at 220 KV.
6. In addition to this 286 MW power plant, the Respondent No.2 has also set up 4x135 MW power plant (DCPP) at the same location which it claims to be captive in its entirety. Page 3 of 29
Appeal Nos. 75 & 69 of 2015
7. 286 MW captive power plant of the Respondent No.2 is connected to the steel manufacturing plant, which in turn, is connected to the State grid through 220 KV station of the Respondent No.3 at Raigarh.
8. As far as 540 MW of DCPP is concerned, as per the Appellants, its two units i.e. unit 1 & 2 are connected to this steel plant under the captive mode, however, the other 2 units i.e. unit 3 & 4 are not connected with the industrial load of the Respondent No.2 and are connected to the switchyard of the power plant of the M/s. Jindal Power Ltd., a subsidiary company of Respondent No.2 which, in turn, is connected to the regional grid through 400 KV line with inter connection line at Raipur. As per the Appellants, units 3 & 4 of DCPP are not in captive mode but maintaining a merchant Status.
9. The State Commission in its Impugned Order dated 02.01.2015 in Petition No. 77/2013(D) has decided to accord the captive status to all the 4 units of 135 MW of DCPP which in the opinion of the Appellants ought to have been for only unit 1 & 2 of DCPP and not for unit 3 & 4 of DCPP and unit 3 & 4 of DCPP should have been treated as merchant power rather than categorizing the same under captive use resulting into loss of revenue to the Appellants on account of Page 4 of 29 Appeal Nos. 75 & 69 of 2015 non-recovery of cross subsidy surcharge since the same would not be applicable to the captive units.
10. The Appellant is functioning as distribution licensee in the Chhattisgarh State and is performing all functions and duties pertaining to distribution of electricity. The Appellant is entitled to recover such charges from generator and other persons as are admissible and leviable under the provisions of Electricity Act, 2003 and the Regulations framed by the State Commission which has been set up under the provisions of Electricity Act, 2003 to perform all such functions as are enjoyed upon it under Section 86(1) of the Electricity Act, 2003, including adjudication of disputes between licensees and the generating companies.
11. The main issue in the present Appeal is regarding grant of captive status to all the 4 units of 135 MW each of DCPP by the State Commission to Respondent No.2 which has resulted in loss of revenue on account of non-recovery of cross subsidy surcharge by the Appellants from the Respondent No.2 in respect of units 3 & 4 consisting of 135 MW each of DCPP.
12. The Appellants submit that cross subsidy surcharge is leviable on all consumers for balancing of cost of supply between subsidizing Page 5 of 29 Appeal Nos. 75 & 69 of 2015 consumers and subsidized consumers of the distribution licensees which is under universal supply obligation under Section 43 of the Electricity Act, 2003 which mandate supply of electricity on request to consumers of the State and the above balance between the subsidizing and subsidized consumers cannot be disturbed otherwise it would result into an enhanced tariff for the subsidized consumers. The Appellants further state that the cross subsidy surcharge is recovered from the consumers who are not availing supply from the distribution licensees and the only exception being a captive use for which cross subsidy surcharge is not payable.
13. The Appellants submits that under the prevailing Regulations of the State Commission, grant of connectivity is necessarily to be sought for injecting power by a captive generating plant into intra state transmission system and a detailed procedure is prescribed for seeking such connectivity by filing of application to the nodal agency i.e. State Transmission Utility (STU) or the transmission licensee or the State Load Despatch Centre (SLDC) in the prescribed format and on receipt of the application, the nodal agency in consultation and through coordination with other agencies involved in bilateral transactions, shall process the application and carry out the Page 6 of 29 Appeal Nos. 75 & 69 of 2015 necessary inter connection study. The Appellants made a reference of Regulations 10(5) of the State Commission's Regulations, 2011 which states that intra state user in case of expansion of capacity including captive generating plant has to make a fresh application for modification in connectivity arrangements and the Regulations do not permit that if any unit of generating plant has obtained connectivity with the grid, the other unit added subsequently at the same location can also get automatically connected with the grid without obtaining separate permission, as such the Appellants alleged that only unit 1 & 2 of DCPP were given connectivity by the STU under the captive category and subsequently additional units 3 & 4 at DCPP for which a separate permission has not been sought by the Respondent No.2 from STU/SLDC ought not to be considered under captive use.
14. In support of the above arguments of the Appellants, they have cited the relevant extracts of Electricity Act, 2003, State Commission's prevailing Regulations, Grid Code etc.
15. The issue in question in both the above Appeals is whether the State Commission in its Impugned Order dated 02.01.2015 erred in considering the 4 units of 135 MW each of DCPP under active use instead of only first 2 units of 135 MW each of DCPP? Page 7 of 29
Appeal Nos. 75 & 69 of 2015
16. We have heard at length Ms. Suparna Srivastava, Learned Counsel for both the Appellants, Ms. Sanjay Sen, Learned Sr. Counsel for Respondent No.2 and Mr. C.K. Rai, Learned Counsel for the Respondent No.1 and considered their written submissions and arguments put forth by the rival parties during the hearing before us and our observations are detailed herein as under.
17. As alleged by the Appellants that the State Commission erred in holding the entire plant of DCPP comprising of all the 4 units of 135 MW each being treated as captive for the relevant years even when the admitted position on record before the State Commission has been that it is only two units of DCPP i.e. units 1 & 2 which are connected to the steel plant (the captive load) and as such, it is only the first two units of DCPP which can be considered having captive status. The main grievance of the Appellants as described in the above Appeals is that when the other two units of DCPP i.e. units 3 & 4 are not connected to the steel plant and have not gained connectivity with the system of Respondent No. 3 as mandatorily required under the Connectivity Regulations and the Grid Code but are instead connected to the regional grid for transmission of power under long term open access granted to Respondent No.2, the power Page 8 of 29 Appeal Nos. 75 & 69 of 2015 generated from these units and supplied to the steel plant does not qualify as captive use and as such, attracts levy of cross-subsidy surcharge as mandated under section 42 of the Electricity Act, 2003.
18. The main allegation of the Appellant is that the cross-subsidy surcharge has wrongly been denied by the State Commission to the Appellants by treating the said unit 3 & 4 of DCPP also as being for captive use, thereby causing grave financial loss to the Appellants. That too in light of the fact that under the provisions of the Electricity Act, 2003, cross-subsidy surcharge has been maintained so as to benefit various classes of consumers of the distribution licensees on account of recovery of cross-subsidy surcharge and in their view, any denial of rightful recovery of cross-subsidy surcharge would ultimately adversely affect these subsidized consumers of the distribution licensees.
19. The Appellants further submitted that as per the provisions of the Connectivity Regulations notified by the State Commission, it is essentially required as per the Regulation 10(3) that a captive generating plant is to mandatorily seek connectivity with the Appellants' system for injecting power in the transmission system by making an application in the prescribed form detailing therein the Page 9 of 29 Appeal Nos. 75 & 69 of 2015 quantum of power to be injected in the system. In case of any enhancement for injection, a fresh application for modification in connectivity arrangement is required and in view of this for each generating unit of a captive generating plant which is desirous of connecting to the State Grid(the Appellant's system), separate connectivity is necessarily to be obtained. The Appellants further state that the prescribed Regulations do not permit that if any unit of the generating plant has obtained connectivity with the State grid, the other units can also be connected with the grid without obtaining separate connectivity and the State Grid code also prescribed the connectivity conditions and criteria for users connected to or seeking connection to intra-State transmission system.
20. The Appellants alleged that in furtherance of vigilance inspection, the status of power generation in DCPP, including unit 3 & 4 has been examined and as per the certified generation of energy data for unit s 3 & 4 of DCPP obtained from the Chief Electrical Inspector, Raipur, it was observed that the generation from unit 3 was also fed to steel plant as per captive use and within the premises, the Respondent No.2 has installed Auxiliary Bus for facilitating transfer of power from units 3 & 4 for captive use on the need basis.
Page 10 of 29
Appeal Nos. 75 & 69 of 2015
21. As per the Appellants, Respondent No. 2 has violated the legal provisions and has illegally and unauthorizedly been supplying power from the unit 3 & 4 and by running the same in parallel with the State grid without obtaining connectivity as mandatorily required under the State Commission's Regulations, 2011. The Appellants further stated that during the matter was heard by the State Commission, the Appellants brought to the notice of the State Commission the Judgment dated 30.04.2013 of this Tribunal passed in Review Petition No. 2/ 203 in Appeal No. 137/2011: M/s. JSW Energy Ltd. Vs. Karnataka Electricity Regulatory Commission wherein, this Tribunal has held that a captive user is required to identify the unit/units intended for captive consumption at the time of induction of equity stage itself and relevant portion of this Judgment is reproduce below:-
"Pre-identification of the unit/units is also essential from prevention of gaming aspect as illustrated by the following example:
Two units at a generating station of 100 MW and 200 MW produced say 1000 MU and 2000 MU in a year respectively. The Captive user consumed around 2000 MU in a particular year. Consumption of 2000 MU is more than 51% of total generation of two units, therefore the captive user would claim total consumption as captive identifying both units as captive generators. Suppose captive user could consume only 1100 MU, it would identify Unit B as captive and claim full 1100 MU as Page 11 of 29 Appeal Nos. 75 & 69 of 2015 captive consumption. Whereas consumption of 1100 MU, being less than 51% of total generation from both units, would not have qualified to be captive if both the units were identified as captive generators. Further, assume in a particular year the captive generator could consume only 900 MU. It would identify Unit A as captive and claim 900 MU as captive consumption which it could not have, if both the units or unit B was identified as captive generator."
It is clear from the above discussion that a captive consumer may indulge in gaming and identify any unit as captive depending upon its own consumption during the relevant year. Such an arrangement would frustrate the very purpose of law.
In light of the above judgment, the Appellants alleged that the present case of the Respondent No.2 is gaming with the ulterior motive of claiming undue benefit of exemption from payment of cross-subsidy surcharge and the Appellants pleaded before the State Commission that the Respondent No.2 is necessarily to be directed to pay cross- subsidy surcharge and the Appellants be allowed to claim the same under the Supplementary Bill, however, the State Commission has failed to appreciate the allegations put forth by the Appellants and considered the units 3 & 4 of DCPP under captive use without realizing that for units 3 & 4 of DCPP, the Respondent No. 2 has not obtained necessary connectivity from the concerned authority as required in law.
Page 12 of 29
Appeal Nos. 75 & 69 of 2015
22. The Appellants further alleged that the Impugned Order of the State Commission granting captive status to all the 4 units of DCPP of the Respondent No.2 suffers from serious legal infirmity and as such, is liable to be set aside.
23. The Learned Counsel for Respondent No.2 brought our attention to the line diagram indicating therein the existing connectivity status of all the 4 units of DCPP & claimed that the same was approved by the Chief Electrical Inspector and further stated that all the 4 units from the stage of inception i.e. DPR stage itself have been envisaged to be for captive use and unit 1 & 2 are connected to unit 3 & 4 through Auxiliary Bus and the generation from unit 1 & 2 of DCPP is meant to meet the power requirement of the steel plant and the Auxiliary Bus has been put in the system to facilitate flexibility for connecting unit 3 & 4 for the captive power requirement of the steel plant in case of emergency or when unit 1 or 2 is shut down due to break down or annual overhauling. Respondent No. 2 stated that such arrangements are duly approved by the Chief Electrical Inspector in its phasewise line diagram. It is further submitted that the generation from the unit 3 & 4 of DCPP could be transmitted to CTU system in case not required for the captive use of its steel plant as well as through the Page 13 of 29 Appeal Nos. 75 & 69 of 2015 Auxiliary Bus to the STU system in case of requirement of captive use for its steel plant and this arrangement has been done with full knowledge of Chief Electrical Inspector which is evident from the approved line diagram and the Chief Electrical Inspector is in fact the final authority in terms of Section 162 of the Electricity Act, 2003. Respondent No. 2 further submitted that the Appellant has not questioned these findings of the Chief Electrical Inspector and as such this line diagram has attained finality.
24. In response to the various allegations of the Appellants, the Learned Counsel for the Respondent No.2 submitted that the undertaking given by it to the effect that it will not connect more than 2 units of 135 MW each for captive use and this undertaking given by it that it will not connect more than 2 units of 135 MW at any point has not been violated in any manner. The surplus power from unit 3 & 4 are sold to third party on short term basis through CTU system which is maintained by Power Grid Corporation of India Limited and in the event of outages of unit 1 & 2 of DCPP, the generation from unit 3 & 4 is used for supply of power to the captive load of its steel plant. Page 14 of 29
Appeal Nos. 75 & 69 of 2015
25. The Respondent No.2 further submitted that captive power plants have been promoted in the country to cater to the power shortage and irregular power supply to industries to facilitate industrial growth, industrial development and employment opportunities and legal requirement for qualification of generating plant as captive power plant are as follows:-
"Section 2 (8) of the Act defines captive generating plant: 'Captive generating plant' means a power plant set up by any person to generate electricity primarily for his own use and includes a power plant set up by any co-operative society or association of persons for generating electricity primarily for use of members of such co-operative society or association" Rules 3 of the Electricity Rules, 2005:
"3. Requirement of captive Generative plant: (1) No power plant shall qualify as a captive generating plant under section 9 read with clause (8) of section 2 of the act unless:-
(i) Not less than twenty six percent of the ownership is held by the captive user(s), and
(ii) Not less than fifty one percent of the aggregate electricity generated in such plant, determined on an annual basis, is consumed for the captive use...." "In view of the above provisions, there are only two requirements for qualifying as a CPP:-
(a) Ownership of not less than 26% ; and Page 15 of 29 Appeal Nos. 75 & 69 of 2015
(b) Captive Consumption of not less than 51% of the aggregate electricity generated in such plant."
26. The Respondent No. 2 further submitted that it has consumed more than 51% of the aggregate power generated during the years in dispute and given the details as under:-
Financial year Total Generation Captive use - Percentage of units in 4x135 units captive use DCCP 2010-2011 636,710,682 300,879,731 53% 2011-2012 1,625,102,427 871,380,367 60% 2012-2013 2,506,657, 097 1,204,511,625 53%
In view of the above, it is clear that Respondent No.2/JSPL has fulfilled both the criteria i.e. Ownership of more than 26% and Quantum of power of self-consumption not less than 51% as prescribed under the Electricity Act, 2003.
27. The Respondent No.2 further submitted that the entire DCPP was acting as CPP from the date of inception i.e. from DPR stage and this fact has been duly accepted by the State Commission in the various orders issued even before the Impugned Order dated 02.01.2015.
28. The Respondent No. 2 further submitted that there is no requirement under the prevailing regulations that restricts unit 3 & 4 have to be permanently disconnected or isolated from the CTU for the purpose Page 16 of 29 Appeal Nos. 75 & 69 of 2015 of connection with the State Grid. On the other hand, the relevant provisions contained in the various Regulations envisage the connectivity for generator to STU as well as CTU.
29. The Respondent No.2 further submitted that the contractual commitment with CTU for utilization of open access capacity is not of any relevance for determination of captive status of DCPP. Any generating unit whether an IPP or CPP could be connected either to ISTS or STU or both as per Indian Electricity Code (IEC). In this context, it is submitted that Units 1 & 2 of DCPP are connected to STU after taking appropriate approval from the State Load Despatch Centre and units 3 & 4 of DCPP are connected to Inter-State Transmission system of CTU after taking appropriate approval from CTU. At any point of time only two units of DCPP would be connected to STU which meant that the maximum capacity of DCPP to the State Grid would be the same and the same undertaking was given by the Respondent No.2 while obtaining connectivity of DCPP.
30. The Respondent No.2 submitted that this Tribunal's Judgment dated 30.04.2013 as quoted by the Appellant above, wherein it was held that to calculate or identify a CPP in accordance with each independent unit and not for an aggregate consumption of both the Page 17 of 29 Appeal Nos. 75 & 69 of 2015 units. In the opinion of Respondent No.2, the said Judgment of this Tribunal is not applicable in the present case since DCPP is fully owned by Respondent No.2. In case a CPP is established by an industrial company for its own use, then only the twin test of ownership and captive consumption as provided in law has to be taken into consideration for determining the status of CPP and it further stated that since twin test for determining CPP status was fully passed in the present case, the State Commission very rightly vide its earlier orders dated 01.07.2013 and 05.03.2013 upheld the captive status of DCPP and further submitted that these orders have never been appealed and, therefore, attained finality.
31. The Respondent No.2 further stated that the demand of cross-
subsidy surcharge by the Appellant is patently unlawful. It has further submitted that the parallel operation charges since November, 2011 have duly been paid by the Respondent No.2 to the concerned authorities.
32. With regard to switchover from CTU to STU, as stated by the Appellant is violating the safety norms as prescribed in the State Grid Code, Respondent No. 2 stated that till date, the Appellants have not raised the issue of safety, if any, with them and the Appellants have Page 18 of 29 Appeal Nos. 75 & 69 of 2015 failed to issue any notice or brought on record any instance to show that the supply of electricity from units 3 & 4 of DCPP has caused any safety violation/concern in relation to the grid.
33. The Learned Counsel for the State Commission defended the Impugned Order dated 02.01.2015 issued by the State Commission and stated the Judgment of the State Commission was relied on the following documents submitted by the Respondent No.2:-
(a) Copy of the Detailed Project Report for phase 2 of the 4 x 135 MW DCPP of JSPL
(b) Copy of the Permission granted by Chief Electrical Inspector, Raipur for HT installation for proposed captive power plant at 4 x 135 MW phase 2 Dongamahua unit 3 & 4 dated 23.02.2011;
(c) Copy of the Permission granted by Chief Electrical Inspector dated 28.12.2010 for proposed 2 x 135 MW units 4 x 135 MW phase 2 captive power plant, Dongamahua;
(d) Licence to import and store Petroleum in an installation;
(e) Copy of Renewal of Consent under Water (Prevention and Control of Pollution) Act 1974;
Page 19 of 29
Appeal Nos. 75 & 69 of 2015
(f) Copy of Provisional Order by Boiler inspectorate, Raipur under Indian Boilers Act, 1923; and
(g) Copy of the Licence to work a factory.
It is submitted that the above documents demonstrate that from its very inception starting with the DPR stage, all the four units were classified as captive generating plants to secure its captive energy requirement of its steel plant and surplus power after captive usage was proposed to be sold in the national market for which it has availed connectivity with the CTU and in support of the same, the relevant portion of the Central Commission's Order dated 09.05.2011 passed in Petition No. 105 of 2010 relating to application for grant of Inter-State Transmission license is reproduced below:- "2. The applicant has submitted that Jindal Power Limited (JPL) has set up a generating station of 1000(4x250) MW Thermal Power Plant at Tamnar in Raigarh District of Chhattisgarh. As part of the generation project, JPL has established 258 km dedicated transmission line i.e. 400 kV D/C Transmission Line from JPL, Tamnar Power Plant to Power Grid Corporation of India Limited (PGCIL) substation at Kumhari in Raiapur District of Chhattisgarh for evacuation of power from the place of generation to the interconnection point for onward inter-State Transmission. The applicant has further submitted that Jindal Steel and Power Limited (JSPL) is engaged in the business of manufacture of steel and steel products. JSPL has independently established captive power plants at Raigarh for an aggregate capacity of 358 MW and is in the process of commissioning an additional 540 MW at Dongamahua, Page 20 of 29 Appeal Nos. 75 & 69 of 2015 Raigarh District. The power units of JSPL are connected to the swtichyard of the generation project of JPL. JSPL has some surplus generation from time to time which it is in a position to sell to third parties subject to applicable laws and regulations.
5. The applicant vide its affidavit dated 19.04.2011 has submitted that the Jindal Steel and Power Limited (JSPL) vide Power of Attorney dated 5.11.2008 authorised it to do all such acts as was necessary for obtaining long-term open access with Central Transmission Utility (CTU) for evacuation of its power. It has been further submitted that in pursuance of the said Power of Attorney, long term open access was applied by the applicant on behalf of JSPL for transmission of 400 MW though PGCIL line and the applicant vide its letters dated 16.09.2009 and 29.09.2009 brought to the notice of PGCIL that the said 400 MW would comprise:-
(a) 175 MW from 4x250 MW power plant at Tamnar;
(b) 225 MW to be injected ex-bus, JPL from 4x135 MW captive plant at Dongamahua.
6. The petitioner has further submitted that a Bulk Power Transmission Agreement (BPTA) was signed on 24.2.2010 between the JPL and PGCIL for 400 MW of power with bifurcation of 225 MW from 4x135 MW captive power plant at Dongamahua of JSPL and 175 MW from existing 4x250 MW Tamnar Thermal Power Station of JPL. Even though the name of JSPL is missing in the LTOA granted by PGCIL and BPTA signed on 24.2.2010, it is evident that JSPL has already obtained Long Term Open Access from PGCIL for transmission of 225 MW power from its captive power plant at Dongamahua. It has been further submitted that considering that JSPL has already authorised JPL to obtain LTOA on its behalf and also that there is no change in the location of plant nor change in the quantum of power, the application already made should be treated as having been made on behalf of JSPL"
Page 21 of 29
Appeal Nos. 75 & 69 of 2015 As mentioned above, the connectivity with the CTU sought by the Respondent No.2 for 225 MW was from the 4 x 135 MW captive power plant of DCPP and the grant of transmission licence to the Respondent No.2 was accorded by the Central Commission vide its above order.
34. The Learned Counsel for the State Commission stated that the State Commission in the present Petition has reiterated its earlier decision made in various petitions (including period under dispute) and held that 4x135 MW power plan of Respondent No.2 is maintaining captive status and, therefore, levy of cross-subsidy surcharge for said period will not be applicable, however, parallel operation charges will be leviable as per prevailing Rules & Regulations.
35. The State Commission also stated in the Impugned Order that if there is any allegation for violation of grid code etc., the State Commission was of the view that the said issue has to be decided separately and can not become subject matter of levy of cross-subsidy surcharge on the ground that on account of connectivity with CTU, unit No. 3 & 4 of DCPP have lost their CPP status.
Page 22 of 29
Appeal Nos. 75 & 69 of 2015
36. After having gone through the submissions as made above, we do not find any ground to consider units 3 & 4 of DCPP not under captive status even considering the fact that the Respondent No.2 has obtained open access to sell the electricity in the market through CTU network. In light of the fact that the DCPP was from the inception itself developed as CPP and has passed twin test laid down in the statute i.e. the Respondent No.2 having equity share of more than 26% and electricity consumption for captive use not less than 51% of the total generation from such plant and in our observation, the Respondent No.2 has maintained captive status of all the four units of DCPP in the past years under question.
37. We also observed that all these aspects and the concerned documents submitted by the Respondent No.2 to the State Commission have been perused by the State Commission while concluding the matter and the relevant extracts of the Impugned Order dated 02.01.2015 is reproduced below:- "48. Under the provisions of Electricity Act, 2003 connectivity of TG-3 and TG-4 with CTU does not make them as IPP. As per the Electricity Rules, 2005 which provides a twin test for classifying a CGP. According to which the consumer of electricity must own at least 26% of the ownership of the CGP. Further, it must consume minimum 51% of the net generation of the CGP. In the present case, it is beyond doubt that the petitioner owns 100% share of TG-3 and TG- Page 23 of 29
Appeal Nos. 75 & 69 of 2015 4 and is consuming more than 51% of the net generation from the CGPs as has been accepted by the report of the Chief Electrical Inspector.
49. The Commission in its previous orders of determination of captive status of various CPPs in the State for the year 2010-11 and 2011-12 has admitted TG-3 and TG-4 of DCPP as a part of petitioner CGP and therefore it don't needs further elaboration. The respondent plea that TG-3 and TG- 4 are connected to the CTU, it is deemed to be an IPP is entirely misplaced because the status of IPP/ CGP is not based on connectivity but as per the Electricity Rules, 2005 it is based on ownership and consumption criteria alone, which is very clear from the reading of the above rules.
50. During the arguments, the petitioner was advised to explain whether he has taken all possible steps in declaring TG-3 and TG-4 as captive units. In response, the petitioner through its petition and rejoinder also relied on the affidavit dated 15.05.2014 has enclosed additional documents which, inter alia, relied on the following:- "3. That the issue in the instant petition is with regard to the captive status of JSPL's 4x135 MW power plant at Dongamahua, in particular with regard to unit 3 and unit 4. In this regard, JSPL is seeking to file the following additional documents to substantiate its contention."
For establishing that, the petitioner has established all the 4 units of 135 MW at Village Dongamahua was for captive purpose, he has submitted following documents:
(a) Copy of the Detailed Project Report for phase 2 of the 4 x 135 MW DCPP of JSPL;
(b) Copy of the Permission granted by Chief Electrical Inspector, Raipur for HT installation for proposed captive power plant at 4 x 135 MW phase 2 Dongamahua unit 3 & 4 dated 23.02.2011;
Page 24 of 29
Appeal Nos. 75 & 69 of 2015
(c) Copy of the Permission granted by Chief Electrical Inspector dated 28.12.2010 for proposed 2 x 135 MW 13.8 KV TG sets at 4 x 135 MW phase 2 captive power plant, Dongamahua;
(d) Licence to import and store Petroleum in an installation;
(e) Copy of Renewal of Consent under Water (Prevention and Control of Pollution) Act 1974;
(f) Copy of Provisional Order by Boiler inspectorate, Raipur under Indian Boilers Act 1923; and
(g) Copy of the Licence to work a factory.
51. From the above documents submitted by the petitioner will unequivocally demonstrate the petitioner from its very inception starting with the DPR, it is proposed that all four units were classified as captive generating plants of JSPL. To secure its captive energy requirement of his steel plant and the surplus power was proposed to be sold in the national market for which he has availed connectivity with the CTU for which CSPDCL has annexed the order of the Central Commission dated 09 05 2011 Passed in Petition No. 105 of 2010 relating to application for grant of inter- State license through JPL. In the said order at paragraph 2 it is, inter alia, provided as follows:
"2. The applicant has submitted that Jindal Power Limited (JPL) has set up a generating station of 1000(4x250) MW Thermal Power Plant at Tamnar in Raigargh District of Chhattisgarh. As part of the generation project, JPL as established 258 km dedicated transmission line i.e. 400 kV D/C Transmission Line from JPL, Tamnar Power Plant to Power Grid Corporation of India Limited (PGCIL) substation at Kumhari in Raipur District of Chhattisgarh for evacuation of power from the place Page 25 of 29 Appeal Nos. 75 & 69 of 2015 of generation to the interconnection point for onward inter-State transmission. The applicant has further submitted that Jindal Steel and Power Limited (JSPL) is engaged in the business of manufacture of steel and steel products. JSPL has independently established captive power plants at Raigarh for an aggregate capacity of 358 MW and is in the process of commissioning an additional 540 MW at Dongamahua, Raigarh District. The power units of JSPL are connected to the switchyard of the generation project of JPL. JSPL has some surplus generation from time to time which it is in a position to sell to third parties subject to applicable laws and regulations."
Further in paragraph 5 and 6, it is also provided as follows:-
"5. The applicant vide its affidavit dated 19.4.2011 has submitted that the Jindal Steel and Power Limited (JSPL) vide Power of Attorney dated 5.11.2008 authorized it to do all such acts as was necessary for obtaining long-term open access with Central Transmission Utility (CTU) for evacuation of its power. It has been further submitted that in pursuance of the said Power of Attorney, long term open access was applied by the applicant on behalf of JSPL for transmission of 400 MW through PGCIL line and the applicant vide its letters dated 16.9.2009 and 29.9.2009 brought to the notice of PGCIL that the said 400 MW would comprise,-
(a) 175 MW from 4x250 MW power plant at Tamnar;
(b) 225 MW to be injected ex-bus, JPL from 4x135 MW captive plant at Dongamahua.
Page 26 of 29
Appeal Nos. 75 & 69 of 2015
6. The petitioner has further submitted that a Bulk Power Transmission Agreement (BPTA) was signed on 24.2.2010 between the JPL and PGCIL for 400 MW of power with bifurcation of 225 MW from 4x135 MW captive power plant at Donga Mahua of JSPL and 175 MW from existing 4x250 MW Tamnar Thermal Power Station of JPL. Even though the name of JSPL is missing in the LTOA granted by PGCIL and BPTA signed on 24.2.2010, it is evident that JSPL has already obtained Long Term Open Access from PGCIL for transmission of 225 MW power from its captive power plant at Dongamahua. It has been further submitted that considering that JSPL has already authorized JPL to obtain LTOA on its behalf and also that there is no change in the location of plant nor change in the quantum of power, the application already made should be treated as having been made on behalf of JSPL."
52. From the various submissions made by the petitioner and respondent, at no stage, it is observed that JSPL is operating its plant in the two systems parallelly. Further, the ability to switch from the CTU to the STU system was done with the full knowledge and approval of the Chief Electrical Inspector as is evidenced in the approved line diagram. The Chief Electrical Inspector while computing/ certifying the energy data for the year 2010-11 and 2011-2 was fully aware of the fact that JSPLs TG-3 and TG-4 was supplying power through the CTU and also self consuming power during the period when TG- 1 and TG-2 were in outage. At no stage has the Chief Electrical Inspector placed any objection to the said arrangement or issued any show cause notice to JSPL. Even if there is an allegation of violation of Grid Code etc., the said issue has to be decided separately and cannot become a subject matter of levy of cross subsidy surcharge on the ground that on account of Page 27 of 29 Appeal Nos. 75 & 69 of 2015 connectivity with CTU TG-3 and TG-4 have lost their CGP status."
38. We observed that the State Commission have gone through all the relevant provisions contained in the various Regulations for according the captive status to all the four units of DCPP and they have been consistent in maintaining the same stand even in the earlier orders issued by them and very rightly so.
39. In our opinion, the DCPP has been envisaged as captive power plant right from the inception and meets both the stipulated conditions discussed above for obtaining captive status irrespective of the fact that it is besides connected to STU is also connected to CTU, it would retain its status as captive so long as it passes twin test as laid down in the law.
40. As regards the violation of various safety considerations brought out by the Appellant, the Appellant is free to initiate any action in accordance with the law provided the Appellant is able to establish the same and in that case, penal provisions as contained in various Regulations would be attracted without fail. Page 28 of 29
Appeal Nos. 75 & 69 of 2015 ORDER
41. In light of the above, we find no merit in the Appeals filed by the Appellants and as such, these Appeals are hereby dismissed. The Impugned Order dated 02.01.2015 passed by the State Commission does not suffer from any defect and is hereby upheld. No order as to costs.
Pronounced in the open court on this 2nd day of February, 2016.
(I.J. Kapoor) (Justice Ranjana P. Desai)
Technical Member Chairperson
√
REPORTABLE/NON-REPORTABLE
dk
Page 29 of 29


Philips Norelco Oneblade Pro is the best electric shaver ever, and it’s down to its lowest price in months
by Maren EstradaWe’ve spoken to a lot of people about which electric shaver and trimmer is their favorite, since it’s such an important product that people use all the time. It’s not even really a competition at this point — the Philips Norelco Oneblade Pro Hybrid Electric Trimmer and Shaver is the overwhelming favorite. If you don’t already have one, you need one, and it’s on sale right now for $59.99. We haven’t seen the Oneblade Pro this cheap in months, so definitely take advantage before it sells out.
Philips Norelco Oneblade QP6520/70 Pro Hybrid Electric Trimmer and Shaver
$59.99
Available from Amazon
BGR may receive a commission
Buy Now
Here’s some important info from the product page:
- Rechargeable OneBlade can do it all – trim, edge, and shave any length of hair
- Shave is not too close so your skin stays comfortable.Automatic voltage 100-240 Volts Max power consumption 5.4 W
- More advanced than the original OneBlade, Pro features a powerful Li-Ion battery and 14 length settings
- Can be used wet or dry;Battery charge time:1 hour
- Replaceable blade lasts up to 4 months. (Based on 2 full shaves per week. Actual results may vary.)
- Number of blades: one
Philips Norelco Oneblade QP6520/70 Pro Hybrid Electric Trimmer and Shaver
$59.99
Available from Amazon
BGR may receive a commission
Buy Now
Follow @BGRDeals on Twitter to keep up with the latest and greatest deals from around the web. Quantities may be limited. Prices are subject to change without notice and coupons may expire at any time. Some deals may not be available to all customers. BGR may receive a commission on orders placed through this article.


SHAShort is the first and only URL shortening service to only use cryptographically secure hashing functions in the process of shortening, thereby making it computationally infeasible to reverse-engineer the original URL from the shortened link. That isn't something you should care about, but I did it anyway.
We also have an API, because the internet deserves SHA-512'ing URLs as a service.


Computer Survey
Questions:
Which of the following OSes do you use:
Windows
Apple
Linux
Other
Personal Info:
Postal Code:
Yearly Income:
Gender (at birth):
Male
Female


Which equation links currency arbitrage, deep Q-learning and light transport? In this enlighted (and enlightning) blog post, Mr. Jang revisits three problems that look distant at first, and put them under the common scope of the Bellman-Ford algorithm. The section on reinforcement learning in particular could very well serve as an introduction on post-2017 advances in Q-learning.
We propose Helix, a declarative machine learning system that accelerates iterative development by optimizing workflow execution end-to-end and across iterations. Helix minimizes the runtime per iteration via program analysis and intelligent reuse of previous results, which are selectively materialized -- trading off the cost of materialization for potential future benefits -- to speed up future iterations. Additionally, Helix offers a graphical interface to visualize workflow DAGs and compare versions to facilitate iterative development.
This report is a few pages long. Note that their proposed system is under Creative Commons NonCommercial-NoDerivates licence.
This is a 'work in progress' version of an online book that I am personally eager to read in more depth. The approach is quite different from a traditional textbook that goes depth first, exploring the ultimate details of specific topics, one after the other. Here it appears to be more horizontal by discussing problem cases and going over the different tools one can use to solve them. I found the explanations extremely clear, which makes me think this book will become a great read for beginners.
The title of the project is self-explanatory. The author goes over a sign-language recognition project and provides design decisions along the way. I particularly liked how he analysed the problem and was able to use Tensorflow.js as a tool to go from idea to prototyping in a short amount of time.
The big show of the last weekend. Will a team of bots be able to beat profesionnal players on a real-life complex strategy game? Yes, 2 out of 3 times. Note however that for this third game, the AI was constrainted in its choice of heroes, which can be seen as a sort of handicap. Congrats to OpenAI! The blog post also features some super interesting videos that show what is happening behind the scenes. My favorite depicts problems researchers faced when working on this awesome project.
In this very exciting project, the company Primer aims to find people of importance who are lacking their dedicated Wikipedia page. For now the project focuses on people from the computer science field. In the blog post, they explain how they trained a network to digest large quantities of news articles and to cross-reference them to identify recurring names. The system is then able to generate sentences describing a summary of the findings and to link to the sources! In short, it is able to identify potentially missing pages from Wikipedia and to generate a draft for such a page. You can see what it generated for Andrej Karpathy. Did you know one of his hobbies was to solve Rubik's cubes?
What is meaning? The most striking successes of recent NLP seem to relate to language models where the mecanism of creating a word or a sentence seems to be decoupled from its meaning. In this post, Mr. Wolf summaries a large discussion that has happened on Twitter on this topic. He identifies the sub-discussions and the themes that were explored. This serves as a great introduction to understand a little better the landscape of NLP and the challenges to come.
If you ever had a five minutes conversation with me, you would know that I am a big fan of Pink Floyd, but also that I absolutely love Sacred. Sacred is a tool for tracking and monitoring experiments. On multiple occasions, I found it extremely useful to retrieve the parameters I have used for previous experiments but also to compare the results of different experiments. For the latter use-case, it is a bit more limited as it lets you only record scalar values and you have to write a custom script to be able to compare results across experiments. ml_board appears to be an interesting alternative to improve performance tracking in particular. The GUI integrates multiple types of metrics and natively lets you compare the results of different experiment. Will definitively give it a try!
The authors (and their institution) of every single paper published at NIPS 2017 were analysed to draw publication statistics. Some facts were not so surprising; for instance the United States is the first country in terms of publication index, both in industry (with Google and Microsoft leading the way) and in acamedia (with CMU, MIT and Standord University in top positions). However what can be surprising is the scale of US predominance, even when combining countries from the European Union and Switzerland. One criticism I would make is that DeepMind seems to have been categorised as a US company.


This tutorial is a hands-on guide which will demonstrate how to write a custom Keptn "notification" service.
If you'd rather follow the official documentation, it's here. If you prefer a Go-based example, my colleague Christian Kreuzberger gave a video walkthrough on Youtube.
Keptn "notification" services are standard services, they're known as "notification" services because they only listen and react to events.
They do not influence Keptn's workflow in any way.
Keptn services can be written in any language you choose.
A "notification" service workflow is something like this:
Every Keptn service requires a corresponding distributor. A distributor is a component which subscribes to Keptn events and forwards them your service. Think of a distributor as the "glue" between the Keptn core engine and your service.
Save the following content as a file called demo-service-distributor.yaml
:
apiVersion: apps/v1
kind: Deployment
metadata:
name: demo-service-distributor
namespace: keptn
spec:
selector:
matchLabels:
run: distributor
replicas: 1
template:
metadata:
labels:
run: distributor
spec:
containers:
- name: distributor
image: keptn/distributor:0.6.1
ports:
- containerPort: 8080
resources:
requests:
memory: "32Mi"
cpu: "50m"
limits:
memory: "128Mi"
cpu: "500m"
env:
- name: PUBSUB_URL
value: 'nats://keptn-nats-cluster'
- name: PUBSUB_TOPIC
value: 'sh.keptn.internal.event.project.create'
- name: PUBSUB_RECIPIENT
value: 'demo-service'
- name: PUBSUB_RECIPIENT_PORT
value: '80'
The important parts are the environment variables at the bottom.
Read as: "This distributor is subscribing to the sh.keptn.internal.event.project.create
event and will forward the event to the demo-service
on port 80
.
Apply this file: kubectl apply -f demo-service-distributor.yaml
Verify that the distributor pod is running: kubectl get pods -n keptn | grep demo
demo-service-distributor-*-* 1/1 Running 0 39s
The custom service we're creating will be built on an Apache webserver running PHP which listens on port 80
.
Notice that you decide what language your service is written in. As long as the service can accept an incoming HTTP request, you're free to implement in any language you choose.
Create a new Dockerfile
with the following content:
FROM php:apache
COPY index.php /var/www/html/index.php
RUN chown -R www-data:www-data /var/www
CMD ["apache2-foreground"]
In the same folder as your Dockerfile
create another file called index.php
:
<?php
/* Create and open the log file
* Root directory is /var/www/html/
* So this log file is: /var/www/html/demoService.log
*/
$logFile = fopen("demoService.log", "a") or die("Unable to open file!");
// Get the incoming data from Keptn
$entityBody = file_get_contents('php://input');
// Decode the incoming JSON event
$cloudEvent = json_decode($entityBody);
/* Your logic here...
* Write a log file entry into the /var/www/html/demoService.log
*/
fwrite($logFile,"Project Created: " . $cloudEvent->{'data'}->{'project'} . "\n\n");
// Close handle to log file
fclose($logFile);
?>
Whenever the distributor detects an sh.keptn.internal.event.project.create
event, it passes the event to this custom service.
This service will parse the incoming keptn event then write a log line. This log file is stored at /var/www/html/demoService.log
inside the demo-service
pod.
The log line will look like this:
Project Created: <project-name>
Build and push your custom service to DockerHub. Be sure to substitute your Docker ID into the following command:
docker build -t <your-docker-username>/keptn-demo-service:notification . && docker push <your-docker-username>/keptn-demo-service:notification
Create a file called demo-service.yaml
.
Be sure to substitute your docker ID into the image:
line
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: demo-service
namespace: keptn
spec:
selector:
matchLabels:
run: demo-service
replicas: 1
template:
metadata:
labels:
run: demo-service
spec:
containers:
- name: demo-service
image: <your-docker-username>/keptn-demo-service:notification
imagePullPolicy: Always
ports:
- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
name: demo-service
namespace: keptn
labels:
run: demo-service
spec:
ports:
- port: 80
protocol: TCP
selector:
run: demo-service
Apply this file:
kubectl apply -f demo-service.yaml
Verify that both the service
and distributor
pods are running:
kubectl get pods -n keptn | grep demo
demo-service-*-* 1/1 Running 0 24s
demo-service-distributor-*-* 1/1 Running 0 39s
Your custom service is now implemented and running. You're now ready to test the custom service.
Every Keptn project requires a shipyard file. This defines the structure of the project.
Create a basic single stage shipyard.yaml
file:
stages:
- name: "quality"
Create a project then check the demo-service
container log demoService.log
. The creation of the project should be logged to this file.
Create the project:
keptn create project demo-project --shipyard=shipyard.yaml
You should see the following output:
Starting to create project
ID of Keptn context: ***
Project demo-project created
Stage quality created
Shipyard successfully processed
Retrieve the demo-service
pod name:
kubectl get pods -n keptn | grep demo
Substitute your pod name into the following command and execute:
kubectl exec -n keptn <your-pod> -- cat /var/www/html/demoService.log
You should see:
Project Created: demo-project
Congratulations. You've built a custom Keptn service which listens for an event and reacts to that event.
Now that you understand the basics, go forth and integrate with any other third-party tooling!


...
Id
Creation date
First Name
Last Name
Tenants
Complete register
Status
See
Id
Creation date
First Name
Last Name
Tenants
Complete register
Status
See


Colors - Protonic Blue and Grey Metalic
Ionic Metallic Silver and BMW i Blue
Crystal White and Frozen Metallic Grey
Crystal White and BMW i Blue
Sophisto Grey and Frozen Metallic Grey
Sophisto Grey and BMW i Blue
Horse Power (Electric Engine) - 131hp
Battery Range - Up to 23 Miles
CO2 Emissions - 49g/km
Interior Extras - Neso - Standard
Carpo Light - £1,150
Carpo Dark - £1,150
Halo - £2,150
Pure Impulse Design Package - £12,200


|
cds
1.2.0
|
Retired pointer. More...
#include <cds/gc/details/retired_ptr.h>
Public Types | |
| typedef void * | pointer |
| Pointer type. |
Public Member Functions | |
| retired_ptr () | |
| Default ctor initializes pointer to NULL. | |
| retired_ptr (pointer p, free_retired_ptr_func func) | |
| Ctor. | |
| template<typename T > | |
| retired_ptr (T *p, void(*pFreeFunc)(T *)) | |
| Typecasting ctor. | |
| retired_ptr & | operator= (const retired_ptr &s) |
| Assignment operator. | |
| void | free () |
| Invokes destructor function for the pointer. |
Static Public Member Functions | |
| static bool | less (const retired_ptr &p1, const retired_ptr &p2) |
| Comparison of two retired pointers. |
Data Fields | |
| pointer | m_p |
| retired pointer | |
| free_retired_ptr_func | m_funcFree |
| pointer to the destructor function |
Retired pointer.
Pointer to an object that is ready to delete.


--- layout: default meta: Description of the page --- {% for posts in site.posts %} {% include partials/episode.html %} {% endfor %} {% include list.html %} {% include about.html %} {% include questions.html %} {% include faq.html %}


  I recommend the 100 health per level rule (e.g. at level 50, have at least 5000 – and at level 90 have at least 9000).
While this build can facetank later on with great DA, you are a kiter. You run around and avoid taking any damage, and often kill everything (including mini-bosses) before they even have a chance to reach you. If you do get some great DA and health early on, facetanking with Fire Strike is devastating and you’ll kill bosses 2x (or more) faster. You’ll get a feel for what works or not rather quickly.
Survival revolves around a combination of Blast Shield, Word of Renewal, Flashbang and kiting. Synergizing each of these allows you to down most any content in the game (paired with the right equipment). It takes time to get this down, but the good thing is farming up to Ultimate (and even the beginning of Ultimate) is such a cakewalk, you’ll have plenty of time to get it down.
Rotation for Trash: Toss your Blackwater Cocktail or Rune of Kalastor when it’s on cooldown… that’s all.
Rotation for Bosses: (Kite) Thermite Mine in area, Blackwater Cocktail in controlled area, Rune of Kalastor behind you as you’re being chased, Flashbang when necessary, and Word of Renewal. Forget Fire Strike, it's too dangerous!

Leveling
This build can easily make 100 and faceroll Ultimate up to AoM with self-found gear, so don’t worry about having the BiS complete legendary sets. You only need those for the really tough end-game content. The end-game build of this character uses the 3-piece Justice set of armor, however you can also use the Infernal Knight Armor set, or even a Flame Keeper’s Armor set. Whatever you have the gear for, you can make it work!
While leveling, you’ll find these items to be very helpful:
Phase I
- Choose class
- 2 points into bar (Demolitionist 2/50)
- 1 point into Fire Strike (1/12)
- 3 points into bar (Demolitionist 5/50)
- 12 points into Blackwater Cocktail (12/12)
- 1 point into Flame Touched (1/12)
- 5 points into bar (Demolitionist 10/50)
- 1 point into Vindictive Flame (1/16)
- 1 point into Explosive Strike (1/12)
- 1 point inzo High Potency (1/1)
- 10 points into bar (Demolitionist 20/50)
- 1 point into Demon Fire (1/12)
- 1 point into Ulzuin’s Wrath (1/12)
- 20 points into bar (Demolitionist 40/50)
- 12 points into Agonizing Flames (12/12)
- 1 point into Thermite Mine (1/16)
- 1 point into Blast Shield (1/12)
Phase II
You should be around level 25 by now.
- Choose class
- 10 points into bar (Inquisitor 10/50)
- 1 point into Deadly Aim (1/12)
- 12 points into Word of Renewal (12/12)
- 5 points into bar (Inquisitor 15/50)
- 1 point into Rune of Kalastor (1/12)
- 5 points into bar (Inquisitor 20/50)
- 1 point into Vigor (1/10)
- 5 points into bar (Inquisitor 25/50)
- 10 points into Ignition (10/10)
- 1 point into Inquisitor Seal (1/12)
- 7 points into bar (Inquisitor 32/50)
- 1 point into Steel Resolve (1/10)
- 1 point into Flashbang (1/12)
- 1 point into Searing Light (1/10)
- 18 points into bar (Inquisitor 50/50)
- 12 points into Aura of Censure (12/12)
- 6 points into Thermite Mine (7/16)
Phase III
- 11 points into Deadly Aim (12/12)
- 1 point into Temper (1/12)
- 9 points into Steel Resolve (10/10)
- 11 points into Blast Shield (12/12)
- 11 points into Flame Touched (12/12)
- 11 points into Inquisitor Seal (12/12)
- 1 point into Null Field (1/1)
- Distribute the rest as you see fit!


Donald Trump attempts to meet with Soviet leader Mikhail Gorbachev, reportedly to sell him on his nuclear plan. This meeting never happened. At this time, Trump also began proclaiming his presidential ambitions and taking out newspaper advertisements harshly criticizing US foreign policy.
Source: Quartz


Cheech and Chong's Next Movie
Cheech and Chong's Next Movie is a movie starring Cheech Marin, Tommy Chong, and Evelyn Guerrero. The two stoners and their friends go through another series of crazy, drug-influenced misadventures.


| org.cschallenge.pinball.engine |
|
| org.cschallenge.pinball.loader |
|
| org.cschallenge.pinball.samples.empty |
|
| org.cschallenge.pinball.samples.GavinPlayer |
|
| org.cschallenge.pinball.samples.LeoPlayer |
|
| org.cschallenge.pinball.samples.teamA |
|
| org.cschallenge.pinball.samples.teamB |
|
| org.cschallenge.pinball.samples.teamK |
|
| org.cschallenge.pinball.samples.teamM |
|
| org.cschallenge.pinball.samples.teamQ |
|
| org.jarclassloader |
|
| org.jdesktop.core.animation.demos |
|
| org.jdesktop.core.animation.i18n |
Provides internationalized messages, in particular error messages, to
the Timing Framework.
|
| org.jdesktop.core.animation.rendering |
Core classes of a rendering framework that can support
both passive and active rendering approaches.
|
| org.jdesktop.core.animation.timing |
Core classes of the Timing Framework; these classes provide the base
functionality that all animations will use.
|
| org.jdesktop.core.animation.timing.evaluators |
Evaluator implementations for the standard Java numeric types.
|
| org.jdesktop.core.animation.timing.interpolators |
Several useful interpolator implementations for animations.
|
| org.jdesktop.core.animation.timing.sources |
Several useful timing source implementations for animations.
|
| org.jdesktop.core.animation.timing.triggers |
A simple mechanism for starting animations when specific events occur.
|
| org.jdesktop.swing.animation.demos |
|
| org.jdesktop.swing.animation.demos.splineeditor |
|
| org.jdesktop.swing.animation.rendering |
A flexible implementation of rendering on a Swing component that supports
both passive and active rendering approaches.
|
| org.jdesktop.swing.animation.timing.evaluators |
Evaluator implementations for the several useful Swing and Java2D types.
|
| org.jdesktop.swing.animation.timing.sources |
Timing source implementation for the Swing timer.
|
| org.jdesktop.swing.animation.timing.triggers |
A simple mechanism for starting animations when specific Swing events occur.
|


Dancing robots have come a long way since Mr. Roboto.
From popping and locking in mechanical fashion to contemporary dances incorporating massive machines, "doing the robot" may have a whole new meaning in the future.
Join us on the dance floor with breakdancing mimes, hoverboard acrobats, giant mechs, and adorable industrial instruments.
Are we human, or are we dancer?
...or are we robots?
The first performers to do a version of what would become "the robot" were silent film actors and mimes in the 1920s, who created comical dances in the stilted style of mannequins. This was also around the time in history when the word "robot" began to circulate in English, and the mannequin dance was mixed with the idea of a mechanical man.
According to one history, it was a mime performer named Robert Shields who inspired Charles "Robot" Washington, the dancer who popularized the robot as a dance move on the TV program Soul Train in the 1960s.
Washington's style was the predecessor for the robot becoming a classic dance as integral as popping, locking, and other breakdancing moves:
In the early 1970s, at the height of Jackson 5 mania, Michael Jackson did the robot as part of his choreography for "Dancing Machine," so he also takes some credit for bringing the robot into the mainstream. Honestly, is there a single dance trend that you can't trace back to MJ?
There are multiple other differing claims to the robot's origination; some sources say that dancers in Chicago and Los Angeles before Soul Train was nationally broadcast perfected the style. Others say it should be attributed to the locking master Don Campbell.
But it may be safe to say the style hasn't been truly perfected until you can't tell the difference between human and robot...
Dances With Robots
Modern dance has undoubtedly been influenced by technology, from live projection mapping to create digitally composited environments, to wearables that can create a data visualization of a ballerina's every move. So it shouldn't be surprising that contemporary choreographers are putting robots on their stages as well.
Most of these dances highlight the opposition between man and machine, while trying to create moments of tenderness and collaboration. Take for example, the caveman-like choreography in Seraph, performed in 2011 by MIT's CSAIL and the Pilobolus modern dance company, featuring a human and a few small drones:
While this kind of stark contrast between (mostly naked) man and (blinking, flying) machine is easy to communicate via modern dance, it is a rather straightforward narrative. Maybe it's a little more interesting when we try to incorporate robots seamlessly, without highlighting their opposition to our fleshy human nature.
While the hoverboard may not technically count as a robot, The RollBots, a group of acrobatic modern dancers formerly known as the "Acrobots," definitely blur the line between human and machine. They garnered over 5 million clicks for their rolling routine to Justin Bieber's "Sorry":
Dancing with robots has also served as a gateway to young women learning about hardware and software: these girls from the Young Women's Leadership School created a dance piece for the Annual NYC Computer Science Fair by programming their LEDs and Sphero robots to be part of the choreography.
Image if all the little girls who are pushed into ballet classes at age 5 also started learning to code at that age!
Robot rock
One of the hardest things about including robots in dance is their physical limitations. Most robots are not constructed to have the same flexibility as a human in their joints, or fluidity in their movement. However, that isn't stopping them from trying.
For 2016's Chinese New Year, 540 small, humanoid robots were programmed to perform a synchronized dance while drones dropped glitter from the sky:
The QRIO was a robot prototype similar to the ones that performed for Chinese New Year that was designed, tested, and marketed by SONY along with their robot dog AIBO in the early 2000s, but was never released commercially. A semi-holographic Beck was the first and seemingly only artist to get to use QRIO robots in his 2005 video for Hell Yes (and it may be only music video magic, but they are pretty funky little guys):
The Robotiq blog has listed several other examples of great robot dances, including this massive and uncomfortably smooth LG-branded robot spotted doing a two-step in Brazil in 2015:
Although many have assumed this footage is fake or part of some kind of viral marketing campaign, other videos have surfaced of similarly modeled robots dancing to Latin beats.
It looks like the giant robot battles that mecha animes have predicted for the future in Asia will actually be based in South America, and are more likely to be dance battles.
The big big bots
The biggest stars on the dance scene have come from a very unlikely background. They are ABB and KUKA robots, two of the world's leading manufacturers of industrial robot arms. In promotional videos, these robots have performed odd human tasks; maybe you've seen a KUKA face off in tennis against a world champion, or ABB robots playing snooker.
Thomas Freundlich, an internationally renowned Finnish choreographer and dance filmmaker, has used ABB robot arms in several of his pieces. In these excerpts from Actuator, a dance film from 2008, you can see how much the stakes are raised with the industrial equipment serving as robot duet partner, in comparison with the project using MIT's drones. In the first clip, a very 2001: A Space Odyssey moment finds the male dancer on his knees reaching for a stick (0:30), and when the ABB rears its head up as the embodiment of all technological progress (1:15-1:30) it is massive, powerful, godlike, but later dances alone to Billy Holiday (3:44) and is somehow able to express an approximation of longing as its body/arm writhes and extends outwards.
KUKA robots have also gotten in on the stagecraft game, teaming up with the Blue Man Group in Las Vegas to help those indigo boys bust out some beats:
But sometimes even hard-working industrial robots just want to have fun, too! Robolounge is a group dedicated to creating performances using industrial robots artistically, and are available to create choreography for a variety of types of events and spaces. They even offer custom special effects like adding lightsabers to the robots' arms.
First they take all the auto factory jobs, now they're coming for the Blue Men and the go-go girls! But until they can pirouette off of those stands and do a little more than a full-body arm wiggle, it seems like human dancers are, well... as secure in their profession as most artists these days.
Robots, like all technologies that change the way we relate to our bodies and selves, will continue to influence the art of dance.
We're sure to see more humanoid robots learning to boogie, and maybe even some designed to pull moves beyond human capability.
Man and machine will waltz into the future together: warm, meaty cheek to cold, metal cheek.


LinkX allows you to set the format that you want dates and times displayed in. Many countries use differing formats to display their dates and times, so this feature will allow you to have your dates and times in a format that the majority of your visitors will understand. The date and time format system used by LinkX is based on the date and time format feature of PHP. If you have experience working with PHP date and time formats, you'll have no problem with these. Even if you don't, these formats are very straightforward and easy to understand.
Changing Formats
The date and time formats you want to use are configured through the LinkX General Settings interface. In the control panel, select the General Settings option from the Settings menu. The General Settings pop window will display, and in the Basic Settings section you will find the Date Format and Time Format fields. This is where you will make the changes to your date and time formats. Once you have made the changes you want, press the Save Options button to save your new settings.
Date and time format specifiers consist of a series of characters. You can find a complete list of these characters below for both dates and times. Using a combination of these specifiers you can create complete date and time formats. Note that LinkX will only pay attention to the defined characters; all other characters in your date or time format will be left alone. This allows you to use separators such as forward-slashes, dashes, and colons as you like.
Date Formats
d - day of the month, 2 digits with leading zeros; i.e. "01" to "31" j - day of the month without leading zeros; i.e. "1" to "31" D - day of the week, textual, 3 letters; i.e. "Fri" l - day of the week, textual, long; i.e. "Friday" M - month, textual, 3 letters; i.e. "Jan" F - month, textual, long; i.e. "January" m - month, 2 digits with leading zeros; i.e. "01" to "12" n - month without leading zeros; i.e. "1" to "12" Y - year, 4 digits; i.e. "1999" y - year, 2 digits; i.e. "99"Time Formats
a - "am" or "pm" A - "AM" or "PM" h - hour, 12-hour format; i.e. "01" to "12" H - hour, 24-hour format; i.e. "00" to "23" g - hour, 12-hour format without leading zeros; i.e. "1" to "12" G - hour, 24-hour format without leading zeros; i.e. "0" to "23" i - minutes; i.e. "00" to "59" s - seconds; i.e. "00" to "59"


visual
filter: url(svg-url#element-id)
.target { filter: url(#c1); } .anothertarget { filter: url(resources.svg#c1); }
| Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari (WebKit) |
|---|---|---|---|---|---|
| Basic support | ? | 3.5 (1.9.1) | --[*] | ? | ? |
| Feature | Android | Firefox Mobile (Gecko) | IE Phone | Opera Mobile | Safari Mobile |
|---|---|---|---|---|---|
| Basic support | ? | ? | ? | ? | ? |
[*] From Internet Explorer 5.5 to Internet Explorer 7.0 included, that browser implemented a non-standard filter
property. The syntax was completely different from this one and is not documented here.
mask
property


Student Information
Name
Email
Mobile No
Name of College
Year studying in
CGPA
Department
Fac-Ad
H.O.D
Dean
Father's Name
Father's Mob
Mother's Name
Mother's Mob