CWP No.3502 of 2012 1 IN THE HIGH COURT OF PUNJAB AND HARYANA AT CHANDIGARH CWP No.3502 of 2012 Date of decision: 24.7.2012 UEM India Private Limited -----Petitioner Vs. Haryana Urban Development Authority and others ----Respondents
CORAM:- HON'BLE MR. JUSTICE AJAY KUMAR MITTAL HON'BLE MR. JUSTICE GURMEET SINGH SANDHAWALIA Present:- Dr. Anmol Rattan Sidhu, Sr. Advocate with Mr. Vivek Sharma, Advocate for the petitioner.
Mr. D.V.Sharma, Sr.Advocate with Ms. Shivani Sharma,Advocate for respondent Nos.1 & 2. Mr. Rahul Sharma, Advocate for respondent No.3.
Ajay Kumar Mittal,J. ` `
1. The petitioner, an unsuccessful tenderer has filed this petition under Articles 226/227 of the Constitution of India challenging the action of respondent-Haryana Urban Development Authority in rejecting its bid vide notice dated 3.2.2012, Annexure P.4 and awarding of contract in favour of respondent No.3 in respect of the project for the construction of 120 MLD capacity Sewage Treatment Plant etc. at Village Behrampur, Gurgaon. Prayer has also been made for quashing Clause 3.1.7 of the Bid document, Annexure P.1 being illegal, arbitrary and without any justification.
2. A few facts relevant for the decision of this case, as narrated in the petition may be noticed. The petitioner is a company CWP No.3502 of 2012 2 incorporated under the Companies Act, 1956. It is engaged in the business of providing services of project development like planning, feasibility studies, engineering design, equipment/system supply and construction/installation. On 25.12.2011, respondent No.1 invited tenders from interested contractors having prescribed technical and financial credentials for construction of 120 MLD capacity Sewage Treatment Plant (STP) and Main Pumping Station (MPS) based on Activated Sludge Process(ASP)/Sequential Batch Reactor (SBR) Technology and 30 MLD capacity Tertiary Treatment plant and all other works contingent thereto including design, construction of Civil Works, Supply of Mechanical, Electrical and Instrumentation Works, Erection, Testing, Commissioning alongwith operation and maintenance for 72 months after stabilization period of 90 days on turnkey basis at Village Behrampur, Gurgaon. Pursuant to the said invitation, respondent No.1 issued bid documents for the project which were made available at its website. The petitioner-company filed its bid for the project through online submission as well as submission of physical documents on 21.1.2012 and 24.1.2012 respectively alongwith necessary documents within the stipulated period. Vide letter dated 31.1.2012, respondent No.1 sought clarification from the petitioner on certain issues. The petitioner replied to the said letter and submitted the documents as required. On 3.2.2012, Annexure P.4 the petitioner was informed that its bid had been rejected but no reasons were communicated. During the course of meeting with the officials of respondent No.1, the petitioner was CWP No.3502 of 2012 3 orally informed that its bid was rejected since it did not qualify the criteria of never having been blacklisted by any government authority.
3. According to the petitioner, earlier, it had bid for a project of Delhi Jal Board (DJB) for setting up of 70 MGD Kalyanpuri Pumping Station. The petitioner was in discussion with two pump suppliers viz. Grundfos and ITT Water and Wastewater LLC for providing technical assistance in relation to the said project. The petitioner first tied up with ITT Water and Wastewater LLC but subsequently, this firm refused to endorse Memorandum of Understanding on stamp paper and also refused to provide original Memorandum of Understanding duly signed by them on their letter head. Consequently, the petitioner entered into a Memorandum of Understanding with Grundfos on 3.8.2010 and submitted the same with DJB to fulfil the qualification criteria. On 11.2.2011, the petitioner received a show cause notice from DJB stating that decision had been taken to debar it from participating in the tenders on the ground that it had already forged certain documents to qualify for the project. On 30.5.2011, Annexure P.5, DJB issued circular blacklisting and debarring the petitioner from participating in any tender for a period of one year for submitting forged documents for Kalyanpuri project. Thereafter, the petitioner submitted various representations before DJB. Ultimately, DJB reviewed its decision and withdrew the debarment vide letter dated 11.8.2011, Annexure P.6. Inspite of that, respondent No.1 rejected the bid of the petitioner vide impugned notice dated 3.2.2012, Annexure P.7. Hence this CWP No.3502 of 2012 4 petition.
4. Notice of the petition was issued. Separate written statements have been filed on behalf of respondent Nos. 1 & 2 on one hand and respondent No.3 on the other. In the reply filed on behalf of respondent Nos. 1 and 2, the averment regarding withdrawal of the action for debarment of the petitioner on 11.8.2011 has been disputed. It has been stated that the order dated 30.5.2011 had never been withdrawn vide Annexure P.6 but the period had been reduced after review from one year upto the date of issuance of the review letter. It has been further stated that financial bid of the petitioner was never opened. As regards the averment of the petitioner that financial bid had been opened on 3.2.2012, it has been submitted that as per the information available on the website, the message shown is "Financial/Price Bid cancelled or Rejected Bid.", Annexure R.2. According to respondent Nos. 1 and 2, the petitioner seems to have created a forged web site/portal of HUDA to show that its commercial bid was opened. In this regard, the petitioner has produced Annexure P.9 with the writ petition. On enquiry, it has been found that the petitioner has committed cyber crime by creating/forging a web site/portal of HUDA. As regards the prayer of the petitioner for quashing of Clause 3.1.7 of the Bid document, Annexure P.1, it has been stated that the petitioner had accepted each and every term and condition of the tender document by signing the same. It is now estopped from challenging the said clause. It is also submitted that the petitioner was earlier awarded a contract for design, supply, CWP No.3502 of 2012 5 construction, installation etc. for a period of three years. The petitioner delayed the said project as a result of which penalty was imposed upon it by HUDA. A show cause notice dated 29.3.2012, Annexure R.4 was also issued by Haryana State Pollution Control Board, Gurgaon to the petitioner under Section 33A of Water (Prevention and Control of Pollution) Act, 1974 as the samples were not found in accordance with the specified standards. It has been further submitted that in view of clause 3.1.10, the petitioner was not eligible for allotment of tender as the performance of the applicant for execution of similar work in HUDA was also required to be considered. On these premises, prayer for dismissal of the petition has been made.
5. An additional affidavit on behalf of respondent-HUDA was also filed explaining the position with regard to Annexure P.9 appended by the petitioner. It was submitted that a unique user ID and password had been assigned to all the bidders who had given bid for tender No.306. Therefore, all the bidders could only use the same to submit their price bid. During the technical evaluation, bid of the petitioner had been rejected as is evident from Open tender details, Annexure R.7. Thus, as a result once the bid of the petitioner had been rejected, the same could not have been opened by respondent HUDA. It was also clarified that e-tendering system of HUDA allows opening of financial bid of only those participating agencies which are duly shortlisted by the department during the technical evaluation stage. According to the respondents, Annexure P.9 is a screenshot CWP No.3502 of 2012 6 which has been managed by the petitioner on 3.5.2012 after the price bids of the qualified bidders had been opened by the respondent on 3.2.2012.
6. In the reply filed on behalf of respondent No.3, the averments made in the writ petition have been controverted on the similar grounds as have been taken by respondent Nos. 1 and 2. It has been further stated that respondent No.3 has already deposited a sum of Rs.90 lacs as security with respondent no.1. The possession of the site has also been handed over to it and it has completed the Survey work and soil investigation work. The designs and drawing of the project have also been submitted to respondent No.1 and the work of the excavation of the soil has already commenced at the site. It has thus been prayed that the writ petition may be dismissed with costs.
7. Learned counsel for the petitioner has raised following four contentions:-
i) Reference was made to the condition of black-listing incorporated in the notice inviting tenders for Joint Ventures in Sub Clause (e) of Clause 1.6 of Condition No.<IP_ADDRESS> which is as under:-
"(e) All the members of the JV shall certify that they have not been blacklisted or debarred by HUDA or any other Ministry/Department of the Government of India/State Government from participation in tenders/contract on the date of opening of bids either in their individual capacity or the JV firm or partnership firm in which they were members/partners."
Attention of the Court was also drawn to Blacklisting Condition No.3.1.7 in the case of an applicant other CWP No.3502 of 2012 7 than Joint Venture which reads thus:-
"3.1.7. The applicant should submit an undertaking in the form of an affidavit on stamp paper of Rs.10/- to the effect that they (Applicant/firm) have never been black- listed/debarred in any Government Department. If any applicant is black-listed by any department, they will not be considered."
It was urged that the condition of blacklisting in Condition No.3.1.7 viz-a-viz blacklisting in Sub Clause (e) of Clause 1.6 of Condition No.<IP_ADDRESS> was arbitrary as in case of a joint venture, it was only on the date of opening of bids that the person was not required to be blacklisted whereas in the case of an individual applicant/firm, who has been blacklisted by any department was debarred from furnishing the tender;
ii) the eligibility of respondent No.3 was sought to be challenged as technical eligibility in condition <IP_ADDRESS> of the tender notice was not complied with. It was also submitted that no parity was being maintained by the respondents as under similar circumstances, the bids of other tenderers had been rejected by the respondent Nos. 1 and 2;
(iii) the price bid of the petitioner was opened on 3.2.2012 and once that was so, the petitioner being the lowest bidder, the price bid should have been accepted. The petitioner had given a bid of Rs.87,90,90,000/- whereas the bid which had been accepted of respondent No.3 was Rs.98,10,00,000/-. In such a situation, acceptance of bid of respondent No.3 was malafide and liable to be struck down;CWP No.3502 of 2012 8
iv) blacklisting of the petitioner had been waived by the respondent and in such a situation, there was no bar for the petitioner's price bid to be considered.
8. Mr. D.V.Sharma, learned Senior counsel for respondent Nos. 1 and 2, controverting the submissions of learned counsel for the petitioner, had vehemently disputed that the price bid of the petitioner was opened by the respondents. It was urged that Annexure P.9 appended alongwith the writ petition was a forged document. It was also urged that respondent Nos. 1 and 2 had filed an affidavit refuting the averment of the petitioner that the price bid had been opened to which no rejoinder had been filed. Reference was also made to Annexures R.1, R.2 and R.3 appended alongwith the written statement wherein a communication addressed by the petitioner was relied upon in which it was admitted by the petitioner that the price bid had not been opened till 20.2.2012. It was further submitted that in the original unamended writ petition, there was no averment with regard to opening of price bid of the petitioner on 3.2.2012. Learned counsel further submitted that cumulative effect of this fact only leads to one conclusion that the petitioner had fabricated Annexure P9 as the date thereon shows that it was generated on 3.5.2012. Conversely, it was argued that in case price bid had been opened then there was no reason for the petitioner not to mention this fact in the communications which had been appended as Annexures R.1, R.2 and R.3. Learned counsel further submitted that the petitioner had not approached this Court with clean hands and therefore, the writ CWP No.3502 of 2012 9 petition was liable to be dismissed with exemplary costs. It was also argued that the petitioner itself did not fulfil the condition as it was debarred from submitting the tender for three months from 30.5.2011 to 11.8.2011. With regard to the argument that the condition of debarring in case of joint venture and individual was bad, it was submitted that the petitioner had misinterpreted the provisions. Condition No.3.1.7 related to individual/firm and therefore, any person who had been blacklisted was not entitled to submit a tender. It was more onerous condition than in the case of joint venture that an applicant who had been debarred till the date of submission of the application form was blacklisted, was not entitled to submit a tender. It could not thus be arbitrary. It was also submitted that the petitioner having participated in the tender process could not now be allowed to raise this objection.
9. Mr. Rahul Sharma, learned counsel for respondent No.3 in addition to the submissions already made by respondent Nos. 1 and 2 submitted that debarring of the petitioner was not disputed and therefore he had no locus standi to file the writ petition. Reliance was placed on the Division Bench judgments of this Court in U.G.Hospitals Private Limited v. State of Haryana and others, 2009 (1) PLR 329 and Baba Bhani Giri Ji Warehousing v. Food Corporation of India and others, CWP No.228 of 2012 decided on 6.3.2012. It was also urged that there was no malafide attributed to any bid on the basis of which it could be said that the contract had been given for extraneous considerations. Learned counsel argued CWP No.3502 of 2012 10 that the respondent No.3 fulfilled the technical eligibility condition mentioned in Condition No.<IP_ADDRESS> and the argument of learned counsel for the petitioner to the contrary did not carry any weight. Lastly, it was contended that under the circumstances, the action of respondent Nos. 1 and 2 was not open to judicial review in view of various pronouncements of the Hon'ble Apex Court.
10. After hearing heard learned counsel for the parties and perusing the record, we do not find any merit in the petition.
11. The issues raised in this petition would require to be examined with respect to the following points:-
a) Whether the petitioner after having participated and being unsuccessful is entitled to challenge the validity of Condition No.3.1.7?
b) Whether the respondent No.3 did not fulfil the conditions enumerated in technical eligibility under Condition No.<IP_ADDRESS>?
c) Whether the petitioner was eligible for opening of technical bid especially when the blacklisting of the petitioner had not been waived completely?
d) the scope of judicial review to evaluate the respective bids of the petitioner and respondent No.3.
Additionally, on the basis of argument raised by the respondent whether petitioner has not come to the Court with clean hands? If so, its effect?
12. Examining the challenge of the petitioner to validity of condition of blacklisting contained in Clause 3.1.7 viz-a-viz condition in sub clause (e) of Clause 1.6 of Condition No.<IP_ADDRESS>, it would not be open to the petitioner to question the legality of the aforesaid CWP No.3502 of 2012 11 condition at this stage after having participated in the tender and remaining unsuccessful therein. A Division Bench of this Court in U.G.Hospitals Private Limited's case (supra), examining similar issue where the petitioner had participated in the selection process for allotment of plot and later on had sought to challenge the validity of the criterion adopted by the respondents, in para 7 had held as under:-
"Having heard the learned counsel for the parties and perusing the paper book with their able assistance we are of the considered view that the advertisement Annexure P.1 clearly postulates the eligibility criterion. According to the criterion an individual/society/trust/institution/ company was eligible to apply but preference was to be given to (i) reputed/renowned institution/trust/society already running multi specialty hospitals (ii) NRI professionals in the field of Medical Science (iii) A team/group of Doctors/Specialists (iv) Retired Doctor/Retiring Doctors in the near future from an eminent medical institutions/ government hospitals (v) Doctors already running hospitals/nursing homes. It is stipulated that preference was to be given to applicants hailing from Haryana State and (vi) allotment was to be made on the basis of professionals as well as financial capability to run the hospital. The petitioner as well as respondent no.5 had applied in time alongwith requisite earnest money. Both the applicants are private limited companies. The petitioner is associated with Metro Heart Institute whereas respondent no.5 has been attached with Apollo Hospital Group. After interview of both the applicants, the high profile committee recommended the case of respondent no.5 for allotment which has been accepted by the Government. It is well settled that once the petitioner has participated in the selection process for allotment of a plot then it looses the right to question the CWP No.3502 of 2012 12 allotment on the ground of adopting irrational criterion. The principle in the nature of estoppel would be attracted in such a case. In a number of cases where the candidate has participated in the selection process for induction in service, the Supreme Court has held that such a candidate cannot be permitted to question the selection process when he has remained unsuccessful. The principles laid down in those cases would fully apply to the facts of the present case. We may place reliance in that regard on the judgements of Hon'ble the Supreme Court in the case of Chandra Prakash Tiwari V. Shakuntla Shukla (2002) 6 SCC 127; Madan Lal v . State of Jammu and Kashmir (1995) 3 SCC 486 and Om Parkash Shukla v . Akhilesh Kumar S harma (1996) suppl. SCC 285."
13. Under the aforesaid condition, the applicant was required to certify that he has not been blacklisted or debarred by any Government department. The petitioner having participated fully knowing the implication of eligibility condition contained in 3.1.7 in the tender document is not entitled to challenge the validity thereof. Even otherwise, the petitioner was unable to demonstrate in what manner the said condition was arbitrary, unreasonable or irrational. The plea is, thus, rejected.
14. Taking up second point,it would be apposite to reproduce technical eligibility as contained in Condition No.<IP_ADDRESS> of the tender document relevant portion of which relating to the dispute reads thus:-
"a. In case of individual bidder:
The bidder must have successfully completed and commissioned in India during last 10 years ending 30.11.2011, either of the following:-CWP No.3502 of 2012 13
• One work of similar nature and capacity not less than 70 MLD.
OR • Two works of similar nature and capacity, each not less than 35 MLD.
Note: Similar nature of work means Sewage Treatment Plants (STP) based on conventional Activated Sludge Process/Extended Aeration/Sequential Batch Reactor (SBR)/Moving Bed Bio Reactor (MBBR)."
Learned counsel for the petitioner, however, could not refer to any material on record and was unable to demonstrate as to which condition of the technical eligibility was not fulfilled by respondent No.3. Thus, this issue is adjudicated against the petitioner.
15. Adverting to the plea of waiver of blacklisting, on examining the order of blacklisting,it is discerned that originally the petitioner was blacklisted for one year vide Annexure P.5 which period was reduced to three months vide Annexure P.6. It was not disputed that the petitioner had been debarred for three months and in such a situation, the petitioner was not technically qualified to submit the tender in view of Clause 3.1.7 of the bid document, Annexure P.1. The penalty of blacklisting was never waived completely which would have entitled the petitioner to draw any help. The contention, thus, is meritless.
16. Adverting to the fourth point, the scope of judicial review in the matter of allotment of tenders would require to be examined. It was considered in detail by a three Judge Bench of the Hon'ble Apex Court in Tata Cellular v. Union of India, (1994) 6 SCC 651, wherein CWP No.3502 of 2012 14 it was observed as under:-
"94. The principles deducible from the above are : (1) The modem trend points to judicial restraint in administrative action.
(2) The court does not sit as a court of appeal but merely reviews the manner in which the decision was made.
(3) The court does not have the expertise to correct the administrative decision. If a review of the administrative decision is permitted it will be substituting its own decision, without the necessary expertise which itself may be fallible.
(4) The terms of the invitation to tender cannot be open to judicial scrutiny because the invitation to tender is in the realm of contract. Normally speaking, the decision to accept the tender or award the contract is reached by process of negotiations through several tiers. More often than not, such decisions are made qualitatively by experts.
(5) The Government must have freedom of contract. In other words, a fair play in the joints is a necessary concomitant for an administrative body functioning in an administrative sphere or quasi- administrative sphere. However, the decision must not only be tested by the application of Wednesbury principle of reasonableness (including its other facts pointed out above) but must be free from arbitrariness not affected by bias or actuated by mala fides.
(6) Quashing decisions may impose heavy administrative burden on the administration and lead to increased and unbudgeted expenditure."
17. In Air India Limited v. Cochin International Airport Limited, (2000) 2 SCC 617, law relating to award of contract by State CWP No.3502 of 2012 15 and Public Sector Corporation was discussed. It was held:-
"The award of a contract, whether it is by a private party or by a public body or the State is essentially a commercial transaction. In arriving at a commercial decision considerations which are paramount are commercial considerations. The State can choose its own method to arrive at a decision. It can fix its own terms of invitation to tender and that is not open to judicial scrutiny. It can enter into negotiations before finally deciding to accept one of the offers made to it. Price need not always be the sole criterion for awarding a contract. It is free to grant any relaxation, for bona fide reasons, if the tender conditions permit such a relaxation. It may not accept the offer even though it happens to be the highest or the lowest. But the State,its corporations, instrumentalities and agencies are bound to adhere to the norms, standards and procedure laid down by them and cannot depart from them arbitrarily. Though that decision is not amenable to judicial review, the Court can examine the decision-making process and interfere if it is found vitiated by malafides, unreasonableness and arbitrariness."
18. Hon'ble Supreme Court summarizing the scope of judicial review and the interference of superior courts in the awards of contracts in M/s B.S.N. Joshi and Sons Limited v. Nair Coal Services Limited, AIR 2007 SC 437, noticed as under:-
"67. We are not oblivious of the expansive role of the superior courts on judicial review.
68. We are also not shutting our eyes towards the new principles of judicial review which are being developed; but the law as it stands now having regard CWP No.3502 of 2012 16 to the principles laid down in the aforementioned decisions may be summarized as under :
i) If there are essential conditions, the same must be adhered to;
ii) If there is no power of general relaxation, ordinarily the same shall not be exercised and the principle of strict compliance would be applied where it is possible for all the parties to comply with all such conditions fully;
iii) If, however, a deviation is made in relation to all the parties in regard to any of such conditions, ordinarily again a power of relaxation may be held to be existing
iv) The parties who have taken the benefit of such relaxation should not ordinarily be allowed to take a different stand in relation to compliance of another part of tender contract, particularly when he was also not in a position to comply with all the conditions of tender fully, unless the court otherwise finds relaxation of a condition which being essential in nature could not be relaxed and thus the same was wholly illegal and without jurisdiction.
v) When a decision is taken by the appropriate authority upon due consideration of the tender document submitted by all the tenderers on their own merits and if it is ultimately found that successful bidders had in fact substantially complied with the purport and object for which essential conditions were laid down, the same may not ordinarily be interfered with.
(vi) The contractors cannot form a cartel. If despite the same, their bids are considered and they are given an offer to match with the rates quoted by the lowest CWP No.3502 of 2012 17 tenderer, public interest would be given priority.
(vii) Where a decision has been taken purely on public interest, the Court ordinarily should exercise judicial restraint."
19. Recently, the Hon'ble Supreme Court in Siemens Public Communication Networks Pvt. Limited and another v. Union of India and others, AIR 2009 SC 1204, after analysing the judicial precedents in para 39 had concluded as under:-
"39. On examining the facts and circumstances of the present case, we are of the view that none of the criteria has been satisfied justifying Court's interference in the grant of contract in favour of the appellants. When the power of judicial review is invoked in the matters relating to tenders or award of contracts, certain special features have to be considered. A contract is a commercial transaction and evaluating tenders and awarding contracts are essentially commercial functions. In such cases principles of equity and natural justice stay at a distance. If the decision relating to award of contracts is bona fide and is in public interest, Courts will not exercise the power of judicial review and interfere even if it is accepted for the sake of argument that there is a procedural lacuna."
20. For the Courts to examine validity of allotment of tenders, it is essential for the person approaching the Court with a grievance to establish that the decision making process is faulty and it is vitiated by malafides, unreasonableness or arbitrariness. The award of contract in the case of a private party or by a public body or the State is essentially a commercial transaction for which commercial CWP No.3502 of 2012 18 considerations shall have precedence. It is open to the State to evolve its own methodology for arriving at a decision. The courts shall exercise judicial restraint in such administrative action as they do not sit as a Court of appeal to substitute its own views.
21. Examining the factual matrix involved herein, in our opinion, none of the grounds for Court's intervention in the grant of contract in favour of respondent No.3 has been satisfied. The respondents No.1 and 2 had evaluated the tenders and found respondent No.3 to be competitive and more suitable to perform the contract successfully. No malafides, arbitrariness, unreasonableness or variation in any procedure had been pointed out so as to nullify the award of the contract to respondent No.3.
22. Lastly, the respondents have raised a plea relating to the conduct of the petitioner in misleading and fabricating by way of cyber crime whereby petitioner had manipulated the entry dated 3.2.2012. The petitioner had shown that its technical bid was opened on 3.2.2012 whereas the sequence of events unambiguously show that no such event had taken place. The glaring factor which requires notice is that the petitioner had appended document Annexure P.9 which was forged. The respondents had categorically filed additional affidavit and also denied opening of financial bid of the petitioner to which no rejoinder had been filed by the petitioner controverting the same. However, the petitioner had itself accepted that the financial bid had not been opened till 20.2.2012 in letters Annexures R.1, R.2 and R.3. Further fact which requires notice is that the unamended CWP No.3502 of 2012 19 writ petition which was filed did not stipulate that price bid had been opened. The same was an after-thought, particularly in view of the averments made in the additional affidavit which has been filed by respondent Nos. 1 and 2. Paras 3 to 7 of the written statement on behalf of respondent Nos. 1 and 2 read as under:-
"3. That the petitioner has tried to overreach the Hon'ble High Court by alleging that he has come to know that his commercial bid was opened. It is respectfully submitted that the financial bid of the petitioner was never opened. Therefore, petitioner has not approached the Hon'ble High Court with clean hands and in view of the law laid down by the Hon'ble Court, a person who does not come to the court with clean hands is not entitled to be heard on merits of his claim. Petitioner has written a letter dated UEM/MKT/MCP/640 dated 3.2.2012 stated that they have come to know from the website that UEM's bid has been disqualified by HUDA and on further perusal, they have come to know that the bid has been disqualified on the ground of debarment of the company for a period of three months (30.5.2011 to 11.8.2011). A copy of the letter dated 3.2.2012 is attached as Annexure R.1 to this amended written statement.
4. That another letter has been written by the petitioner that the financial bid has been opened on 3.2.2012. As per the information available on the website the message shown is 'Financial/Price bid cancelled or Rejected Bid'. A copy of the letter dated 10.2.2012 is attached as Annexure R.2 to this amended written statement.
5. That yet another letter has been written by the CWP No.3502 of 2012 20 petitioner vide No.UEM/MKT/MCP/671A dated 20.2.2012 to the Chief Administrator, Haryana Urban Development Authority, Panchkula that despite repeated follow-ups including meetings in person with the concerned official, the bid of the petitioner has not been opened. He has further mentioned that it is most shocking that none of the representations have been responded. Petitioner has further mentioned that as per the information available on the website, their financial bid was not being considered and hence was not opened. A copy of the letter dated 20.2.2012 is attached as Annexure R.3 to this written statement.
6. That now the petitioner seems to have created a forged web site/portal of HUDA to show that his commercial bid was opened. He has attached undated Annexure P.9 with the writ petition. Unfortunately, the copy of the said letter has not been supplied to the counsel for the answering-respondents or to the answering respondents when the amended writ petition has been filed. Enquiry by the counsel for HUDA from the counsel for respondent No.3 also showed that he has also not been supplied the copy of Annexure P.9. Infact petitioner has committed the cyber crime by creating/forging a website/portal of HUDA. In any case, the answering respondent reserves the right to file an additional reply, if need be, after receipt of Annexure P.9. Thus, the writ petition of the petitioner is liable to be dismissed with exemplary costs."
23. The trite law is that petitioner is required to approach the Court with clean hands. The law has been succinctly summarized in that regard in the under noted terms.
24. This Court in Pawan Kumar v. State of Haryana and CWP No.3502 of 2012 21 another, 1994(5) SLR 73 had an occasion to consider the situation wherein petitioner had attempted to mislead the Court. The petitioner was held not entitled to any relief under Article 226 of the Constitution of India.
25. The Hon'ble Apex Court in the case of S.P.Chengalvaraya Naidu v. Jagannath, AIR 1994 SC 853 had observed as under:-
"The courts of law are meant for imparting justice between the parties. One who comes to the court, must come with clean hands. We are constrained to say that more often than not, process of the court is being abused. Property-grabbers,tax-evaders,bank-loan-dodgers and other unscrupulous persons from all walks of life find the court-process a convenient lever to retain the illegal- gains indefinitely. We have no hesitation to say that a person, who's case is based on falsehood, has no right to approach the court. He can be summarily thrown out at any stage of the litigation.
8. The facts of the present case leave no manner of doubt that Jagannath obtained the preliminary decree by playing fraud on the court. A fraud is an act of deliberate deception with the design of securing something by taking unfair advantage of another. It is a deception in order to gain by another's loss. It is a cheating intended to get an advantage. Jagannath was working as a clerk with Chunilal Sowcar. He purchased the property in the court auction on behalf of Chunilal Sowcar. He had, on his own volition,executed the registered release deed (Ex. B-15) in favour of Chunilal Sowcar regarding the property in dispute. He knew that the appellants had paid the total decretal amount to his CWP No.3502 of 2012 22 master Chunilal Sowcar. Without disclosing all these facts, he filed the suit for the partition of the property on the ground that he had purchased the property on his own behalf and not on behalf of Chunilal Sowcar. Non- production and even non-mentioning of the release deed at the trial is tantamount to playing fraud on the court. We do not agree with the observations of the High Court that the appellants-defendants could have easily produced the certified registered copy of Ex. B-15 and non-suited the plaintiff.A litigant, who approaches the court, is bound to produce all the documents executed by him which are relevant to the litigation. If he withholds a vital document in order to gain advantage on the other side then he would be guilty of playing fraud on the court as well as on the opposite party.
9. We, therefore, allow the appeal, set aside the impugned judgment of the High Court and restore that of the trial court. The appellants shall be entitled to their costs which we quantify as Rs 11,000."
26. Similarly, the Hon'ble Apex Court in Chandra Shashi v. Anil Kumar Verma, (1995) 1 SCC 421 noted as under:-
"The stream of administration of justice has to remain unpolluted so that purity of Court's atmosphere may give vitality to all the organs of the state. Polluters of judicial firmament are, therefore, required to be well taken care of to maintain the sublimity of Court's environment; so as to enable it to administer justice fairly and to the satisfaction of all concerned.
2. Anyone who takes recourse to fraud, deflects the course of judicial proceedings; or if anything is done with oblique motive, the same interferes with the administration of justice. Such persons are required CWP No.3502 of 2012 23 to be properly dealt with, not only to punish them for the wrong done, but also to deter others from indulging in similar acts which shake the faith of people in the system of administration of justice."
27. In view of above, we do not find any merit in this writ petition and the same is dismissed with costs quantified at ` 50,000/-. Respondents No.1 and 2 and respondent No.3 shall be entitled to costs equally i.e., ` 25,000/- each.
(Ajay Kumar Mittal) Judge July 24, 2012 (Gurmeet Singh Sandhawalia) 'gs' Judge


Check this option to print the path of the build output without uploading anything
You can use this option to simulate the plugin features without sending anything to Data Theorem


akka.http.javadsl
Entity streaming support trait allowing rendering and receiving incoming Source[T, _] from HTTP entities.
Source[T, _]
See JsonEntityStreamingSupport or CsvEntityStreamingSupport for default implementations.
Entity streaming support, independent of used Json parsing library etc.
Entity streaming support trait allowing rendering and receiving incoming
from HTTP entities.Source[T, _]
See JsonEntityStreamingSupport or CsvEntityStreamingSupport for default implementations.


| git | an open source, distributed version-control system |
| GitHub | a platform for hosting and collaborating on Git repositories |
| commit | As a noun: A single point in the Git history; the entire history of a project is represented as a set of interrelated commits. The word "commit" is often used by Git in the same places other revision control systems use the words "revision" or "version". Also used as a short hand for commit object.
As a verb: The action of storing a new snapshot of the project’s state in the Git history, by creating a new commit representing the current state of the and advancing to point at the new commit. |
| branch | A "branch" is an active line of development. The most recent commit on a branch is referred to as the tip of that branch. The tip of the branch is referenced by a branch , which moves forward as additional development is done on the branch. A single Git can track an arbitrary number of branches, but your is associated with just one of them (the "current" or "checked out" branch), and points to that branch. |
| clone | a local version of a , including all and |
| origin | The default upstream . Most projects have at least one project which they track. By default origin is used for that purpose. New upstream updates will be fetched into named origin/name-of-upstream-branch, which you can see using git branch -r. |
| fast-fowrard merge | A fast-forward is a special type of where you have a and you are "merging" another branch's changes that happen to be a descendant of what you have. In such a case, you do not make a new but instead just update to his revision. This will happen frequently on a of a remote . |
| pull request | a place to compare and discuss the differences introduced on a with reviews, comments, integrated tests, and more |
| push | Pushing a means to get the branch’s from a remote , find out if it is an ancestor to the branch’s local head ref, and in that case, putting all objects, which are from the local head ref, and which are missing from the remote repository, into the remote , and updating the remote head ref. If the remote is not an ancestor to the local head, the push fails. |
| HEAD | The current . In more detail: Your is normally derived from the state of the tree referred to by HEAD. HEAD is a reference to one of the in your repository, except when using a , in which case it directly references an arbitrary commit. |
| porcelain | Cute name for programs and program suites depending on , presenting a high level access to core Git. Porcelains expose more of a interface than the . |
| plumbing command | Cute name for |
| ahead | a (local or remote) has more recent that it's associated (local or remote) |
| behind | opposite of ahead |


For testing only Disclaimer: This is NOT a real business. It is only provided for demonstration purposes. No medicine is actually sold.


Otoroshi
Otoroshi is a modern http reverse proxy with a thin layer of api management
coming soon ...


|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
| Class Summary | |
|---|---|
| MediaControlIntent | Constants for media control intents. |
| MediaItemMetadata | Constants for specifying metadata about a media item as a Bundle . |
| MediaItemStatus | Describes the playback status of a media item. |
| MediaItemStatus.Builder | Builder for media item status objects . |
| MediaRouteDescriptor | Describes the properties of a route. |
| MediaRouteDescriptor.Builder | Builder for media route descriptors . |
| MediaRouteDiscoveryRequest | Describes the kinds of routes that the media router would like to discover and whether to perform active scanning. |
| MediaRouteProvider | Media route providers are used to publish additional media routes for use within an application. |
| MediaRouteProvider.Callback | Callback which is invoked when route information becomes available or changes. |
| MediaRouteProvider.ProviderMetadata | Describes properties of the route provider's implementation. |
| MediaRouteProvider.RouteController | Provides control over a particular route. |
| MediaRouteProviderDescriptor | Describes the state of a media route provider and the routes that it publishes. |
| MediaRouteProviderDescriptor.Builder | Builder for media route provider descriptors . |
| MediaRouteProviderService | Base class for media route provider services. |
| MediaRouter | MediaRouter allows applications to control the routing of media channels and streams from the current device to external speakers and destination devices. |
| MediaRouter.Callback | Interface for receiving events about media routing changes. |
| MediaRouter.ControlRequestCallback | Callback which is invoked with the result of a media control request. |
| MediaRouter.ProviderInfo | Provides information about a media route provider. |
| MediaRouter.RouteInfo | Provides information about a media route. |
| MediaRouteSelector | Describes the capabilities of routes that applications would like to discover and use. |
| MediaRouteSelector.Builder | Builder for media route selectors . |
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |


Cheatsheets
Cheatsheets are two-page PDFs loaded with short Hail Query examples and even shorter explanations. They push you over all the little roadblocks.
Query Docs
When you need to find detailed information on how to get started with Hail Query, examples of Hail Query use, and how a function works: the reference document is your go to. To do a quick search of a Hail Query function, try out the search bar in the documentation.
Batch Docs
For all your massively scalable compute needs, check out the Hail Batch reference documentation.
Ask a question
When you reach a blocking issue with your analysis using Hail, and you think you are unable to find an answer to your question via the documentation, search through or ask a question on our Forum! It is highly recommended -- your question may be able to serve another person in our ever growing Hail community.


1 Chronicles 13:3
And let us bring again the ark of our God to us: for we inquired not at it in the days of Saul.


2 cars stolen from Watertown street, police say
by Stephen CohnWATERTOWN, Wis. - Police are investigating two stolen car complaints in Watertown on Wednesday morning.
According to a news release, both cars were reported stolen from the 500 block of Grey Fox Run.
Officials said one car was found south of Watertown, while the other was involved in a police chase and last seen in Dane County.

Anyone with information on the robberies is asking to call Watertown police at 920-261-660 or report it anonymously by texting "WTTN" and their tip to 847411.


07. Data Warnings and Bitcoin.config Setup
At this point, we've talked a lot about the Bitcoin Core Software. Coming up, we'll be installing this software locally on our computers.
This is a pretty intensive software to have installed locally. There’s a few things to know before getting started.
Requirements and Warnings
To start, have a look at the the requirements and warnings about this software that are available on the bitcoin core website.
Alternatives
We understand that this may not be a viable option for many people. Below we have provided alternatives that can help you get started even if you are unable to install Bitcoin Core.
Workspaces
We have a Bitcoin Core Full node installed in the classroom that you can access using a command line interface.
You can type commands directly into this console, and you’ll get the same values as if you had run it locally.
Anytime you see something that looks like the image below in the classroom, that's a workspace!
It's an interactive terminal environment you can use to run commands in. We’ll be going into these commands in the next lesson when we review the Bitcoin Core Debug Console.
Switching Networks
While the workspaces can help with running commands, they don’t give you access to the user interface of the wallet provided by Bitcoin Core.
To get access to these you’ll need to get onto a network somehow.
One way to make this more manageable is to run the software with certain modifications.
One change is to set the default network to be the testnet or regnet.
If you do this, rather than the software syncing to the mainnet, which can be up to 200GB or more, you’ll sync to the testnet which is approximately 15GB, or the regnet which is 0GB.
If you choose this option, download the software as shown in the next section, then jump directly to Bitcoin Core Networks Demonstration to see how to switch to a different network.
Pruning
You can also use pruning to reduce the amount of space taken by the bitcoin blockchain. This does not make the blockchain sync faster, but reduces the amount of storage held on your local computer.
You will do this using what’s known as a bitcoin.conf file in your bitcoin core directory.
If you are using this method, jump to Bitcoin Core Networks Demonstration to see how this file is set up.
As a quick summary here are the steps you’ll go through.
- Step 1: create a bitcoin.conf file in your bitcoin installation directory.
- Step 2: In this file, write prune=550.
For more information on reducing storage you can read more here: Full Node: Reduce Storage
Final Note
We understand this is a significant hurdle to becoming a Blockchain Developer.
We’ve chosen to follow through with Bitcoin as our starting point because it is an excellent way to get started with the core concepts that persist throughout all Blockchain technologies you will come across.
Bitcoin was not only the first blockchain, it was the starting point from which the components, terminology, concepts for all other blockchains derived.
We hope that you see the value in starting with this software, and will continue to do everything we can do make sure you can comfortably get started no matter what restrictions you may have to your local environment.
Thank you, please reach out if you have any questions or concerns about this.


CDM: Cognitive Diagnosis Modeling
Functions for cognitive diagnosis modeling and multidimensional item response modeling
for dichotomous and polytomous item responses. This package enables the estimation of
the DINA and DINO model (Junker & Sijtsma, 2001, <doi:10.1177/01466210122032064>),
the multiple group (polytomous) GDINA model (de la Torre, 2011,
<doi:10.1007/s11336-011-9207-7>), the multiple choice DINA model (de la Torre, 2009,
<doi:10.1177/0146621608320523>), the general diagnostic model (GDM; von Davier, 2008,
<doi:10.1348/000711007X193957>), the structured latent class model (SLCA; Formann, 1992,
<doi:10.1080/01621459.1992.10475229>) and regularized latent class analysis
(Chen, Li, Liu, & Ying, 2017, <doi:10.1007/s11336-016-9545-6>).
See George, Robitzsch, Kiefer, Gross, and Uenlue (2017) <doi:10.18637/jss.v074.i02>
for further details on estimation and the package structure.
For tutorials on how to use the CDM package see
George and Robitzsch (2015) as well as
Ravand and Robitzsch (2015).
| Version: |
7.1-20 |
| Depends: |
R (≥ 3.1), mvtnorm |
| Imports: |
graphics, grDevices, MASS, methods, polycor, Rcpp, sfsmisc, stats, utils |
| LinkingTo: |
Rcpp, RcppArmadillo |
| Suggests: |
BIFIEsurvey, GDINA, lattice, miceadds, mirt, sirt, TAM |
| Published: |
2018-12-13 |
| Author: |
Alexander Robitzsch [aut, cre], Thomas Kiefer [aut],
Ann Cathrice George [aut], Ali Uenlue [aut] |
| Maintainer: |
Alexander Robitzsch <robitzsch at ipn.uni-kiel.de> |
| BugReports: |
https://github.com/alexanderrobitzsch/CDM/issues?state=open |
| License: |
GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
| URL: |
https://github.com/alexanderrobitzsch/CDM,
https://sites.google.com/site/alexanderrobitzsch2/software |
| NeedsCompilation: |
yes |
| Citation: |
CDM citation info |
| Materials: |
README NEWS |
| In views: |
Psychometrics |
| CRAN checks: |
CDM results |
Downloads:
Reverse dependencies:
Linking:
Please use the canonical form
https://CRAN.R-project.org/package=CDM
to link to this page.


Code Documentation¶
Frisbee Interface¶
-
class
frisbee.
Frisbee
(project: str = 'pensive_perlman', log_level: int = 20, save: bool = False)[source]¶ Class to interact with the core code.
-
_config_bootstrap
() → None[source]¶ Handle the basic setup of the tool prior to user control.
Bootstrap will load all the available modules for searching and set them up for use by this main class.
-
Module Interface¶
-
class
frisbee.modules.base.
Base
(log_level=10)[source]¶ Base module class to assist in writing new modules.
-
_extract
() → None[source]¶ Extract email addresses from results.
Text content from all crawled pages are ran through a simple email extractor. Data is cleaned prior to running pattern expressions.
-
_fetch
(urls: List[str]) → None[source]¶ Perform bulk collection of data and return the content.
Gathering responses is handled by the base class and uses futures to speed up the processing. Response data is saved inside a local variable to be used later in extraction.
-
_format
() → None[source]¶ Format search queries to perform in bulk.
Build up the URLs to call for the search engine. These will be ran through a bulk processor and returned to a detailer.
-


Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
Lorem Ipsum is simply dummy text of the printing and typesetting industry.
Lorem Ipsum
Lorem Ipsum
Lorem Ipsum
Lorem Ipsum
Lorem Ipsum
Lorem Ipsum
Lorem Ipsum
Lorem Ipsum
Lorem Ipsum
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry.Lorem Ipsum is simply dummy text of the printing and typesetting industry.


Class: Aws::GameLift::Types::VpcPeeringConnection
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Struct
|
|
|
Instance Chain:
self,
::Aws::Structure ,
Struct
|
|
| Inherits: |
Struct
|
| Defined in: | gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb |
Overview
Represents a peering connection between a VPC on one of your Amazon Web Services accounts and the VPC for your Amazon GameLift fleets. This record may be for an active peering connection or a pending connection that has not yet been established.
Related actions
Constant Summary
Instance Attribute Summary
-
#fleet_arn ⇒ String
rw
The Amazon
::Aws::GameLift::Resource
Name ([ARN][1]) associated with the::Aws::GameLift
fleet resource for this connection. -
#fleet_id ⇒ String
rw
A unique identifier for the fleet.
-
#game_lift_vpc_id ⇒ String
rw
A unique identifier for the VPC that contains the Amazon GameLift fleet for this connection.
-
#ip_v4_cidr_block ⇒ String
rw
CIDR block of IPv4 addresses assigned to the VPC peering connection for the
::Aws::GameLift
VPC. -
#peer_vpc_id ⇒ String
rw
A unique identifier for a VPC with resources to be accessed by your Amazon GameLift fleet.
-
#status ⇒ Types::VpcPeeringConnectionStatus
rw
The status information about the connection.
-
#vpc_peering_connection_id ⇒ String
rw
A unique identifier that is automatically assigned to the connection record.
Instance Method Summary
Instance Attribute Details
#fleet_arn ⇒ String
(rw)
The Amazon ::Aws::GameLift::Resource
Name (ARN) associated with the ::Aws::GameLift
fleet resource for this connection.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 9660
class VpcPeeringConnection < Struct.new( :fleet_id, :fleet_arn, :ip_v4_cidr_block, :vpc_peering_connection_id, :status, :peer_vpc_id, :game_lift_vpc_id) SENSITIVE = [] include Aws::Structure end
#fleet_id ⇒ String
(rw)
A unique identifier for the fleet. This ID determines the ID of the Amazon GameLift VPC for your fleet.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 9660
class VpcPeeringConnection < Struct.new( :fleet_id, :fleet_arn, :ip_v4_cidr_block, :vpc_peering_connection_id, :status, :peer_vpc_id, :game_lift_vpc_id) SENSITIVE = [] include Aws::Structure end
#game_lift_vpc_id ⇒ String
(rw)
A unique identifier for the VPC that contains the Amazon GameLift fleet for this connection. This VPC is managed by Amazon GameLift and does not appear in your Amazon Web Services account.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 9660
class VpcPeeringConnection < Struct.new( :fleet_id, :fleet_arn, :ip_v4_cidr_block, :vpc_peering_connection_id, :status, :peer_vpc_id, :game_lift_vpc_id) SENSITIVE = [] include Aws::Structure end
#ip_v4_cidr_block ⇒ String
(rw)
CIDR block of IPv4 addresses assigned to the VPC peering connection
for the ::Aws::GameLift
VPC. The peered VPC also has an IPv4 CIDR block
associated with it; these blocks cannot overlap or the peering
connection cannot be created.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 9660
class VpcPeeringConnection < Struct.new( :fleet_id, :fleet_arn, :ip_v4_cidr_block, :vpc_peering_connection_id, :status, :peer_vpc_id, :game_lift_vpc_id) SENSITIVE = [] include Aws::Structure end
#peer_vpc_id ⇒ String
(rw)
A unique identifier for a VPC with resources to be accessed by your Amazon GameLift fleet. The VPC must be in the same Region as your fleet. To look up a VPC ID, use the VPC Dashboard in the Amazon Web Services Management Console. Learn more about VPC peering in VPC Peering with Amazon GameLift Fleets.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 9660
class VpcPeeringConnection < Struct.new( :fleet_id, :fleet_arn, :ip_v4_cidr_block, :vpc_peering_connection_id, :status, :peer_vpc_id, :game_lift_vpc_id) SENSITIVE = [] include Aws::Structure end
#status ⇒ Types::VpcPeeringConnectionStatus (rw)
The status information about the connection. Status indicates if a connection is pending, successful, or failed.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 9660
class VpcPeeringConnection < Struct.new( :fleet_id, :fleet_arn, :ip_v4_cidr_block, :vpc_peering_connection_id, :status, :peer_vpc_id, :game_lift_vpc_id) SENSITIVE = [] include Aws::Structure end
#vpc_peering_connection_id ⇒ String
(rw)
A unique identifier that is automatically assigned to the connection record. This ID is referenced in VPC peering connection events, and is used when deleting a connection.
# File 'gems/aws-sdk-gamelift/lib/aws-sdk-gamelift/types.rb', line 9660
class VpcPeeringConnection < Struct.new( :fleet_id, :fleet_arn, :ip_v4_cidr_block, :vpc_peering_connection_id, :status, :peer_vpc_id, :game_lift_vpc_id) SENSITIVE = [] include Aws::Structure end


Birthday Parties
Our Gallery
About Us
Contact
For Ordering and Getting the Detailed Information please contact us:
phone:<PHONE_NUMBER>
Email<EMAIL_ADDRESS>LEAVE YOUR REQUEST:
Your name:
Your email:
Your phone:
Your message:
Submit


Cornish Marathon
Liskeard ENG
Website: www.eastcornwallharriers.com/pages/marathon.php
Race Winners
(34 runnings)
18 Nov
2007
19 Nov
2006
20 Nov
2005
21 Nov
2004
16 Nov
2003
17 Nov
2002
18 Nov
2001
19 Nov
2000
21 Nov
1999
1998
23 Nov
1997
24 Nov
1996
1995
27 Nov
1994
28 Nov
1993
1992
1991
18 Nov
1990
19 Nov
1989
20 Nov
1988
15 Nov
1987
Notes: 1984 was the inaugural year. The 1984 course was about a mile
short.
19 Nov
2017
2:52:49
Oliver Jones (ENG)
3:12:45
Isobel Wykes-2
20 Nov
2016
2:47:21
Daniel Costello (ENG)
3:01:15
Zelah Morrall-2
15 Nov
2015
2:43:51
Paul Whear-2
3:03:18
Zelah Morrall
(46,ENG)
16 Nov
2014
2:45:37
Paul Whear (ENG)
3:20:36
Isobel Wykes (ENG)
17 Nov
2013
2:45:20
Kitson Benbow
(ENG)
3:19:14
Rebecca Mingo
(ENG)
18 Nov
2012
2:40:13
Justin Thomas
(ENG)
2:56:24
Naomi Tier
(29,ENG)
20 Nov
2011
2:44:15
Noel Kindon (ENG)
3:09:33
Suzy Bosustow (ENG)
21 Nov
2010
2:42:35
Daniel Alsop (ENG)
3:20:07
Diane Roy-2
15 Nov
2009
2:45:44
Steve Osborne (ENG)
3:26:37
Diane Roy (ENG)
16 Nov
2008
2:45:22
Shaun Milford-3
3:15:22
Philippa Stephens-3
2:53:18
Jeremy Bragg (ENG)
3:15:09
Philippa Stephens-2
2:49:27
Laslo Boden (ENG)
3:10:15
Philippa Stephens (ENG)
2:47:55
Shaun Milford-2
3:01:07
Heather Foundling-Hawker (ENG)
2:53:50
Bob Brown (ENG)
3:12:03
Vicky Skelton (ENG)
2:58:41
Dave Stone-2
3:26:18
Lisa Baumann (RSA)
2:44:50
Dave Stone (ENG)
3:06:35
Maddie Horton (ENG)
2:36:40
Michael Feighan (ENG)
3:18:02
Revis Crowle (ENG)
2:55:10
Neil Holmes-2
3:38:58
Jenny Mills (ENG)
2:47:24
Neil Holmes (ENG)
3:03:51
Jess Hoskin-2
2:35:00
Ronnie James (ENG)
3:10:42
Jess Hoskin (ENG)
2:53:08
J Mackay (ENG)
3:22:19
Debbie Dunleavy-2
2:37:14
Shaun Milford (ENG)
3:25:19
Mary Picksley (ENG)
2:41:43
Paul Howarth (WAL)
3:11:53
Lynda Lee (ENG)
2:53:48
M Pearson (ENG)
3:45:04
K Smith (ENG)
2:41:50
Nicholas Grenney-4
3:24:38
Debbie Dunleavy (ENG)
---
n/a
---
n/a
---
n/a
---
n/a
2:37:07
Nicholas Grenney-3
3:41:38
S Carmichael (ENG)
2:35:31
Nicholas Grenney-2
-3:30:09
Susan Eason (ENG)
2:32:39
Nicholas Grenney (ENG)
3:58:16
L Reeves (ENG)
---
n/a
---
n/a
16 Nov 1986
2:42:33
Bob Manison-2
3:27:13
Jill Libby (ENG)
1985
2:40:14
Richard Koehler (GER)
3:23:12
Maria Smart (ENG)
09 Dec 1984
2:29:15
Bob Manison (ENG)
---
Heidi Golant (ENG)
Most Wins
(1984/date)
Men
4
Nicholas Grenney (ENG)
1988-90,1993
Women
3
Philippa Stephens (ENG)
2006-08
Prize Money
(ADR qualified runners)
No information on prize money has been received for this race.
Race Time Bias
(sec/km)
Insufficient data to calculate the race time bias.
Competitive Level
(1990-date)
Insufficient data to calculate the competitive level.
Quality Performances
Men No men under 2:20. Women No women under 2:50.
Last Updated on 02 Dec 2017
Contributor: Klaas Loonstra (40), Mick McGeoch (34)


Make a To Do List
To Do List:
Enter task
Enter name
When?
Where?
Enter
Tasks:
Task:
name:
When:
Where:


Actions, resources, and condition keys for AWS DeepRacer
AWS DeepRacer (service prefix:
deepracer
) provides the following service-specific resources, actions, and condition context keys for use in IAM permission policies.
References:
-
Learn how to configure this service .
-
View a list of the API operations available for this service .
-
Learn how to secure this service and its resources by using IAM permission policies.
Topics
Actions defined by AWS DeepRacer
You can specify the following actions in the
Action
element of an IAM policy statement. Use policies to grant permissions to perform an operation in AWS. When you use an action in a policy, you usually allow or deny access to the API operation or CLI command with the same name. However, in some cases, a single action controls access to more than one operation. Alternatively, some operations require several different actions.
The
Resource types
column of the Actions table indicates whether each action supports resource-level permissions. If there is no value for this column, you must specify all resources ("*") to which the policy applies in the
Resource
element of your policy statement. If the column includes a resource type, then you can specify an ARN of that type in a statement with that action. If the action has one or more required resources, the caller must have permission to use the action with those resources. Required resources are indicated in the table with an asterisk (*). If you limit resource access with the
Resource
element in an IAM policy, you must include an ARN or pattern for each required resource type. Some actions support multiple resource types. If the resource type is optional (not indicated as required), then you can choose to use one of the optional resource types.
The
Condition keys
column of the Actions table includes keys that you can specify in a policy statement's
Condition
element. For more information on the condition keys that are associated with resources for the service, see the
Condition keys
column of the Resource types table.
For details about the columns in the following table, see Actions table .
| Actions | Description | Access level | Resource types (*required) | Condition keys | Dependent actions |
|---|---|---|---|---|---|
| AddLeaderboardAccessPermission [permission only] | Grants permission to add access for a private leaderboard | Write | |||
| AdminGetAccountConfig [permission only] | Grants permission to get current admin multiuser configuration for this account | Read | |||
| AdminListAssociatedResources [permission only] | Grants permission to list all deepracer users with their associated resources created under this account | Read | |||
| AdminListAssociatedUsers [permission only] | Grants permission to list user data for all users associated with this account | Read | |||
| AdminManageUser [permission only] | Grants permission to manage a user associated with this account | Write | |||
| AdminSetAccountConfig [permission only] | Grants permission to set configuration options for this account | Write | |||
| CloneReinforcementLearningModel [permission only] | Grants permission to clone an existing DeepRacer model | Write | |||
| CreateCar [permission only] | Grants permission to create a DeepRacer car in your garage | Write | |||
| CreateLeaderboard [permission only] | Grants permission to create a leaderboard | Write | |||
| CreateLeaderboardAccessToken [permission only] | Grants permission to create an access token for a private leaderboard | Write | |||
| CreateLeaderboardSubmission [permission only] | Grants permission to submit a DeepRacer model to be evaluated for leaderboards | Write | |||
| CreateReinforcementLearningModel [permission only] | Grants permission to create ra einforcement learning model for DeepRacer | Write | |||
| DeleteLeaderboard [permission only] | Grants permission to delete a leaderboard | Write | |||
| DeleteModel [permission only] | Grants permission to delete a DeepRacer model | Write | |||
| EditLeaderboard [permission only] | Grants permission to edit a leaderboard | Write | |||
| GetAccountConfig [permission only] | Grants permission to get current multiuser configuration for this account | Read | |||
| GetAlias [permission only] | Grants permission to retrieve the user's alias for submitting a DeepRacer model to leaderboards | Read | |||
| GetAssetUrl [permission only] | Grants permission to download artifacts for an existing DeepRacer model | Read | |||
| GetCar [permission only] | Grants permission to retrieve a specific DeepRacer car from your garage | Read | |||
| GetCars [permission only] | Grants permission to view all the DeepRacer cars in your garage | Read | |||
| GetEvaluation [permission only] | Grants permission to retrieve information about an existing DeepRacer model's evaluation jobs | Read | |||
| GetLatestUserSubmission [permission only] | Grants permission to retrieve information about how the latest submitted DeepRacer model for a user performed on a leaderboard | Read | |||
| GetLeaderboard [permission only] | Grants permission to retrieve information about leaderboards | Read | |||
| GetModel [permission only] | Grants permission to retrieve information about an existing DeepRacer model | Read | |||
| GetPrivateLeaderboard [permission only] | Grants permission to retrieve information about private leaderboards | Read | |||
| GetRankedUserSubmission [permission only] | Grants permission to retrieve information about the performance of a user's DeepRacer model that got placed on a leaderboard | Read | |||
| GetTrack [permission only] | Grants permission to retrieve information about DeepRacer tracks | Read | |||
| GetTrainingJob [permission only] | Grants permission to retrieve information about an existing DeepRacer model's training job | Read | |||
| ImportModel [permission only] | Grants permission to import a reinforcement learning model for DeepRacer | Write | |||
| ListEvaluations [permission only] | Grants permission to list a DeepRacer model's evaluation jobs | Read | |||
| ListLeaderboardSubmissions [permission only] | Grants permission to list all the DeepRacer model submissions of a user on a leaderboard | Read | |||
| ListLeaderboards [permission only] | Grants permission to list all the available leaderboards | Read | |||
| ListModels [permission only] | Grants permission to list all existing DeepRacer models | Read | |||
| ListPrivateLeaderboardParticipants [permission only] | Grants permission to retrieve participant information about private leaderboards | Read | |||
| ListPrivateLeaderboards [permission only] | Grants permission to list all the available private leaderboards | Read | |||
| ListSubscribedPrivateLeaderboards [permission only] | Grants permission to list all the subscribed private leaderboards | Read | |||
| ListTagsForResource | Grants permission to lists tag for a resource | Read | |||
| ListTracks [permission only] | Grants permission to list all DeepRacer tracks | Read | |||
| ListTrainingJobs [permission only] | Grants permission to list a DeepRacer model's training jobs | Read | |||
| MigrateModels [permission only] | Grants permission to migrate previous reinforcement learning models for DeepRacer | Write | |||
| PerformLeaderboardOperation [permission only] | Grants permission to performs the leaderboard operation mentioned in the operation attribute | Write | |||
| RemoveLeaderboardAccessPermission [permission only] | Grants permission to remove access for a private leaderboard | Write | |||
| SetAlias [permission only] | Grants permission to set the user's alias for submitting a DeepRacer model to leaderboards | Write | |||
| StartEvaluation [permission only] | Grants permission to evaluate a DeepRacer model in a simulated environment | Write | |||
| StopEvaluation [permission only] | Grants permission to stop DeepRacer model evaluations | Write | |||
| StopTrainingReinforcementLearningModel [permission only] | Grants permission to stop training a DeepRacer model | Write | |||
| TagResource | Grants permission to tag a resource | Tagging | |||
| TestRewardFunction [permission only] | Grants permission to test reward functions for correctness | Write | |||
| UntagResource | Grants permission to untag a resource | Tagging | |||
| UpdateCar [permission only] | Grants permission to update a DeepRacer car in your garage | Write | |||
Resource types defined by AWS DeepRacer
The following resource types are defined by this service and can be used in the
Resource
element of IAM permission policy statements. Each action in the
Actions table
identifies the resource types that can be specified with that action. A resource type can also define which condition keys you can include in a policy. These keys are displayed in the last column of the Resource types table. For details about the columns in the following table, see
Resource types table
.
| Resource types | ARN | Condition keys |
|---|---|---|
| car |
arn:$
{
Partition}:deepracer:$
{
Region}:$
{
Account}:car/$
{
ResourceId}
|
|
| evaluation_job |
arn:$
{
Partition}:deepracer:$
{
Region}:$
{
Account}:evaluation_job/$
{
ResourceId}
|
|
| leaderboard |
arn:$
{
Partition}:deepracer:$
{
Region}::leaderboard/$
{
ResourceId}
|
|
| leaderboard_evaluation_job |
arn:$
{
Partition}:deepracer:$
{
Region}:$
{
Account}:leaderboard_evaluation_job/$
{
ResourceId}
|
|
| reinforcement_learning_model |
arn:$
{
Partition}:deepracer:$
{
Region}:$
{
Account}:model/reinforcement_learning/$
{
ResourceId}
|
|
| track |
arn:$
{
Partition}:deepracer:$
{
Region}::track/$
{
ResourceId}
|
|
| training_job |
arn:$
{
Partition}:deepracer:$
{
Region}:$
{
Account}:training_job/$
{
ResourceId}
|
Condition keys for AWS DeepRacer
AWS DeepRacer defines the following condition keys that can be used in the
Condition
element of an IAM policy. You can use these keys to further refine the conditions under which the policy statement applies. For details about the columns in the following table, see
Condition keys table
.
To view the global condition keys that are available to all services, see Available global condition keys .
| Condition keys | Description | Type |
|---|---|---|
| aws:RequestTag/${TagKey} | Filters actions by tag key-value pairs in the request | String |
| aws:ResourceTag/${TagKey} | Filters actions by tag key-value pairs attached to the resource | String |
| aws:TagKeys | Filters actions by tag keys in the request | ArrayOfString |
| deepracer:MultiUser | Filters access by multiuser flag | Bool |
| deepracer:UserToken | Filters access by user token in the request | String |


The <xenon-linkify> component hyperlinks plain text content and adds carriage returns.
Output:
Now is the time for all good men
to come to the aid of http://google.com.
Contact support by calling<PHONE_NUMBER> or
emailing us at<EMAIL_ADDRESS>You can also try http://support.google.com


A Small sample of photos Taken by McKinley Fulmer.
Lens: SIGMA 70-200mm F2.8 DG OS HSM
Subject:
Subject: Sunflower With Bees
Lens: Nikon AF-S 50mm F1.8


Centaurs originated in Greek mythology.
They have the body of a horse and the torso of a man.
Centaurs represented barbarism and chaos to the Greeks.
Chiron was the most well known Centaur and was a tutor for Hercules, Achilles and Jason.
Centaurs followed the Greek god Dionysus.
Cyclops originated in Greek mythology.
Cyclops are generally larger than a human and look humanlike in appearence. But with only 1 eye in the center of their face instead of two.
According to Greek mythology, Cyclops were a race of lawless creatures.
Cyclops were known to build and craft powerful weapons which they gave to different hero's.
They were known to have very poor depth perception.
Dragons did not orginate from one singular culture. They have appeared in many differing cultures.
Dragons have a large lizard like body, generally with wings. They have a tail have 4 legs.
In some cultures Dragons are known to fly and breathe fire.
Dragons are often found in lairs with gold and other valuables.
Dragons often appear very smart and live a very long time.
Faries originated in the Middle Ages in Europe and are found in Greek mythology.
Faries are described as tiny human-like creatures who have magical abilitiesIn folklore fairies rarely have wings and are usually described with wings in the Victorian artworks 'Banshees' are malevolent fairies who usually appear only to foretell a tragedy
Fairies were thought of as to be demons in Puritanism.
Faries are allergic to iron.
One of the earliest claims of contact with a fairy was recorded in 1907.
Griffins originated in western Asia and into Greece by the 14th century BCE
Usually appears to have a body of a lion with brown fur and tufted tail with the head, wings and forelegs of an eagle.
They are often found guarding treasure.
They can fly.
They symbolize intelligence and strength.
Kelpie's originated in Scotland.
The Kelpie is a shape shifting aquatic spirit of Scottish legend.
Kelpie's have been described as having a mermaid like tail when entering the water. The Kelpie is a shape shifting aquatic spirit of Scottish legend.
Kelpie's haunt rivers and streams taking shape of a horse.
They are able to summon floods.
Most people think of kelpies as creatures you should never cross paths with, while some people actually consider them to save children from drowning.
Earliest mentions from Syria 1000BC
Mermaids are generally depicted as female humans from the waist up with the lower half of a fish.
In sailor folklore mermaids can signify both good and bad luck.
It was frequent for a mermaid to be carved into the bow of a ship to appease the sea and bring good fortune to a voyage.
Mermaids are often confused with Sirens, as seen in Homer's Odyssey, though they are not the same creature.
Vampires originated in Medieval Europe.
A vampire is an undead human, who has previously died (often of the bite of another vampire), and has risen from the grave to feed on the blood of living humans.
Vampires fear holy symbols such as the cross, avoid garlic, and can be killed with a steak through the heart.
In the 18th century in Europe a mass panic arose in which even the governments of various countries were involved in digging up suspected graves of vampires and staking the corpses to keep them from rising.
Bram Stoker's Dracula was a novel published in 1897 that told one of the most famous vampire legends in history.
Werewolves appears to have originated in the Epic of Gilgamesh.
Werewolves are part human and part wolf, generally frozen somewhere in the middle of a transformation between the two.
Werewolves can only be injured by silver.
People who are werewolves seem as normal most days of the month, but transform into their bestial form on nights of the full moon.
Ancient Greeks and Romans believed lycanthropy could be cured by exhaustion and people believed to be werewolves were sentenced to long periods of physical labor.
Goblins come from several different European cultures.
Goblins are generally small with grotesque features such as warts.
One of the most famous depictions of Goblins is from Lord of the Rings.
Goblins fear and hate horses and dogs.
A group of Goblins is referred to as a horde and female Goblins are called Hags, Crones, or Goblettes.

The most famous Hydra is the Lernaean Hydra of Greek myth.
Hydra blood is poisonous, and Hercules dipped his arrows in ones blood, which his wife used to kill him.
If you cut a head off the Hydra 2 more will grow to take its place.
Troll's originated in Scandinavian and Norse mythology.

Often times it is said Trolls are turned to stone if exposed to sunlight.
In folklore Trolls rarely help humans and often try to eat them.
It is said that Trolls can turn perfectly fine food rotten just by breathing on it.
The Unicorn comes from ancient Greek and Indus Valley civilizations.
Unicorns are horse-like and have a long horn coming from their head.
A Unicorns horn is known as an Alicorn.

A Unicorn that can fly is known as a Pegasus.
Kitsune comes from Japan and literally translates to Fox.
In Japanese folklore Kitsune are smart, devious creatures, often with magical powers.
A Kitsune can transform itself to look like a human.
In some stories Kitsune can take control of a Human female and are known as Kitsunetsuki.
Kitsune sometimes cannot get rid of their tails when they transform into a human.
Dryads come from Greek Mythology.
They are a type of Nymph, usually depicted as a female who is part plant.
Dryads live as long as the tree they are connected to, if the tree dies they die.
Dryads are loyal to the Goddess Artemis.
As an infant, Zeus was looked after by several Dryads.
Genie's come from Arabic cultures.
A Genie, or Djinn is a magical spirit that is bound to a vessel.
Djinn delight in punishing humans for harm done.
The story of Aladdin comes from a Turkish folklore entitled One Thousand and One Nights.
If you free a Genie from its vessel it will grant you 3 wishes.
Wendigo's come from First Nation Algonquin tribes in the East Coast of Canada
Wendigo's can take control of people, to do this they give them a sickness known as Wendigo fever. This drives the person mad.
As a Wendigo ages it becomes more and more dangerous.
There is a real posychological disorder where people gain an appetite for human flesh. This is know an Wendigo Psychosis.
They feed on humans.
The Thunderbird comes from Native American mythology in the United States and Canada.
It is described as an enourmas bird with massive wings.
The flapping of its wings sounds like thunder and it can shoot lightning from its eyes.
There are stories of the bird picking up whales with its talons from the ocean.
It is a symbol of power and strength.
Gorgons come from Greek Mythology.
Gorgons were 3 female monsters which were all sisters. Stheno, Eurale, and Medusa.
They could turn people to stone by looking at them.
They had gold wings and snakes in place of their hair.
Two of the sisters, were immortal. The third, Medusa, was killed by Perseus using a shield as a mirror.
Phoenix's trace their roots back to Roman and Egyptian mythology.
They appear as a giant bird.
They could live for up to 500 years before dying and then being reborn.
They could breathe fire and were strengthened by the sun.
When close to death, they build a nest of fire and would be born again in about 3 days once they died.


| Class | Description |
|---|---|
| Configuration | |
| Configuration.Builder | |
| DeploymentOptionSection |
The DeploymentOptionSection specifies a discrete set of intended resource configurations.
|
| DeploymentOptionSection.Builder<B extends DeploymentOptionSection.Builder<B>> | |
| Disk | |
| Disk.Builder | |
| DiskSection |
A DiskSection describes meta-information about virtual disks in the OVF package.
|
| DiskSection.Builder<B extends DiskSection.Builder<B>> | |
| Item |
Java class for anonymous complex type.
|
| MsgType |
Type for localizable string.
|
| MsgType.Builder<B extends MsgType.Builder<B>> | |
| Network | |
| Network.Builder | |
| NetworkSection |
The NetworkSection element shall list all logical networks used in the OVF package.
|
| NetworkSection.Builder<B extends NetworkSection.Builder<B>> | |
| OperatingSystemSection |
An OperatingSystemSection specifies the operating system installed on a virtual machine.
|
| OperatingSystemSection.Builder<B extends OperatingSystemSection.Builder<B>> | |
| ProductSection |
The ProductSection element specifies product-information for an appliance, such as product name,
version, and vendor.
|
| ProductSection.Builder<B extends ProductSection.Builder<B>> | |
| ProductSectionProperty |
Property element
|
| Property | |
| Property.Builder<B extends Property.Builder<B>> | |
| PropertyConfigurationValueType |
Type for alternative default values for properties when DeploymentOptionSection is used
|
| SectionType |
Metadata about a virtual machine or grouping of them.
|
| SectionType.Builder<B extends SectionType.Builder<B>> | |
| StartupSection |
Specifies the order in which entities in a VirtualSystemCollection are powered on and shut down
|
| StartupSection.Builder<B extends StartupSection.Builder<B>> | |
| StartupSectionItem |
Java class for Item element declaration.
|
| VirtualHardwareSection |
The virtual hardware required by a virtual machine is specified in VirtualHardwareSection.
|
| VirtualHardwareSection.Builder<B extends VirtualHardwareSection.Builder<B>> |
Copyright © 2009-2013 jclouds. All Rights Reserved.


The content on this application is provided by Chugulu Inc.. Please read these terms and conditions carefully, they are the terms of use for our Application « Games Me 5 » as provided by Chugulu Inc.
1. User obligation
Use of our Application constitutes your acknowledgement and acceptance of these Terms and Conditions, which take effect on the date on which you first use our Application. By accessing, using and/or downloading materials from this application, you agree on your own behalf and on behalf of each entity and person on whose behalf you act to abide by the terms and conditions set forth below. Chugulu Inc. reserves the right to change these Terms and Conditions at any time and it is your responsibility to refer to and comply with these terms on accessing our Application. Your continued use of this application after changes are posted constitutes your acceptance of these terms and conditions as modified. If these Terms and Conditions are not accepted in full, you do not have permission to access the contents of this application and therefore should cease using this application immediately. If there is any conflict between these Terms and Conditions and rules and/or specific terms of use appearing on this application relating to specific material then the latter shall prevail.
2. Copyright and Other Intellectual Property
The names, images and logos identifying Chugulu Inc. applications, associated companies or third parties and their products and services are proprietary marks of Chugulu Inc., its associated companies and/or third parties. Nothing contained herein shall be construed as conferring by implication or otherwise any license or right under any trade mark or patent of Chugulu Inc., its associated companies or any other third party. All copyright, trade marks and other intellectual property rights in this application (including the design, arrangement and look and feel) and all material or content supplied as part of our Application shall remain at all times the property of Chugulu Inc. or Chugulu Inc.'s licensors. In accessing the Chugulu Inc. application, you agree that you do so only for your own personal, non-commercial use. You may not agree to, permit or assist in any way any third party to copy, reproduce, download, post, store, distribute, transmit, broadcast, commercially exploit or modify in any way the material or content without Chugulu’s prior written permission.
3. Terms of use
The use of this application is only for lawful purposes, in a manner which does not infringe the rights of or restrict or inhibit the use and enjoyment of this application by any third party. Such restriction or inhibition includes, but is not limited to, conduct which is defamatory, or which may harass, cause distress or inconvenience to any person and the transmission of obscene or offensive content or interruption of the normal flow of dialogue within this application.
4. Third Party Applications / Links
Chugulu Inc. is not responsible for the availability or content of any third party websites or material you access through this application. If you decide to visit any linked site, you do so at your own risk and it is your responsibility to take all protective measures to guard against viruses or other destructive elements. Chugulu Inc. does not endorse and is not responsible or liable for any content, advertising, products, services or information on or available from third party websites or material (including payment for and delivery of such products or services). Chugulu Inc. is not responsible for any damage, loss or offence caused by or, in connection with, any content, advertising, products, services or information available on such websites or material. Any terms, conditions, warranties or representations associated with such dealings, are solely between you and the relevant provider of the service. Links to this application must be direct to any complete content page (and not any part of a page) within Chugulu Inc. and must not be viewed within the pages of any other application. Chugulu Inc. disclaims all liability for any legal or other consequences (including for infringement of third party rights) of links made to this application. Links do not imply that Chugulu Inc. endorses, is affiliated or associated with any linked application, or is legally authorised to use any trademark, trade name, logo or copyright symbol displayed in or accessible through the links, Games Me 5 or that any linked application is authorised to use any trademark, trade name, logo or copyright symbol of or any of its affiliates or subsidiaries.
5. Disclaimer/Limitation of Liability
This application and the information, names, images, pictures, logos and icons relating to Games Me 5, Chugulu Inc. and/or any associated company, products and services (or to third party products and services), is provided "AS IS" and on an "AS AVAILABLE" basis without any representation or endorsement being made and without warranty of any kind, including but not limited to the implied warranties of satisfactory quality, fitness for a particular purpose, non-infringement, compatibility, security and accuracy. The information and other materials included on this application may contain inaccuracies and typographical errors. Chugulu Inc. does not warrant the accuracy or completeness of the information and materials or the reliability of any statement or other information displayed or distributed through our Application (including, without limitation, the information provided through the use of any software). You acknowledge that any reliance on any such statement or information shall be at your sole risk. Chugulu Inc. reserves the right, in its sole discretion, to correct any errors or omissions in any part of our Application and to make changes to our Application and to the materials, products, programs, services or prices described in our Application at any time without notice. In no event will Chugulu Inc. and/or third parties be liable or any damages including, but not limited to, indirect or consequential damages or any damages including, but not limited to, errors or omissions, indirect or consequential damages or any damages whatsoever arising from use, loss of use, data or profits, whether in action of contract, negligence or other action, arising out of or in connection with the use of our Application. These exclusions do not apply to death or personal injury caused by Chugulu Inc.'s negligence and only applies to the extent permitted by law. Chugulu Inc. does not warrant that the functions contained in this application will be uninterrupted or error free or that defects will be corrected or that this application or the server that makes it available are free of viruses or bugs. Chugulu Inc. does not represent the full functionality, accuracy or reliability of any material. Chugulu Inc. may terminate, change, suspend or discontinue any aspect of this application, including the availability of any features of our Application, at any time without notice or liability.
6. Software
From time to time certain software which is the protected work of Chugulu Inc. or its suppliers may be made available to download from this application. You are licensed to use the software on a non-exclusive basis only for the purposes for which it is indicated. You may not use the software for any other purpose and may not redistribute, sell, decompile, reverse engineer, disassemble or otherwise deal with the software.
7. Indemnity
You agree to indemnify and keep indemnified Chugulu Inc. from and against all claims, damages, expenses, costs and liabilities arising in any manner from your entry to and use of our Application other than in accordance with these terms and conditions.
8. Law and jurisdiction
These Terms and Conditions shall be governed by and construed in accordance with the laws of the United States of America. Disputes arising herefrom shall be exclusively subject to the jurisdiction of the courts of the United States of America. Any cause of action you may have with respect to your use of this application must be commenced within one (1) year after the claim or cause of action arises. If any of these Terms and Conditions should be determined to be illegal, invalid or otherwise unenforceable by reason of the law of any state or country in which these Terms and Conditions are intended to be effective, then to the extent and within the jurisdiction in which that Term or Condition is illegal, invalid or unenforceable, it shall be severed and deleted from that clause and the remaining terms and conditions shall survive and continue to be binding and enforceable. Chugulu Inc. makes no representation that materials on this application are appropriate or available for use at other locations outside of the United States of America and access to them from territories where their contents are illegal is prohibited. If you access this application from a location outside of the United States of America, you are responsible for compliance with all local laws.