W.P. No.43370/2016 IN THE HIGH COURT OF JUDICATURE AT MADRAS DATED : 05.08.2019 CORAM THE HONOURABLE MR.JUSTICE S.MANIKUMAR and THE HONOURABLE MR.JUSTICE SUBRAMONIUM PRASAD Writ Petition No.43370 of 2016 and W.M.P. No.37228 of 2016 Dr.J.Umarani ...Petitioner Vs 1. The State of Tamil Nadu, Rep.by its Secretary, Health & Family Welfare Department, Fort.St.George, Chennai 600 009. 2. Tamil Nadu Pollution Control Board, By its Member Secretary, 76, Mount Salai, Guindy, Chennai 600 032. 3. The Union of India, Rep.by its Secretary, Ministry of Environment, Forest & Climate Change, New Delhi. ... Respondents Writ Petition filed under Article 226 of The Constitution of India praying for the issuance of a Writ of Mandamus directing the respondents herein to take appropriate steps towards effective implementation of Bio- Page No.1 of 40 http://www.judis.nic.in W.P. No.43370/2016 Medical Waste Management Rules, 1998 and as amended in GSR 343 (E) dated 28.03.2016 issued by the third respondent on 2016 including issuance of license to any person or concern authorizing to treat the category Bio Medical Waste viz., soiled linen, beddings and items contaminated with blood or body fluid. For Petitioner : Mr.R.S.Jeeva Rathinam, Senior Counsel for M/s.Madhuri Donti Reddy For Respondents : Mr.E.Manoharan Additional Government Pleader for R1 Mr.H.Yasmeen Ali for R2 ORDER
[Order was delivered by S.MANIKUMAR,J] The present writ petition has been filed as a Public Interest Litigation for a Writ of Mandamus, directing the respondents herein to take appropriate steps towards effective implementation of Bio-Medical Waste Management Rules, 1998 and as amended in GSR 343(E) dated 28.03.2016, issued by Union of India, represented by its secretary, Ministry of Environment, Forest & Climate Change, New Delhi/third respondent herein, including issuance of licence to any person or the concerned authorizing to treat the category, bio-medical Waste viz., soiled linen, beddings and items Page No.2 of 40 http://www.judis.nic.in W.P. No.43370/2016 contaminated with blood or body fluid.
2. Petitioner is a doctor and has put in 32 years of practice in the field of Medicine. She has worked as a Professor in Madras Medical College and Kilpauk Medical College, Chennai and holder of a Post Graduate Degree in Micro-Biology. The petitioner states that, Union of India has framed rules with respect to treatment of Bio-Medical Waste, wherein, each and every occupier is mandated to maintain the standards as mentioned therein, in treating Bio-Medical Waste. Tamil Nadu Pollution Control Board, Guindy, Chennai/second respondent herein, being the prescribed statutory authority, has not issued license to any one or any concerned to treat Bio-
Medical Waste and the State of Tamil Nadu, represented by its Secretary, Health & Family Welfare Department, Chennai/first respondent herein, being the Chairman of the Advisory Committee is bound to see whether the rules are implemented. Since there is no authorised person to handle Bio-
Medical waste in the State of Tamil Nadu, the same are not treated, as per the provisions of Bio-Medical Waste Rules. According to the petitioner, impact of the same is posing a serious threat to the environment as well as health hazardous to the public. There is no separate provision made in any hospital for collection of Bio-Medical Waste. In most of the hospitals, the Page No.3 of 40 http://www.judis.nic.in W.P. No.43370/2016 infectious wastes are not transported as per the provisions.
3. According to the petitioner, in view of the undisputed fact that the second respondent, Tamil Nadu Pollution Control Board, Chennai, has not issued any licence to any hospital or any individual to treat Bio-Medical Waste, it is obvious that Bio-Medical Waste are treated against the provisions, causing serious threat to the environment and health of the public at large. In view of non-usage of authorised persons, who have licence to treat soiled linens, there is so much of health hazards.
Unauthorised washing of these linens/clothes is exposed to danger, as washing is done in public water bodies and that the water gets contaminated with the untreated Bio-Medical Waste. The water so contaminated can very well categorised as chemical liquid waste and all these contamination stand in contravention of the Water Act, but also invites health hazards to humans.
4. According to the petitioner, the ordinary washers/launderers are not well informed of the impact of washing soiled linen, whereas all the hospitals are well informed and educated with respect to the impact of treating the soiled linen. The hospitals are not caring about the impacts, for Page No.4 of 40 http://www.judis.nic.in W.P. No.43370/2016 the simple reason of the cost cutting factors alone. It is also a matter of concern, as water is also mixed with the drainage and effluents which contain toxicants, pathogens, and is at the risk of causing numerous health hazards to humans. The impact of the effluent from washing of soiled linen would contain Bio-Medical Waste and pose a direct threat to life of people at large. Since the rules framed, which according to the petitioner, are not implemented, the present writ petition is filed.
5. Per contra, Mr.E.Manoharan, learned Additional Government Pleader, appearing for the Health and Family Welfare Department, State of Tamil Nadu/first respondent submitted that, in Government Hospitals, bio medical wastes are segregated into colour coded plastic bags placed in bins and managed, as per Schedule I of Bio Medical Waste Management Rules, 2016. In all the Government Hospitals in Tamil Nadu, bio medical waste is segregated, at the source like wards, IMCU, Operation theatre etc., and transported to a common storage area, inside the campus of every institution and from there, bio medical wastes are handed over to the government authorised Common Bio Medical Waste Treatment Facility provided for final disposal, as per the norms. They have an agreement with Common Bio Medical Waste Treatment Facility Provider for disposing the Page No.5 of 40 http://www.judis.nic.in W.P. No.43370/2016 segregated bio medical wastes. There are 11 common bio medical waste treatment facility providers approved by the Tamil Nadu Pollution Control Board/second respondent herein. Agreement has been made between the hospital administration (occupier) and Common Bio Medical Waste Treatment Facility (CBWTF) provider, according to the districts allotted to them.
6. He has further submitted that 46 hospitals under the control of Directorate of Medical Education, 29 District Head Quarters hospital, 206 Taluk Hospitals and 68 Non Taluk Hospitals have obtained authorisation for handling Bio Medical Wastes from the Tamil Nadu Pollution Control Board.
Bio Medical Waste Management Rules, 2016, has been issued in super-
session of the Bio Medical Waste (Management and Handling) Rules, 1998 and is not an amendment to the earlier Rules, as wrongly stated by the petitioner and Bio Medical Waste Management Rules, 2016, speak about wastes, such as discarded/condemned/soiled linen wastes, and not about soiled or regular hospital linen.
7. As per Bio Medical Waste Management Rules, 2016 Schedule - I -
Category Yellow-(c) Soiled Waste, consists of items contaminated with Page No.6 of 40 http://www.judis.nic.in W.P. No.43370/2016 blood, body fluids like dressings, plaster casts, cotton swabs and bags containing residual or discarded blood and blood components. The treatment and disposal option for this category, is incineration or Plasma Pyrolysis or deep burial. In the absence of above facilities, autoclaving or micro-waving/hydro-claving is followed by shredding or mutilation or combination of sterilization and shredding. Treated waste has to be sent for energy recovery. Soiled and regular hospital linens are managed, as per World Health Organisation Practical Guidelines for infection control in Health Care facilities SEARO Publication-no 41-WPRO regional publication 2004-page 26. Soiled and regular hospital linen are disinfected with Sodium Hypochlorite solution and washed with detergent in the steam laundry (70C-
80C).
8. It is his further contention that, as per the minutes of meeting of the Tamil Nadu Pollution Control Board (TNPCB) on 22.09.2016, it was decided that larger hospitals, in consultation with TNPCB, may provide laundry facilities, on their own for treatment of disinfected and soiled linen and can also tie up with other hospitals for the treatment of the same.
However hospitals shall strictly comply with the standards prescribed by the Board. Chairman, TNPCB has informed that the facilities provided by Page No.7 of 40 http://www.judis.nic.in W.P. No.43370/2016 the hospitals, will be inspected by TNPCB officials and necessary guidelines/instructions would be provided for any further improvement.
9. Government Hospitals under the control of Directorate of Medical Education, have laundry and CSSD (Central Sterile Supply Department) through which soiled linen are disinfected, washed and autoclaved. Soiled Linen has not come under the scope of Bio Medical Waste Management Rules, 2016, Schedule-I-category Yellow-(c). All the government hospitals have Bio Medical Waste Management Committees and Hospital infection control committees. Every month, Hospital infection Control Committees, audit the situation and initiate necessary corrective measures are taken.
There are 11 Common Bio Medical Waste Treatment facility providers approved by the Tamil Nadu Pollution Control Board. The occupier (Hospital Administration) would not do on-site treatment for Bio Medical Waste except, pre-treatment of the laboratory waste, microbiological waste, blood samples and blood bags through disinfection or sterilisation on-site, in the manner, as prescribed by the World Health Organisation (WHO) or National AIDs Control Organisation (NACO) guidelines, and then sent to the common bio-medical waste treatment facility for final disposal, as per the Bio Medical Waste Management Rules, 2016.
Page No.8 of 40http://www.judis.nic.in W.P. No.43370/2016
10. According to Mr.E.Manoharan, learned Additional Government Pleader, in Government Hospitals, Bio Medical Waste is segregated into colour coded plastic bags placed in bins and managed, as per the Schedule-I of Bio Medical Waste Management Rules, 2016. In Tamil Nadu, State Level Advisory Committee for Bio Medical Waste Management has been constituted as per G.O.Ms.No.277 Health and Family Welfare (H1) Department dated 29.11.2016 and District and Hospital level Bio Medical Waste Committees have been constituted as per G.O. (Ms) No.179 Health and Family Welfare (H1) Department dated 06.07.2016 to monitor Bio Medical Waste Management in the State. State Level Advisory Committee has been constituted, as per rule 11 of the Bio Medical Waste Management Rules, 2016, under the Chairmanship of the Principal Secretary to the Government, Health & Family Welfare Department, Government of Tamil Nadu. The Member Secretary, Tamil Nadu Pollution Control Board is also one among the members of the said Advisory Committee.
11. Mr.H.Yasmeen Ali, learned counsel for the Tamil Nadu Pollution Control Board, represented by its Member Secretary, Guindy, Chennai/second respondent, submitted that the Ministry of Environment, Page No.9 of 40 http://www.judis.nic.in W.P. No.43370/2016 Forest and Climate Change, Government of India, in exercise of the powers conferred by sections 6, 8 and 25 of the Environment (Protection) Act, 1986 (Act 29 of 1986) and in super-session of the Bio-Medical Waste (Management and Handling) Rules, 1998, have notified Bio-Medical Waste Management Rules, 2016. In the said rules, duties of the occupier, Common biomedical waste treatment and disposal facility and authorities, have been prescribed. Section 2 (n) of the Biomedical Waste Management Rules, 2016, defines operator, as "operator of a common bio-medical waste treatment facility" means a person who owns or controls a Common Bio-Medical Waste Treatment Facility (CBMWTF) for the collection, reception, storage, transport, treatment, disposal or any other form of handling of bio-medical waste".
12. As per Rule 7(1) of the said Rules, "Bio-Medical wastes shall be treated and disposed of in accordance with schedule I, and in compliance with the standards provided in Schedule-II by the health care facilities and common bio-medical waste treatment facility. "Whereas schedule I refers to the Biomedical wastes categories and their segregation, collection, treatment, processing and disposal options. As per yellow category, waste under section (g) clearly refers to "Discarded Linen, Mattresses, Beddings Page No.10 of 40 http://www.judis.nic.in W.P. No.43370/2016 contaminated with blood or body fluid”. As per the schedule, the said waste has to be collected in a non-chlorinated yellow plastic bags or suitable packing material and to be subjected to non-chlorinated chemical disinfection followed by incineration or plasma pyrolysis or for energy recovery by the respective Common Bio-Medical Waste Treatment Facilities.
13. It is the further contention of the learned counsel for the Tamil Nadu Pollution Control Board that, in pursuance of the orders of the Hon'ble High Court order dated 23.12.2016, bio medical waste generated from the hospitals and the health centres are treated through 11 Common Bio Medical Waste treatment facilities located in various parts of Tamil Nadu.
14. He has further submitted that discarded linen, mattresses, beddings contaminated with blood or body fluid generated from the health care facilities are collected by the respective Common Bio Medical Waste Treatment Facilities and subjected to incineration. Of the 11 Common Biomedical Waste Treatment Facilities, 9 facilities have the provision of incinerator. All the 11 Common Biomedical Waste Treatment Facilities have obtained authorisation from TNPCB for collection, treatment and disposal of biomedical wastes including the discarded linen, mattresses, beddings Page No.11 of 40 http://www.judis.nic.in W.P. No.43370/2016 contaminated with blood or body fluid. TNPCB is continually addressing the Health Secretary for effective handling of bio-medical waste, as per the said Rules.
15. He has further submitted that, after the notification of the Biomedical Waste Management Rules, 2016, Chairman, TNPCB vide DO letter dated 28.04.2016 has addressed the Secretary to the Government, Health and Family Welfare Department, Secretariat, Chennai, to issue necessary instructions, to all the Government Health Care Institutions including medical colleges in the State, to comply with the provisions of the Bio Medical Waste Management Rules, 2016. TNPCB has addressed the common biomedical waste treatment facilities in Tamil Nadu, to strictly adhere to all the provisions of Biomedical Waste Management Rules, 2016.
16. In the rejoinder, the petitioner has averred that Tamil Ndu Pollution Control Board, Guindy, Chennai/second respondent has approved 11 common Bio Medical Waste Treatment facilities. However the State of Tamil Nadu, represented by its Secretary, Health & Family Welfare Department, Chennai/first respondent herein, is under a total misconception that rules for treatment of Bio Medical Waste relate only to Page No.12 of 40 http://www.judis.nic.in W.P. No.43370/2016 those that need to be discarded and be governed, as per section 2 (f) of the Bio Medical Waste Management Rules, 2016.
17. Petitioner has contended that the responsibility of the respondents, do not end with merely enacting laws & granting licences to Common Bio Medical Waste Treatment Facility.
18. According to the petitioner, the respondents till date, have not mentioned, as to whether they have granted licence to any person, individual or corporate entity, for the purpose of disinfecting soiled and regular hospital linen. The Secretary, Health & Family Welfare Department, Chennai/first respondent has only dealt with only that aspect of the Act and the Rules but failed to respond to the query raised as to the methods adopted by the hospitals, dispensaries and laboratories in treating soiled linen through outsourced launderers or their own washing machines or local dhobi.
19. By way of reply to the rejoinder, State of Tamil Nadu, represented by its Secretary, Health & Family Welfare Department, Page No.13 of 40 http://www.judis.nic.in W.P. No.43370/2016 Chennai/ first respondent has stated that Bio-Medical Waste (Management and Handling) Rules, 1998 have come into force on 20.07.1998 and amended in 2000. Modification of 1998 rules have come into force on 28.03.2016 with many changes. The short title of the rules itself, change from Bio Medical Waste (Management and Handling) Rules, to Bio Medical Waste Management Rules, 2016. The number of Bio-Medical Waste categories has changed from 10 to 4. The categories are classified with the well defined treatment option. This is being strictly followed. As of now, the chemical liquid waste generated from the government hospitals in Tamil Nadu are disinfected and drained into sewer lines. Government of Tamil Nadu is in the process of installing Effluent Treatment Plants as per the provisions contained in the Bio-Medical Waste Management Rules, 2016 in consultation with Tamil Nadu Pollution Control Board. Until then, chemical liquid/waste are disinfected and drained into sewer lines.
20. In schedule III, in serial No.2 of the Bio-Medical Waste Management Rules 2016, the corresponding duties of the authorities, namely, the Central or State Ministry of Health and Family Welfare is to grant license to health care facilities or nursing homes or veterinary establishments, with a condition to obtain authorisation from the Page No.14 of 40 http://www.judis.nic.in W.P. No.43370/2016 prescribed authority for Bio-Medical Waste Management. This is the only licence to be given by the Central or State Ministry of Health and Family Welfare. It is submitted that all the Government Hospitals have got Bio-
Medical Waste authorisation from Tamil Nadu Pollution Control Board.
Licence for the purpose of disinfecting and laundering of soiled linen and regular hospital linen, provision is not under the scope of Bio-Medical Waste Management Rules, 2016. According to the said rules, schedule I, part 1, prescribes Bio-Medical Wastes categories and their segregation, collection, treatment, processing and disposal options under the Heading “Schedule – I” in part – 1 in the tabular column against the category “Yellow” specified in column (1) and the entries relating to Chemical Liquid Waste (f) specified in column (2) that the liquid waste generated due to use of chemicals in production of biological and used or discarded disinfectants, silver X-ray film developing liquid, discarded formalin, infected secretions, aspirated body fluids, liquid from laboratories and floor washings, cleaning, housekeeping and disinfecting activities etc., Hence chemical liquid waste category covers all the infectious liquid waste generated from the hospitals.
21. Heard the learned counsel for the parties and perused the materials available on record.
Page No.15 of 40http://www.judis.nic.in W.P. No.43370/2016
22. On this day, when the matter came up for hearing, Mr.R.S.Jeeva Rathinam, learned Senior Counsel appearing for M/s.Madhurai Donti Reddy, learned counsel on record for the petitioner, by inviting the attention of this court, to certain photographs taken in the hospitals and by referring to the judgment dated 22.02.2017 in W.P. No.375 of 2012 in the case of Paryavaran Suraksha Samiti and another Vs Union of India and others paragraph Nos.13 to 17, submitted that though Sewerage Treatment Plants are stated to be established in hospitals, they are not functional and that washing linen is not done as per the decision of the Hon'ble Supreme Court, which is extracted as hereunder:-
"13. We are of the view, that mere directions are inconsequential, unless a rigid implementation mechanism is laid down. We therefore hereby provide, that the directions pertaining to continuation of industrial activity only when there is in place a functional "primary effluent treatment plants", and the setting up of functional " common effluent treatment plants" within the time lines, expressed above, shall be of the Member Secretaries of the concerned pollution control Boards. The Secretary of the Department of Environment, of the concerned State Government (and the concerned Union Territory, shall be answerable in case of default. The concerned Secretaries to the Government shall be Page No.16 of 40 http://www.judis.nic.in W.P. No.43370/2016 responsible of monitoring the progress, and issuing necessary directions to the concerned Pollution Control Board, as may be required, for the implementation of the above directions. They shall be also responsible for collecting and maintaining records of data, in respect of the directions contained in this Order. The said data shall be finished to the Central Ground Water Authority. which shall evaluate the data, and shall furnish the same to the Bench of the jurisdictional National Green Tribunal.
14. To supervise complaints of non-implementation of the instant directions, the concerned Benches of the National Green Tribunal, will maintain running and numbered case files, by dividing the jurisdictional area into units. The above mentioned case files, will be listed periodically. The concerned pollution case files, will be listed periodically. The concerned Pollution Control Board is also hereby directed, to initiate such civil or criminal action, as may be permissible in law, against all or any of the defaulters.
15. Liberty is granted to private individuals, and organizations, to approach the concerned Bench of the jurisdictional National Green Tribunal, for appropriate orders, by pointing out deficiencies in implementation of the above directions.
16. It however needs to be clarified, that the instant directions and time lines, shall not in any way dilute any time lines and directions issued by courts or Benches of the National Page No.17 of 40 http://www.judis.nic.in W.P. No.43370/2016 Green Tribunal, hitherto before, wherein the postulated time lines would expire before the ones expressed through the directions recorded above. It is clarified, that the time lines, expressed herein above will be relevant, only in situations where there are no prevalent time line(s)and also, where a longer period, has been provided for.
17. It would be in the interest of implementation of the objective sought to be achieved, to also require each concerned State ( and each, concerned Union Territory) to make provision for "online, real time, continuous monitoring system" to display emission levels, in the public domain, on the portal of the concerned State Pollution Control Board. We are informed, that atleast three State Governments have already adopted the aforesaid measures. Such measures shall be put in place by all the concerned State Government (including, the concerned Union Territories), within six months from today."
23. Per contra, Mr.E.Manoharan, learned Additional Government Pleader, appearing for the State, submitted that Sewerage Treatment Plants are available in the institutions, coming under the Directorate of Medical Education and Director of Medical & Rural Health Services, and that the same are extracted hereunder:-
STP availability in DME Institutions
1. Tirunelveli Medical College Hospital.
Page No.18 of 40http://www.judis.nic.in W.P. No.43370/2016
2. Theni Medical College Hospital.
3. Tiruvarur Medical College Hospital.
4. Villupuram Medical College Hospital.
5. Tiruvannamalai Medical College Hospital.
6. Government Mohan Kumaramangalam Medical College Hospital, Salem.
7. Sivagangai Medical College Hospital.
8. Tamil Nadu Multi Speciality Hospital, Omandurar, Chennai.
9. TB Hospital, Tambaram.
DMS Institutions
1. Govt. Hospital, Cuddalore.
2. Govt. Hospital, Tiruppur.
3. Govt. Hospital, Tiruvallur.
4. Govt. Hospital, Kallacurichi.
5. Govt. Hospital, Manaparai.
6. Govt. Hospital, Erode.
7. Govt. Hospital, Padmanabapuram.
8. Govt. Hospital, Tenkasi.
9. Govt. Hospital, Ramanathapuram.
10. Govt. Hospital, Mayiladuthurai.
11. Govt. Hospital, Tambaram.
12. Govt. Hospital, Hosur.
13. Govt. Hospital, Sholingar
14. Govt. Hospital, Arupukkottai.
Page No.19 of 40http://www.judis.nic.in W.P. No.43370/2016
24. It is the further contention of Mr.E.Manoharan, learned Additional Government Pleader that, Government have issued orders in G.O. Ms.No.179, Health and Family Welfare (H1) Department, dated 06.07.2016 for Constitution of District and Hospital Level Committee, for Bio Medical Waste Management. He also added that the issue of washing linen is not in accordance with the direction of the Hon'ble Supreme Court, but the same is pending before the National Green Tribunal. Submission of the learned Additional Government Pleader is placed on record.
25. Biomedical Waste (Management & Handling) Rules, 1998, as amended on 2000, is extracted hereunder:
BIOMEDICAL WASTE (MANAGEMENT & HANDLING) RULES 1998 Amended on 2000 • The powers confirmed by section 6, 8, and 25 of the Environment (Protection) Act 1986, the Central Govt. has made The Biomedical Waster (Management & Handling) Rules to safeguard the public and health care workers from the risk arising due to Biomedical Waste. The penalties are same as specified in Environment (Protection) Act 1986. Delhi hospitals alone produce more than 30 tonnes of biomedical waste every day. None of them has satisfactory biomedical waste management (CPCB 2001). There is a need to have centralized facility which will enable the authority to monitor and maintain in a better way.Page No.20 of 40
http://www.judis.nic.in W.P. No.43370/2016
1.  Definition: In these rules unless the context otherwise requires: -
1. “Act” means the Environment (Protection) Act, 1986 (29 of 1986);
2. “Animal House” means a place where animals are reared/kept for experiments or testing purposes;
3. “Authorization” means permission granted by the prescribed authority for the generation, collection, reception, storage, transportation, treatment, disposal and/or any other form of handling of bio-medical waste in accordance with these rules and any guidelines issued by the Central Government;
4. “Authorized person” means an occupier or operator authorized by the prescribed authority to generate, collect, receive, store, transport, treat, dispose and/or handle biomedical waste in accordance with these rules and any guidelines issued by the Central Government;
5. “Bio-medical waste” means any waste, which is generated during the diagnosis, treatment or immunization of human beings or animals or in research activities pertaining to in the production or testing of biologicals, and including categories mentioned in Schedule 1;
6. “Biologicals” means any preparation made from organisms or micro organisms or product of metabolism and biochemical reaction intended for use in the diagnosis, immunization or the treatment of disposal of human beings or animals or in research Page No.21 of 40 http://www.judis.nic.in W.P. No.43370/2016 activities pertaining, hereto;
7. “Bio-medical waste treatment facility” means any facility wherein treatment, disposal of bio-medical waster or processes incidental to such treatment or disposal is carried out;
8. “Occupier” in relation to any institution generation bio- medical waster, which includes a hospital, nursing home, clinic, dispensary, veterinary institutions, animal house, pathological laboratory, blood bank by whatever name called, means a person who has control over that institution and/or its premise.
9. “Operator of a bio-medical waster facility” means a person who owns or controls or operates a facility for the collection, reception, storage, transport, treatment, disposal or any other form of handling of bio-medical waste;
10. “Schedule” means schedule appended to these rules;
3. Duty of Occupier It shall be the duty of every occupier of an instituion generating bio-medical waste, which includes a hospital nursing home, clinic, dispensary, veterinary institutions, and animal house, pathological laboratory, blood bank by whatever name called to take all steps to ensure that such waste is handled without any adverse effect to human health and the environment.
4. Treatment and Disposal a. Bio-medical waste shall be treated and disposal of in accordance with Schedule 1, and in compliance with the sandards prescribed in Schedule V.
b. Every occupier, where required, shall set up requisite bio- medical waste treatment facilities like incinerator, autoclave, Page No.22 of 40 http://www.judis.nic.in W.P. No.43370/2016 microwave system for the treatment of waste, or, ensure requisite treatment of waste at a common waste treatment facility or any other waste treatment facility.
5. Segregation, Packing, Transportation and Storage a. Bio-medical waste shall not be mixed with other wastes. b. Bio-medical waste shall be segregated into containers/bags at the point of generation in accordance with Schedule II prior to its storage, transportation, treatment and disposal. The containers shall be labelled according to Schedule III.
c. If a container is transported from the premises where bio- medical waste is generated to any waste treatment facility outside the premises, the container shall, apart from the label prescribed in Schedule III, also carry information prescribed in Schedule IV.
d. Notwithstanding anything contained in the Motor Vehicle Act, 1988, or rules there under, untreated biomedical waste shall be transported only in such vehicles as may be authorized for the purpose by the competent authority as specified by the government.
e. No untreated bio-medical waste shall be kept/stored beyond a period of 48 hours: Provided that if for any reason it becomes necessary to store the waste beyond such period, the authorized person must take permission of the prescribed authority and take measures to ensure that the waste does not adversely affect human health and the environment.
6. Prescribed Authority a. The Government of every State and Union Territory shall establish a prescribed authority with such members as may specified for granting authorization and implementing these rules. If the prescribed authority comprises of more than one member, a Page No.23 of 40 http://www.judis.nic.in W.P. No.43370/2016 chairperson for the authority shall be designated.
b. The prescribed authority for the State or Union Territory shall be appointed within one month of the coming into force of these rules.
c. The prescribed authority shall function under the supervision and control of the respective Government of the State or Union Territory.
d. The prescribed authority shall on receipt of Form 1 make such enquiry as it deems fit and if it is satisfied that the applicant possesses the necessary capacity to handle biomedical waste in accordance with these rules, grant or renew an authorization as the case may be.
e. An authorization shall be granted for a period of three years, including an initial trial period of one year from the date of issue. Thereafter, an application shall be made by the occupier/operator for renewal. All such subsequent authorization shall be for a period of three years. A provisional authorization will be granted for the trial period, to enable the occupier/ operator to demonstrate the capacity of the facility.
f. The prescribed authority may after giving reasonable opportunity of being heard to the application and for reasons thereof to be recorded in writing, refuse to grant or renew authorization.
g. Every application for authorization shall be disposal of by the prescribed authority within ninety days from the date of receipt of the application.
h. The prescribed authority may cancel or suspend an authorization, if for reason, to be recorded in writing, the occupier/operator has failed to comply with any provision of the Act or these rules.
Provided that no authorization shall be cancelled or suspended Page No.24 of 40 http://www.judis.nic.in W.P. No.43370/2016 without giving a reasonable opportunity to the occupier/operator of being heard.
7. Authorization a. Every occupier of an institution generating, collecting, receiving, storing, transporting, treating, disposing and/or handling bio-medical waste in any other manner, except such occupier of clinic, dispensaries, pathological laboratories, blood banks providing treatment/service to less than 1000 (one thousand) patients per month, shall make an application in Form 1 to the prescribed authority for grant of authorization.
b. Every operator of a bio-medical waste facility shall make an application in Form 1 to the prescribed authority for grant of authorization.
c. Every application in Form 1 for grant of authorization shall be accompanied by a fee as may be prescribed by the Government of the State of Union territory.
8. Advisory Committee The Government of every State/Union Territory shall constitute and advisory committee. The Committee will include experts in the field of medical and health, animal husbandry and veterinary sciences, environmental management, municipal administration, and any other related department or organization including non-governmental organizations. The State Pollution Board/ Pollution Control Committee shall be represented. As and when required, the committee shall advise the Union Territory /State Government about matters related to the implementation of these rules.
9. Annual Report Every occupier/operator submit an annual report to the prescribed authority in Form II by 31 January every year, to include information Page No.25 of 40 http://www.judis.nic.in W.P. No.43370/2016 about the categories and quantities of bio-medical wastes handled during the preceding year. The prescribed authority shall send this information in a compiled form to the Central Pollution Control Board by 31 March every year.
10. Maintenance of Records a. Every authorized person shall maintain records related to the generation, collection, reception, storage, transportation, treatment, disposal and/or any form of handling of bio-medical waste in accordance with these rules and any guidelines issued. b. All records shall be subjected to inspection and verification by the prescribed authority at any time.
11. Accident Reporting When any accidents occur at any institution or facility or any other site where biomedical waste is handled or during transportation of such waste, the authorized person shall report the accident in Form III to the prescribed authority forth with.
12. Appeal Any person aggrieved by an order by the prescribed authority under these rules may, within thirty days from date on which the order is communicated to them, refer an appeal to such authority as the Government of State/Union Territory may think fit to constitute: Provided that the authority may entertain the appeal after the expiry of the said period of thirty days if it is satisfied that the appellant of prevent by sufficient cause from filing the appeal in time.
SCHEDULE 1 (See Rule 5) CATEGORIES OF BIO-MEDICAL WASTE, TREATMENT & DISPOSAL Category Biomedical waste Treatment & Disposal Human Anatomical Waste (Human tissues, organs, body parts) Incineration/deep burial * Animal Waste (Animal tissues, organs, body Page No.26 of 40 http://www.judis.nic.in W.P. No.43370/2016 parts carcasses, bleeding parts, fluid, blood and experimental animals used in Incineration/deep burial * research, waste generated by veterinary hospitals colleges, discharge from hospitals, animals houses).
Microbiology & Biotechnology Waste (Wastes from lab. Cultures, stocks of specimens of micro-organisms live or attenuated vaccines, human and animal incineration* cell culture Autoclaving/ micro-waving. used in research and infectious agents from research and industrial laboratories, wastes from production of biologicals, toxins, dishes and devices sued for transfer of cultures) Waste Sharps Needles, syringes, scalpels, Chemical/ disinfection blades, glass etc. that may cause puncture autoclave/ micro-waving andcuts. This includes both used and unused and mutilation/shredding sharps) Discarded Medicines & Cytotoxic drugs incineration/destruct & (Wastes comprising of outdated drugs disposal in secured contaminated and discarded medicines) landfills Soiled Waste (Items contaminated with blood, and body fluids including cotton, incineration/ autoclave dressing, soiled plaster casts, lines, beddings, micro-waving other material contaminated with blood) Sold Waste (Waste generated from Chemical disinfection disposable items other than sharps such as autoclave/micro-waving tubings catheters, intravenous sets, etc.) and mutilation/shredding Liquid Waste (Waste generated from Disinfect-chemically & laboratory and washing, cleaning housekeeping discharge into drains and disinfecting activities) Incineration Ash (Ash from incineration of disposal in municipal any bio-medical waste) landfill Page No.27 of 40 http://www.judis.nic.in W.P. No.43370/2016 Chemical Waste (Chemical used in production Chemically treatment of biologicals, chemicals used in insecticides disinfection and etc.) discharge of drains for liquid and secured landfill for solids.
Note:
1. Chemicals treatment using at least 1% hypochlorite solution or any other equivalent chemical reagent should ensure disinfection.
2. Mutilation/shredding must be such so as to prevent unauthorized reuse.
3. There will be no chemical pretreatment before incineration. PVC shall not be incinerated.
The Central Pollution Control Board has recommended two types of incinerators:
- Incinerators or individual hospitals/nursing homes/medical establishments.
- Common incinerator to handle waste from a number of hospitals/nursing homes/pathological laboratories etc. Site for Incinerator Incinerators should be installed at appropriate location to avoid nuisance to patients and neighbourhood.
COLOUR CODING AND TYPE OF CONTAINER FOR DISPOSAL OF BIO-MEDICAL WASTE Colour Coding Type of Container Waste Category Treatment options Yellow Plastic Bag Categories 1, 2, Incineration deep 3 & 6. burial Red.
Plastic Bag Categories 3, 6, Autoclaving/Microwaving
7 Chemical Treatment
Blue/White Plastic Bag /
Translucent punctproof Cat. 4, Cat. 7 Treatment &
containers Destruction /
shredding
Black Plastic Bag Categories 5, 9,Disposal in secured
10 landfill.
Page No.28 of 40
http://www.judis.nic.in
W.P. No.43370/2016
Notes:
1. Colour coding of waste categories with multiple treatment options as defined in schedule 1, shall be selected depending on treatment option chosen, which shall be as specified in Schedule I.
2. Waste collection bags for waste types needing incineration shall not be made of chlorinated plastics.
3. Categories 8 and 10 (liquid) do not require containers/bags.
4. Category 3, if disinfected locally need not be put in containers/bags.
STANDARDS FOR INCINERATORS All incinerators shall meet the following operating and emission shandards. A. Operating Standards Combustion efficiency (CE) shall be at least 99.0% The compustion efficiency is computed as follows: %CO2 X 100 C.E. = -----------------------------
% COS + % CO
1. The temperature of the primary chamber shall be 800+_ 50 deg C
2. The secondary chamber gas resistance time shall be at least 1 (one) second at 1050 deg + - 50 deg C, with a minimum of 3% Oxygen in the stack gas.
B. Emission Standards Parameters Concentration mg/Nm3 at (12% CO2 correction)
1. Particulate matter 150
2. Nitrogen Oxide 450
3. HCl 50
4. Minimum stack height shall be 30 meters above ground.
5. Volatile organic compounds in ash shall not be more than 0.01 %.
26. As per the directions of the Hon'ble Supreme Court, Government have issued an order in G.O.Ms.No.179, Health and Family Welfare (H1) Department, dated 06.07.2016 for Constitution of District and Hospital Level Committee for Bio Medical Waste Management. Duties and responsibilities of the officers, Bio Medical Management Committee, Page No.29 of 40 http://www.judis.nic.in W.P. No.43370/2016 Medical Officers and others, are set out morefully in G.O.Ms.No.179, Health and Family Welfare (H1) Department, dated 06.07.2016. For brevity, the said G.O. is reproduced hereunder:-
ABSTRACT Bio Medical Waste Management – constitution of District and Hospital Level Committee – Orders – Issued.
-------------------------------------------------------------------------------------------------
Health and Family Welfare (H1) Department G.O.(M.S)No.179 Dated : 06.07.2016 Thiruvalluvar Aandu-2047 Durmughi, Aani-22.
Read:
1.G.O.(Ms) No.72, Environment and Forest Department, dated 06.04.2000
2.G.O.(2D) No.52, Health and Family Welfare Department, dated: 25.07.2005
3.From the Project Director, Tamil Nadu Systems Project, Chennai Letter no.481/HSP/BMWM/2005, dated: 09.12.2005
4.From the Project Director, Tamil Nadu Health Systems Project, Chennai Letter No.4385/HSP/BMWM/2009, dated:11.11.2009, 15.06.2013 and 26.11.2013 ORDER:
The Project Director, Tamil Nadu Health Systems project in his letters third and fourth read above had stated that the Bio Medical Waste generated by the health institutions both in public and private sector needs to be regulated under the Bio Medical Waste (Management and Handling) (Second amendment) Rules 2000, Ministry of Environment and Forest, Government of India Notification, New Delhi, under the health care waste management plan developed by the Tamil Nadu Health Systems Project it was proposed to institutionalize a health care waste management system for Page No.30 of 40 http://www.judis.nic.in W.P. No.43370/2016 the whole health care system in Tamil Nadu. To facilitate the above, the Project Director, has proposed that the Bio Medical Waste Management will be monitored at three levels viz., State level, District level and Hospital Level.
2) In the Government Order first read above orders have been issued for constitution of a State Level Advisory Committee for the implementation of Bio-Medical Waste (Management & handling) Rules, 1998 (as amended, from time to time) under the Chairmanship of Secretary to Government, health and Family Welfare Department.
3) Based on the proposal of the Project Director, Tamil Nadu Health Systems Project third and fourth read above and in accordance with the Bio Medical Waste (Management and handling) Rules 2000 and 2016 the Government Orders that the District Level and Hospital level Bio Medical Wast Management Monitoring Committee be constituted as follows:
Status District Bio Medical Waste Hospital Bio Medical Waste
management Monitoring Management Monitoring
Committee Committee
1. Chairperson District Collector 1. Hospital superintendent /
Chief Medical Officer
2. Member Dean of Medical College
(Wherever Applicable)
3. Member Joint director of Medical and 2. Medical Officer (infection
Secretary Rural Health Services and Control & Environment
Family Welfare health)
4. Member Deputy Director of Medical 3. Nursing Superintendent /
and Rural Health Services Head Nurse / Senior Nurse
and Family Welfare
5. Member Deputy Director of Health 4. Paramedical Staff
Service (Nominated by Hospital
Superintendent / Chief
Medical officer)
6. Member District Environment 5. Assistant Engineer (Public
Page No.31 of 40
http://www.judis.nic.in
W.P. No.43370/2016
Engineer / Assistant Works Department –
Environmental Engineer / Buildings)
Heading and district / All
District Environmental
Engineer in the District.
7. Member All Municipal Commissioners
8. Member Indian Medical Association
(IMA) Representative
9. Member Non Government
Organization (NCO)
Representative (Nominated
by the Collector)
The Director of Medical an Rural Health Service will be the state level coordinator of Health Department.
4)The duties and responsibilities of the Bio Medical Management Committee and its members are annexed to this Government Order.
(BY order of the Governor) J.RADHAKRISHNAN PRINCIPAL SECRETARY TO GOVERNMENT To The Project Director, Tamil nadu Health systems Project, Chennai-6. The Director of Medical and Rural health Services, Chennai-6. The Director of Medical Education, Chennai-10 Copy to:
The Environmental and forest Department, Chennai-9. The Chairman, Tamil Nadu Pollution control Board, Chennai-106. The Health and Family Welfare (Data Cell) Department, Chennai-9.
Stock file/ Spare copy Page No.32 of 40 http://www.judis.nic.in W.P. No.43370/2016 // FORWARDED/ BY ORDER // SECTION OFFICER ANNEXURE Duties and Responsibilities I The State Level Co-ordinator The Director of Medical and Rural Health Services as the State Level Co-ordinator will be responsible for the Management and monitoring of entire Bio Medical Waste Management Programme in Tamil Nadu in Coordination with the Tamil Nadu Pollution Control Board.
II Members of the District Bio Medical Management Committee
1. The Committee will meet once in 15 days and discuss about the proper functioning of Bio Medical Waste management mechanism in the hospitals in proper segregation, storage, transport, end disposal by Common Treatment Facility (CTF), Consumables availability CTF regularity, payments, daily HMIS entries.
2. The District Level Monitoring Committee shall submit its report once in six months to the State Advisory Committee and a copy thereof shall also be forwarded to State Pollution Control Board.
III Joint Director of Medical & Rural Health Services & Family Welfare in Districts
1. Joint Director of Medical and Rural Health Services and Family Welfare will be responsible for the Bio-Medical Waste Management System in the District.
2. The Joint Director is responsible for laying down guidelines for the Hospital Waste Management System in the district and provide funds.
1. Joint Director of Medical and Rural Health Services will be responsible for monitoring the system at the district level and would take corrective Page No.33 of 40 http://www.judis.nic.in W.P. No.43370/2016 action is required.
IV. Responsibilities of Hospital Bio Medical Waste Management Committee ● Proper segregation and storage ● Transport and end disposal by Common Treatment Facility (CTF) Consumables availability ● CTF regularity and payments. Daily HMIS entries Duties and responsibilities of members of the Waste Management committee/Team should be clearly defined to avoid any overlapping. The task could be divided as:
V. Superintendent/Chief Medical Officers ● Apply for authorization ● Formation of Hospital Bio Medical Waste Management Committee ● Responsible for segregation, treatment, collection, transport and stroage of waste within the hospital and its final disposal.
● Provide manpower and resources.
● Will appoint Medical Officer (as infection Control & Environmental Health) to supervise the functioning.
● To liaise with the department heads for coordination and implementation of activities.
VI. Medical Officer (Infection Control & Environment Health) ● Directly report to the Head of the facility. ● Ensure the availability and continuous supply of waste disposal bags and chemical disinfectants.
● Ensure the availability of resources example Needle syringes destroyers, waster collection containers etc., at appropriate sites. ● Ensure implementation at various levels. ● To look into storage and transport of waste. ● To maintain statistics.
● To liaise with Departmental Heads and Nursing Superintendent ● Surprise checks.
● To liaise with Hospital Superintendent/Chief Medical Officer on control of infection.
Page No.34 of 40http://www.judis.nic.in W.P. No.43370/2016 ● To monitor standards of Waste Management. ● To identify the training needs of all categories of staff. ● To organize training programme of all categories of staff.
VII. Nursing Superintendent/Head Nurse ● Responsible for continuous monitoring of waste Management System through out the hospital.
Shall liase with department heads, Medical Officer (Infection Control & Environment Health).
VIII. Role of Doctor and Paramedical Staff in Waste Management Doctors.
● Always wear aprons properly buttoned while examining patients. ● Stick to the golden rules of good hand washing. ● Do not dispose dressing in patients bins.
● Ask for colour coded bags. ● Ensure all plastics and gloves are cut and put in bleach. ● Ensure all used needles and syringes are destroyed using Needles and syringe cutter. ● Ensure compliance during Ward visits. ● Encourage patients and attendants to help follow segregation practices. IX. Nurses ● Identify the problem ● Focus on Segregation ● Sharps ● Plastics ● General Waste ● Infected Waste
Ensure all gloves and plastic are cut and put in bleach Ensure the use of needle and syringe cutters Avoid injury from sharps Take care of spills Ensure – Worker education – Personal protection
- Education of Patients
- Reporting of accidents
- Sanitary workers Page No.35 of 40 http://www.judis.nic.in W.P. No.43370/2016 ● To understand the risk and importance of segregation that it is in their own interest.
● Use of protective coats example glove, aprons, masks etc. ● Do not walk bare foot while handling waste ● Do wet mopping ● Wash hand properly after handling waste ● Wash hand before eating and drinking ● Not to eat or drink near wastage dump J.RADHAKRISHNAN, PRINCIPAL SECRETARY TO GOVENMEMNT //True Copy// SECTION OFFICER
27. We have gone through the pleadings and materials on record and prima facie satisfy that steps are being taken by the Government, as well as by the Tamil Nadu Pollution Control Board, Chennai, respondents 1 & 2, addressing the issue of Bio Medical Waste Management. Details furnished by Mr.E.Manoharan, learned Additional Government Pleader further shows that STPs (Sewerage Treatment Plants), in various Government run hospitals under the control of Directorate of Medical Education and Director of Medical & Rural Health Services. Though, Mr.R.S.Jeeva Rathinam, learned Senior Counsel for the petitioner submitted that still linen washing is not done, as per the directions of the Hon'ble Supreme Court, at this Juncture, we only observe that the directions of the Hon'ble Supreme Court, and guidelines issued in G.O.Ms.No.179, Health and Family Welfare (H1) Page No.36 of 40 http://www.judis.nic.in W.P. No.43370/2016 Department, dated 06.07.2016 for the Constitution of District and Hospital Level Committees should be followed in letter and spirit. Respondents are directed to ensure proper implementation of the same and make the Sewerage Treatment Plants functional, if have not done earlier. Under the 141 of the Constitution of India, orders issued by the Hon'ble Supreme Court are binding, including Courts.
28. To ensure proper implementation of Bio Medical Waste Management rules, respondents 1 & 2 are directed to make a periodical inspection once in two months, of all the health institutions, both in public and private hospitals, required to implement the directions of the Hon'ble Supreme Court and suitable instructions be issued to the District and Hospital Level Committees, to make periodical inspection, as stated supra, and submit a report to both respondents 1 and 2. Defects pointed out by the respective Committees be addressed and rectified by the health institutions in public and private sector and appropriate action be taken, in the event of failure to follow the directions of the Hon'ble Supreme Court, and orders issued by the governemnt, action to be taken, as per the rules.
Though the issue, regarding washing of linen discarded or not, as per the definition of Bio Medical Waste Management, Rules 1988, is stated to be Page No.37 of 40 http://www.judis.nic.in W.P. No.43370/2016 pending before the National Green Tribunal. Power of the High Court under Article 226 of the Constitution of India, cannot be restricted.
29. Thus, we issue the above directions and accordingly the writ petition is disposed of. No costs. Consequently connected miscellaneous petitions are also closed.
[S.M.K., J] [S.P., J]
05.08.2019
Index : Yes
Internet : Yes
dpq/asr
Page No.38 of 40
http://www.judis.nic.in
W.P. No.43370/2016
S.MANIKUMAR, J.
&
SUBRAMONIUM PRASAD.,J.
dpq/asr
To
1. The State of Tamil Nadu,
Rep.by its Secretary,
Health & Family Welfare Department,
Fort.St.George,
Chennai 600 009.
2. Tamil Nadu Pollution Control Board,
By its Member Secretary,
76, Mount Salai,
Guindy, Chennai 600 032.
3. The Union of India,
Rep.by its Secretary,
Ministry of Environment, Forest & Climate Change, New Delhi.
Writ Petition No.43370 of 2016 and W.M.P.No.37228 of 2016 Page No.39 of 40 http://www.judis.nic.in


CHECK-REGEXP(1) User Commands CHECK-REGEXP(1) NAME check-regexp - test regular expressions from the command line SYNOPSIS check-regexp 'regular expression' 'string1' 'string2' ... DESCRIPTION check-regexp (GNU Source-highlight) You simply pass as the first command line argument the regular expression and then the strings you want to try to match. It is crucial, in order to avoid shell substitutions, to enclose both the expression and the strings in single quotes. The program then prints some information about the possibly successful matching. In the output the what[0] part represents the whole match, and the what[i] part represents the i-th marked subexpression that matched. The program also prints possible prefix and suffix. OPTIONS This program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below. -h, --help Print help and exit -V, --version Print version and exit AUTHOR check-regexp was written by Lorenzo Bettini <www.lorenzobettini.it>. This man page was written by Cesare Tirabassi<EMAIL_ADDRESS>check-regexp 2.9 June 2008 CHECK-REGEXP(1)


Full AccreditationB.Sc Engineering Degree Program conducted by Department of Civil and Environmental Engineering (DCEE), University of Ruhuna, was granted unconditional “Full Accreditation”. Read more.. |
ACEPS - 2018The 6th International Symposium on, Advances in Civil and Environmental Engineering Practices, for Sustainable Development (ACEPS-2018), was held on 15 th March 2018 at the Faculty of Engineering, University of Ruhuna, Galle. Read more..
|
|
National Spaghetti Bridge Competition 2016University of Ruhuna became the WinnersNational Spaghetti Bridge competition 2016, organized by IESL YMS and CES of University of Peradeniya took place on the second day of TECHNO 2016, held at BMICH premises. Read more.. |
Concrete Mix Design Competition - 2016University of Ruhuna won the 1st place with 85 MpaFinal Year undergraduate student of the Department of Civil and Environmental Engineering, University of Ruhuna won the 1st place with 85 Mpa. Read more... |
|
Derana TV Programme on ACEPS - 2018 The 6th International Symposium on, Advances in Civil and Environmental Engineering Practices, for Sustainable Development (ACEPS-2018) was held on 15 th March 2018 at the Faculty of Engineering, University of Ruhuna, Galle. |
Techno Exhibition - Sphagetti Bridge Competion - 2016 Techno Exhibition 2016 was held on 7, 8 & 9th October at BMICH. The Spaghetti Bridge competition wason 9th October in the Techno Exhibition 2016. Read more. |
|
Job fair November 7th - (Organized By CEES) We are pleased to inform you that the Civil and Environmental Engineering Society (CEES) of Faculty of Engineering, University of Ruhuna has decided to host Job Fair 2017. Read more..
|
The Annual Shramadana Campaign - (Organized By CEES) The Annual Shramadana Campaign on cleaning the galle fort area will be conducted on the 1st week of December. |


--- layout: page title: Search in the Blog description: "Search this site" permalink: /search/ type: page tipue_search_active: true exclude_from_search: true icon: search # See here for a complete list of awesome icons .http://fontawesome.io/3.2.1/icons/ ---


Vdmc Demo
button
unelevated button
raised button
outlined button
dense button
link button
Title
Body goes here.
Action
This is a chip.
Selected.


R/utils.R
subset_input.Rd
An inputted matrix or 3-dimensional array is first subsetted - by rownames - to remove those subjects who are not in `id2keep`. After that, the object's rows are ordered to match the ordering of subject ids in the vector `id2keep`. This (possibly reordered) object is returned.
subset_input(input, id2keep)
| input | a matrix of either phenotypes or covariates or array of allele probabilities |
|---|---|
| id2keep | a character vector of subject ids to identify those subjects that are shared by all inputs |
an object resulting from subsetting of `input`. Its rows are ordered per `id2keep`
# define s_id s_id <- paste0("s", 1:10) # set up input matrix foo <- matrix(data = rnorm(10 * 3), nrow = 10, ncol = 3) rownames(foo) <- s_id subset_input(input = foo, id2keep = s_id)#> [,1] [,2] [,3] #> s1 -1.34074797 -2.16814685 0.4169224 #> s2 -2.19271124 -0.91754935 -2.2745533 #> s3 1.56809186 0.10268885 -1.2683205 #> s4 -0.03514251 0.07783576 0.6346674 #> s5 1.55185708 -0.54841718 0.2799669 #> s6 -0.63760140 2.20743416 1.1000911 #> s7 -0.98548753 0.31547913 0.6364982 #> s8 -2.10558882 0.03216748 0.8395000 #> s9 -0.04354969 0.15585690 -0.3503503 #> s10 0.90456079 -1.62969131 1.1048359


Sorry, no livestreamed matches at the moment
Go watch some CS:GO on
Azubu
Hitbox
Twitch
MLG
(You have to actually click CS:GO, sorry)
or do like the silvers and check
reddit
Live, streamed matches
Other streams that might be matches


; it falls off rapidly with distance from the Sun and has shrunk to about
at an elongation of .
As already described, the annual aberration is a function of the Earth's velocity relative to the solar system barycentre (available through the SLALIB routine sla_EVP) and produces shifts of up to about .
The precession/nutation, from J2000 to the current epoch, is expressed by a rotation matrix which is available through the SLALIB routine sla_PRENUT.
The whole mean-to-apparent transformation can be done using the SLALIB routine sla_MAP. As a demonstration, here is a program which lists the North Polar Distance () of Polaris for the decade of closest approach to the Pole:
IMPLICIT NONE DOUBLE PRECISION PI,PIBY2,D2R,S2R,AS2R PARAMETER (PI=3.141592653589793238462643D0) PARAMETER (D2R=PI/180D0, : PIBY2=PI/2D0, : S2R=PI/(12D0*3600D0), : AS2R=PI/(180D0*3600D0)) DOUBLE PRECISION RM,DM,PR,PD,DATE,RA,DA INTEGER J,IDS,IDE,ID,IYMDF(4),I DOUBLE PRECISION sla_EPJ2D CALL sla_DTF2R(02,31,49.8131D0,RM,J) CALL sla_DAF2R(89,15,50.661D0,DM,J) PR=+21.7272D0*S2R/100D0 PD=-1.571D0*AS2R/100D0 WRITE (*,'(1X,'// : '''Polaris north polar distance (deg) 2096-2105''/)') WRITE (*,'(4X,''Date'',7X''NPD''/)') CALL sla_CLDJ(2096,1,1,DATE,J) IDS=NINT(DATE) CALL sla_CLDJ(2105,12,31,DATE,J) IDE=NINT(DATE) DO ID=IDS,IDE,10 DATE=DBLE(ID) CALL sla_DJCAL(0,DATE,IYMDF,J) CALL sla_MAP(RM,DM,PR,PD,0D0,0D0,2000D0,DATE,RA,DA) WRITE (*,'(1X,I4,2I3.2,F9.5)') (IYMDF(I),I=1,3),(PIBY2-DA)/D2R END DO END
For cases where the transformation has to be repeated for different times or for more than one star, the straightforward sla_MAP approach is apt to be wasteful as both the Earth velocity and the precession/nutation matrix can be re-calculated relatively infrequently without ill effect. A more efficient method is to perform the target-independent calculations only when necessary, by calling sla_MAPPA, and then to use either sla_MAPQKZ, when only the is known, or sla_MAPQK, when full catalogue positions, including proper motion, parallax and radial velocity, are available. How frequently to call sla_MAPPA depends on the accuracy objectives; once per night will deliver sub-arcsecond accuracy for example.
The routines sla_AMP and sla_AMPQK allow the reverse transformation, from apparent to mean place.
SLALIB --- Positional Astronomy Library


This is a basic demo of a
SWI-Prolog
shell based on SWI-Prolog compiled to
WASM
Alpha version. See
Wiki on Discourse
for status and usage
Next
Stop
?-
Abort
🗑
+
Create
(Re)consult


Penn
Course
Grapher
Departments at Penn
Clicking on a bubble will take you to the course page for that department
CourseGrapher requires Flash


Feature the star of your collection first.
To get started, replace the image above with a striking product photo to catch people's attention.
Then, describe what makes your product unique, useful, or gift-worthy. Be sure to highlight the main features, and let people know where it's available.
|


 If you'd like a printable list then click here for a pdf version.
 If you'd like a printable list then click here for a pdf version.


Far Infrared Spectrometry of the Cosmic Background Radiation By John Cromwell Mather
A.B. (Swarthmore College) 1968 DISSERTATION
Submitted in partial satisfaction of the requirements for the degree of DOCTOR OF PHILOSOPHY in
Physics
in the GRADUATE DIVISION of the
UNIVERSITY OF CALIFORNIA, BERKELEY
Approved:
\ Food daa
i ‘ Tr Ey peeroesave ep ge eee
Committee in Charge
etpreeouvuevnaaeeseaeateho eevee eeewmesetoeeoeeeeeeeaneee
Reproduced with permission of the copyright owner. Further reproduction prohibited without permission.


This file is part of ExtendTube. It will be injected on most YouTube pages. Version: 1.13 Copyright: Darko Pantić, 2010-2012 License: Apache License, Version 2.0 Source: xtt.js, line 16


Tutorial: Attributes and omitting tags
In the fourth tutorial instalment we shall look at how to manipulate the attributes of a markup element. We shall also see an advanced scenario for omitting the start/end tags for an element, whilst preserving its content & descendents.
tal:attributes
adds, removes & updates attributes
Let's try a change to our model, and some additional markup. As in the previous tutorial page, the full model/markup is omitted for brevity, only the new content is shown. Make the changes shown below to your model & template markup and then render them.
New model values
{
UrlOne = "http://example.com/",
UrlTwo = "",
UrlThree = null,
}
New markup

This will have an 'href' attribute added

This will have an 'href' attribute updated

This will have an 'href' attribute set to empty string

This will have its 'href' attribute removed

What we learned
- A
tal:attributes
attribute value has two parts: an attribute name (which thetal:attributes
-attribute will work upon) followed by a space and then an expression - If the named attribute does not already exist on the element and the expression result is not-null, then the attribute will be added with a value equal to expression result
- If the named attribute already exists on the element and the expression result is not-null, then the attribute value will be updated to the expression result
- If the named attribute already exists on the element and the expression result is null, then the attribute will be removed from the element entirely
- As an aside, if the attribute does not already exist on the element and the expression result is null, then it will not be added
You can specify multiple attribute/expression pairs
One other aspect of a tal:attributes
attribute worth noting is that a single attributes-attribute may name as many attribute/expression pairs as it needs.
Each pair of attribute-name and value expression must be separated with a semicolon character.
Each named attribute will be handled separately, so a single tal:attributes
attribute could plausibly perform a mixture of adding, updating and also removing attributes.
Example
The following markup will add a class
attribute with a value of "external_link" and also update the href attribute value to "http://example.com/".
The whitespace inside the tal:attributes
attribute value, putting each new attribute on a new line is only for readability, it has no effect upon ZptSharp's interpretation of the template.
This is a sample hyperlink
Omitting element tags
Sometimes, there is a desire to make use of a feature such as tal:repeat
or tal:define
at a position where you do not wish to write a markup element.
Because ZPT makes use of markup attributes for its processing instructions, each instruction requires an element.
This problem can be solved by use of the tal:omit-tag
attribute, which very simply instructs ZPT to not-render the open/close tags in the output document.
Other processing attributes upon the element are still treated normally though.
Addditionally, all of the element's descendents are unaffected.
Let's try this out; here are some model changes and some markup to try in your document.
Model values
{
SomeNames = new [] { "Jane", "Peter", "Jacques" },
}
Markup

The name

How this renders
The output markup for the example above is simply the three names, with no other markup tags surrounding them.
The tal:omit-tag
attribute ensures that the outermost span is not rendered in the output (although it is still repeated three times) and the use of tal:replace
ensures that the innermost span is not rendered either.
The tal:omit-tag
attribute will remove the start & end tags for the element upon which it appears.
It is commonly used without any value, in which case it always omits the start/end tags.
A tal:omit-tag
attribute may optionally contain an expression as its attribute value; if it does then it will omit the tag if the expression evalues to a truthy value, or it will not omit the tag if it is a falsey value.
Next: Introducing METAL macros
So far we have only made use of TAL, which binds model data to the template. In the next tutorial page we will take our first look at METAL, which is for declaring and consuming reusable sections of markup.


Abs Rope Crunch Reverse Crunch Parallel bar leg raise (knee ups) I always practice Abs 2 or 3 times each week.


This tool was created using the official EVE Online API and Karbowiak's Project Rena for the backend and a custom website for the frontend.
By...
Vincent Eneticum
Feature requests as well as ingame donations are appreciated.
EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. CCP hf. has granted permission to eve.eneticum.de to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, eve.eneticum.de. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.


All aggrieved contractors welcome.
Economy got you down? Look no further.
Being harassed by someone other than your lawyer? We can help.


Geometric Figures
Javascript workshop
Calculate area and perimeter of a aquare
Type Side size
Calculate Perimeter
Calculate Area


Issue 1:
This is the dojo AMD loader(require) async test.
Click on "test require success" button to test require success.
Click on "test require error" button to test require error and process
require error.
Click on "test require
error" button again, the console output nothing, but the expect is
output error again like before.
Issue 2:
This is the dojo AMD loader(require) sync test. Please
modify dojoConfig.async=false first.
Click on "test require
sync success" button to test require plugin success.
Click on
"test require sync error" button to test require plugin error and
process require error.
You can see the
404 Not Found error and catch in require output.
This error is
catched in catch statement, but not trigger require.on("error"). Not
sure this is a defect of dojo AMD loader, but seems an error should
trigger require.on("error")
Issue 3:
This is the dojo AMD loader plugin(dojo/text) test.
Click on "test require plugin success" button to test require plugin
success.
Click on "test require plugin error" button to test
require plugin error and process require error.
You can see xhr plugin throw Unable to load
./requireerror.html status:404 error, but require.on("error") not be
triggered as expect.
In fact, require.on("error") is triggered
by "timeout" error event after 30 seconds.
Issue 4:
require not exist module test.
This
test is the same as issue 1. require a not exist module more than one
times will cause the require waiting list increament, and each new
require will check the waiting list. If the waiting list is too big,
the require perform is very low. Click on "100", "1000", "10000" and
"100000" button to test. You can see require a not exist module 10000
times is cannot tolerant, the browser almost crush when require
100000 times.


FieldNames
fileName - the name of an open
database file (local or remote).
layoutName - the name of a
layout or
table in the specified database file.
If no parameter is specified for fileName, FileMaker returns results for the current file.
Note If FieldNames returns a question mark (?) or the name of only one field, go to the Specify Calculation dialog box and make sure
Calculation result is text. Also, you can increase the size of the field on the layout to show more field names.
FieldNames(“Customers”;””) returns a list of all the fields in the default table of the Customers database file.
FieldNames(“Customers”;“Data Entry”) returns a list of all the fields, including related fields, in the Customers database file that appear on the Data Entry layout.


Class: Aws::KMS::Types::CreateKeyRequest
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Struct
|
|
|
Instance Chain:
self,
::Aws::Structure ,
Struct
|
|
| Inherits: |
Struct
|
| Defined in: | gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb |
Overview
Constant Summary
Instance Attribute Summary
-
#bypass_policy_lockout_safety_check ⇒ Boolean
rw
Skips ("bypasses") the key policy lockout safety check.
-
#custom_key_store_id ⇒ String
rw
Creates the
::Aws::KMS
key in the specified [custom key store][1]. -
#customer_master_key_spec ⇒ String
rw
Instead, use the
KeySpec
parameter. -
#description ⇒ String
rw
A description of the
::Aws::KMS
key. -
#key_spec ⇒ String
rw
Specifies the type of
::Aws::KMS
key to create. -
#key_usage ⇒ String
rw
Determines the [cryptographic operations][1] for which you can use the
::Aws::KMS
key. -
#multi_region ⇒ Boolean
rw
Creates a multi-Region primary key that you can replicate into other Amazon Web Services Regions.
-
#origin ⇒ String
rw
The source of the key material for the
::Aws::KMS
key. -
#policy ⇒ String
rw
The key policy to attach to the
::Aws::KMS
key. -
#tags ⇒ Array<Types::Tag>
rw
Assigns one or more tags to the
::Aws::KMS
key. -
#xks_key_id ⇒ String
rw
Identifies the [external key][1] that serves as key material for the
::Aws::KMS
key in an [external key store][2].
Instance Method Summary
::Aws::Structure
- Included
| #to_hash | Alias for Structure#to_h. |
Instance Attribute Details
#bypass_policy_lockout_safety_check ⇒ Boolean
(rw)
Skips ("bypasses") the key policy lockout safety check. The default value is false.
Setting this value to true increases the risk that the ::Aws::KMS
key
becomes unmanageable. Do not set this value to true
indiscriminately.
For more information, see Default key policy in the Key Management Service Developer Guide.
Use this parameter only when you intend to prevent the principal
that is making the request from making a subsequent PutKeyPolicy
request on the ::Aws::KMS
key.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#custom_key_store_id ⇒ String
(rw)
Creates the ::Aws::KMS
key in the specified custom key store. The
ConnectionState
of the custom key store must be CONNECTED
. To
find the CustomKeyStoreID and ConnectionState use the
DescribeCustomKeyStores operation.
This parameter is valid only for symmetric encryption ::Aws::KMS
keys in a
single Region. You cannot create any other type of ::Aws::KMS
key in a
custom key store.
When you create a ::Aws::KMS
key in an ::Aws::CloudHSM
key store, ::Aws::KMS
generates a
non-exportable 256-bit symmetric key in its associated ::Aws::CloudHSM
cluster and associates it with the ::Aws::KMS
key. When you create a ::Aws::KMS
key in an external key store, you must use the XksKeyId
parameter
to specify an external key that serves as key material for the ::Aws::KMS
key.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#customer_master_key_spec ⇒ String
(rw)
Instead, use the KeySpec
parameter.
The KeySpec
and CustomerMasterKeySpec
parameters work the same
way. Only the names differ. We recommend that you use KeySpec
parameter in your code. However, to avoid breaking changes, ::Aws::KMS
supports both parameters.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#description ⇒ String
(rw)
A description of the ::Aws::KMS
key.  The default
value is an empty string (no description).
Do not include confidential or sensitive information in this field.
This field may be displayed in plaintext in ::Aws::CloudTrail
logs and
other output.
To set or change the description after the key is created, use UpdateKeyDescription.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#key_spec ⇒ String
(rw)
Specifies the type of ::Aws::KMS
key to create. The default value,
SYMMETRIC_DEFAULT
, creates a ::Aws::KMS
key with a 256-bit AES-GCM key
that is used for encryption and decryption, except in China Regions,
where it creates a 128-bit symmetric key that uses SM4 encryption.
For help choosing a key spec for your ::Aws::KMS
key, see Choosing a ::Aws::KMS
key type in the Key Management Service Developer
Guide .
The KeySpec
determines whether the ::Aws::KMS
key contains a symmetric
key or an asymmetric key pair. It also determines the algorithms
that the ::Aws::KMS
key supports. You can't change the KeySpec
after the
::Aws::KMS
key is created. To further restrict the algorithms that can be
used with the ::Aws::KMS
key, use a condition key in its key policy or ::Aws::IAM
policy. For more information, see kms:EncryptionAlgorithm,
kms:MacAlgorithm or kms:Signing Algorithm in the
Key Management Service Developer Guide .
Amazon Web Services services that are integrated with KMS use
symmetric encryption ::Aws::KMS
keys to protect your data. These services
do not support asymmetric ::Aws::KMS
keys or HMAC KMS keys.
::Aws::KMS
supports the following key specs for ::Aws::KMS
keys:
Symmetric encryption key (default)
SYMMETRIC_DEFAULT
^
HMAC keys (symmetric)
HMAC_224
HMAC_256
HMAC_384
HMAC_512
Asymmetric RSA key pairs
RSA_2048
RSA_3072
RSA_4096
Asymmetric NIST-recommended elliptic curve key pairs
ECC_NIST_P256
(secp256r1)ECC_NIST_P384
(secp384r1)ECC_NIST_P521
(secp521r1)
Other asymmetric elliptic curve key pairs
ECC_SECG_P256K1
(secp256k1), commonly used for cryptocurrencies.
^
SM2 key pairs (China Regions only)
SM2
^
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#key_usage ⇒ String
(rw)
Determines the cryptographic operations for which you can use
the ::Aws::KMS
key. The default value is ENCRYPT_DECRYPT
. This parameter
is optional when you are creating a symmetric encryption ::Aws::KMS
key;
otherwise, it is required. You can't change the KeyUsage
value
after the ::Aws::KMS
key is created.
Select only one valid value.
For symmetric encryption
::Aws::KMS
keys, omit the parameter or specifyENCRYPT_DECRYPT
.For HMAC
::Aws::KMS
keys (symmetric), specifyGENERATE_VERIFY_MAC
.For asymmetric
::Aws::KMS
keys with RSA key material, specifyENCRYPT_DECRYPT
orSIGN_VERIFY
.For asymmetric
::Aws::KMS
keys with ECC key material, specifySIGN_VERIFY
.For asymmetric
::Aws::KMS
keys with SM2 key material (China Regions only), specifyENCRYPT_DECRYPT
orSIGN_VERIFY
.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#multi_region ⇒ Boolean
(rw)
Creates a multi-Region primary key that you can replicate into other
Amazon Web Services Regions. You cannot change this value after you
create the ::Aws::KMS
key.
For a multi-Region key, set this parameter to True
. For a
single-Region ::Aws::KMS
key, omit this parameter or set it to False
. The
default value is False
.
This operation supports multi-Region keys, an ::Aws::KMS
feature that
lets you create multiple interoperable ::Aws::KMS
keys in different Amazon
Web Services Regions. Because these ::Aws::KMS
keys have the same key ID,
key material, and other metadata, you can use them interchangeably
to encrypt data in one Amazon Web Services Region and decrypt it in
a different Amazon Web Services Region without re-encrypting the
data or making a cross-Region call. For more information about
multi-Region keys, see Multi-Region keys in KMS in the Key
Management Service Developer Guide.
This value creates a primary key, not a replica. To create a replica key, use the ReplicateKey operation.
You can create a symmetric or asymmetric multi-Region key, and you can create a multi-Region key with imported key material. However, you cannot create a multi-Region key in a custom key store.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#origin ⇒ String
(rw)
The source of the key material for the ::Aws::KMS
key. You cannot change
the origin after you create the ::Aws::KMS
key. The default is AWS_KMS
,
which means that ::Aws::KMS
creates the key material.
To create a ::Aws::KMS
key with no key material (for imported key
material), set this value to EXTERNAL
. For more information about
importing key material into ::Aws::KMS
, see Importing Key Material in
the Key Management Service Developer Guide. The EXTERNAL
origin
value is valid only for symmetric ::Aws::KMS
keys.
To create a ::Aws::KMS
key in an ::Aws::CloudHSM
key store and create its key
material in the associated ::Aws::CloudHSM
cluster, set this value to
AWS_CLOUDHSM
. You must also use the CustomKeyStoreId
parameter
to identify the ::Aws::CloudHSM
key store. The KeySpec
value must be
SYMMETRIC_DEFAULT
.
To create a ::Aws::KMS
key in an external key store, set this value to
EXTERNAL_KEY_STORE
. You must also use the CustomKeyStoreId
parameter to identify the external key store and the XksKeyId
parameter to identify the associated external key. The KeySpec
value must be SYMMETRIC_DEFAULT
.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#policy ⇒ String
(rw)
The key policy to attach to the ::Aws::KMS
key.
If you provide a key policy, it must meet the following criteria:
The key policy must allow the calling principal to make a subsequent
PutKeyPolicy
request on the KMS key. This reduces the risk that the KMS key becomes unmanageable. For more information, see Default key policy in the Key Management Service Developer Guide. (To omit this condition, setBypassPolicyLockoutSafetyCheck
to true.)Each statement in the key policy must contain one or more principals. The principals in the key policy must exist and be visible to KMS. When you create a new Amazon Web Services principal, you might need to enforce a delay before including the new principal in a key policy because the new principal might not be immediately visible to KMS. For more information, see Changes that I make are not always immediately visible in the Amazon Web Services Identity and Access Management User Guide.
If you do not provide a key policy, ::Aws::KMS
attaches a default key
policy to the ::Aws::KMS
key. For more information, see Default key
policy in the Key Management Service Developer Guide.
The key policy size quota is 32 kilobytes (32768 bytes).
For help writing and formatting a JSON policy document, see the IAM JSON Policy Reference in the Identity and Access Management User Guide .
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#tags ⇒ Array
<Types::Tag> (rw)
Assigns one or more tags to the ::Aws::KMS
key. Use this parameter to tag
the ::Aws::KMS
key when it is created. To tag an existing ::Aws::KMS
key, use the
TagResource operation.
Do not include confidential or sensitive information in this field.
This field may be displayed in plaintext in ::Aws::CloudTrail
logs and
other output.
::Aws::KMS
key can allow or deny permission to the
::Aws::KMS
key. For details, see ABAC for KMS in the Key Management
Service Developer Guide.
To use this parameter, you must have kms:TagResource permission
in an ::Aws::IAM
policy.
Each tag consists of a tag key and a tag value. Both the tag key and
the tag value are required, but the tag value can be an empty (null)
string. You cannot have more than one tag on a ::Aws::KMS
key with the same
tag key. If you specify an existing tag key with a different tag
value, ::Aws::KMS
replaces the current tag value with the specified one.
When you add tags to an Amazon Web Services resource, Amazon Web
Services generates a cost allocation report with usage and costs
aggregated by tags. Tags can also be used to control access to a ::Aws::KMS
key. For details, see Tagging Keys.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end
#xks_key_id ⇒ String
(rw)
Identifies the external key that serves as key material for the
::Aws::KMS
key in an external key store. Specify the ID that the
external key store proxy uses to refer to the external key. For
help, see the documentation for your external key store proxy.
This parameter is required for a ::Aws::KMS
key with an Origin
value of
EXTERNAL_KEY_STORE
. It is not valid for ::Aws::KMS
keys with any other
Origin
value.
The external key must be an existing 256-bit AES symmetric
encryption key hosted outside of Amazon Web Services in an external
key manager associated with the external key store specified by the
CustomKeyStoreId
parameter. This key must be enabled and
configured to perform encryption and decryption. Each KMS key in an
external key store must use a different external key. For details,
see Requirements for a ::Aws::KMS
key in an external key store in the
Key Management Service Developer Guide.
Each KMS key in an external key store is associated two backing
keys. One is key material that ::Aws::KMS
generates. The other is the
external key specified by this parameter. When you use the ::Aws::KMS
key
in an external key store to encrypt data, the encryption operation
is performed first by ::Aws::KMS
using the ::Aws::KMS
key material, and then by
the external key manager using the specified external key, a process
known as double encryption. For details, see Double
encryption in the Key Management Service Developer Guide.
# File 'gems/aws-sdk-kms/lib/aws-sdk-kms/types.rb', line 1109
class CreateKeyRequest < Struct.new( :policy, :description, :key_usage, :customer_master_key_spec, :key_spec, :origin, :custom_key_store_id, :bypass_policy_lockout_safety_check, :, :multi_region, :xks_key_id) SENSITIVE = [] include Aws::Structure end


SEEK is developed as not only an Open source project, but also an Open development project. We welcome contributions of all kinds, whether it is source code, improvement suggestions or bug reports. We are always grateful of any contribution regardless of its size.
If you wish to do some development work on SEEK - following our basic Installation Guide will set up everything you need, including the latest stable source code.
If you have never used Ruby or Ruby on Rails, we strongly suggest you read through the documentation at rubyonrails.org/documentation. There are also many tutorials available online.
You can contact us through our developers mailing list at groups.google.com/group/seek-developers . We particularly encourage you to contact us before you start on adding a new feature, as it maybe something that we have already put some thought into or have in our pipeline.
Our main source code repository can be found at bitbucket.org/seek4science/seek . You can fork or clone this project before making changes to it, and then make your changes available to us either with patch files or by pointing us at your cloned repository.


Welcome
to The Marathon Pizza Shop.
Here you will get the best pizza you've ever had unless you are a returning customer. Life is a marathon and to succeed
in running through it you need good fuel.


OASIS
OASIS API dissolves the complexity of blockchain and making NFT minting possible in muliplte chains like ETHEREUM, Polygon and all layer-2 ERC-721 standards, SOLANA SPL standard NFT's
All made possible with simple HTTP request
OASIS API dissolves the complexity of blockchain and making NFT minting possible in muliplte chains like ETHEREUM, Polygon and all layer-2 ERC-721 standards, SOLANA SPL standard NFT's
All made possible with simple HTTP request


The examples in this section use intracommunicators.
Example
Gather 100 ints from every process in group to root. See
Figure 4
.
MPI_Comm comm; int gsize,sendarray[100]; int root, *rbuf; ... MPI_Comm_size(comm, &gsize); rbuf = (int *)malloc(gsize*100*sizeof(int)); MPI_Gather(sendarray, 100, MPI_INT, rbuf, 100, MPI_INT, root, comm);
Example
Previous example modified --- only the root allocates memory for the
receive buffer.
MPI_Comm comm; int gsize,sendarray[100]; int root, myrank, *rbuf; ... MPI_Comm_rank(comm, &myrank); if (myrank == root) { MPI_Comm_size(comm, &gsize); rbuf = (int *)malloc(gsize*100*sizeof(int)); } MPI_Gather(sendarray, 100, MPI_INT, rbuf, 100, MPI_INT, root, comm);
Example
Do the same as the previous example, but use a derived datatype. Note that
the type cannot be the entire set of gsize*100 ints since type matching
is defined pairwise between the root and each process in the gather.
MPI_Comm comm; int gsize,sendarray[100]; int root, *rbuf; MPI_Datatype rtype; ... MPI_Comm_size(comm, &gsize); MPI_Type_contiguous(100, MPI_INT, &rtype); MPI_Type_commit(&rtype); rbuf = (int *)malloc(gsize*100*sizeof(int)); MPI_Gather(sendarray, 100, MPI_INT, rbuf, 1, rtype, root, comm);
Example
Now have each process send 100 ints to root, but place each set (of 100)
stride ints apart at receiving end. Use MPI_GATHERV
and the displs
argument to achieve this effect. Assume
.
See Figure 5
.
MPI_Comm comm; int gsize,sendarray[100]; int root, *rbuf, stride; int *displs,i,*rcounts; ... MPI_Comm_size(comm, &gsize); rbuf = (int *)malloc(gsize*stride*sizeof(int)); displs = (int *)malloc(gsize*sizeof(int)); rcounts = (int *)malloc(gsize*sizeof(int)); for (i=0; i<gsize; ++i) { displs[i] = i*stride; rcounts[i] = 100; } MPI_Gatherv(sendarray, 100, MPI_INT, rbuf, rcounts, displs, MPI_INT, root, comm);Note that the program is erroneous if stride < 100.
Example
Same as Example Examples using MPI_GATHER, MPI_GATHERV
on the receiving side, but send the
100 ints from the 0th column of a
100×150 int array, in C. See Figure 6
.
MPI_Comm comm; int gsize,sendarray[100][150]; int root, *rbuf, stride; MPI_Datatype stype; int *displs,i,*rcounts; ... MPI_Comm_size(comm, &gsize); rbuf = (int *)malloc(gsize*stride*sizeof(int)); displs = (int *)malloc(gsize*sizeof(int)); rcounts = (int *)malloc(gsize*sizeof(int)); for (i=0; i<gsize; ++i) { displs[i] = i*stride; rcounts[i] = 100; } /* Create datatype for 1 column of array */ MPI_Type_vector(100, 1, 150, MPI_INT, &stype); MPI_Type_commit(&stype); MPI_Gatherv(sendarray, 1, stype, rbuf, rcounts, displs, MPI_INT, root, comm);
Example
Process i sends (100-i) ints from the i-th column of a
100 × 150 int array, in C. It is received into a buffer with stride,
as in the previous two examples. See Figure 7
.
MPI_Comm comm; int gsize,sendarray[100][150],*sptr; int root, *rbuf, stride, myrank; MPI_Datatype stype; int *displs,i,*rcounts; ... MPI_Comm_size(comm, &gsize); MPI_Comm_rank(comm, &myrank); rbuf = (int *)malloc(gsize*stride*sizeof(int)); displs = (int *)malloc(gsize*sizeof(int)); rcounts = (int *)malloc(gsize*sizeof(int)); for (i=0; i<gsize; ++i) { displs[i] = i*stride; rcounts[i] = 100-i; /* note change from previous example */ } /* Create datatype for the column we are sending */ MPI_Type_vector(100-myrank, 1, 150, MPI_INT, &stype); MPI_Type_commit(&stype); /* sptr is the address of start of "myrank" column */ sptr = &sendarray[0][myrank]; MPI_Gatherv(sptr, 1, stype, rbuf, rcounts, displs, MPI_INT, root, comm);Note that a different amount of data is received from each process.
Example
Same as Example Examples using MPI_GATHER, MPI_GATHERV
, but done in a different way at the sending end.
We create a datatype that causes the correct striding at the
sending end so
that
we read a column of a C array.
A similar thing was done in Example Examples
,
Section Examples
.
MPI_Comm comm; int gsize, sendarray[100][150], *sptr; int root, *rbuf, stride, myrank; MPI_Datatype stype; int *displs, i, *rcounts; ... MPI_Comm_size(comm, &gsize); MPI_Comm_rank(comm, &myrank); rbuf = (int *)malloc(gsize*stride*sizeof(int)); displs = (int *)malloc(gsize*sizeof(int)); rcounts = (int *)malloc(gsize*sizeof(int)); for (i=0; i<gsize; ++i) { displs[i] = i*stride; rcounts[i] = 100-i; } /* Create datatype for one int, with extent of entire row */ MPI_Type_create_resized( MPI_INT, 0, 150*sizeof(int), &stype); MPI_Type_commit(&stype); sptr = &sendarray[0][myrank]; MPI_Gatherv(sptr, 100-myrank, stype, rbuf, rcounts, displs, MPI_INT, root, comm);
Example
Same as Example Examples using MPI_GATHER, MPI_GATHERV
at sending side, but
at receiving side we make the
stride between received blocks vary from block to block.
See Figure 8
.
MPI_Comm comm; int gsize,sendarray[100][150],*sptr; int root, *rbuf, *stride, myrank, bufsize; MPI_Datatype stype; int *displs,i,*rcounts,offset; ... MPI_Comm_size(comm, &gsize); MPI_Comm_rank(comm, &myrank); stride = (int *)malloc(gsize*sizeof(int)); ... /* stride[i] for i = 0 to gsize-1 is set somehow */ /* set up displs and rcounts vectors first */ displs = (int *)malloc(gsize*sizeof(int)); rcounts = (int *)malloc(gsize*sizeof(int)); offset = 0; for (i=0; i<gsize; ++i) { displs[i] = offset; offset += stride[i]; rcounts[i] = 100-i; } /* the required buffer size for rbuf is now easily obtained */ bufsize = displs[gsize-1]+rcounts[gsize-1]; rbuf = (int *)malloc(bufsize*sizeof(int)); /* Create datatype for the column we are sending */ MPI_Type_vector(100-myrank, 1, 150, MPI_INT, &stype); MPI_Type_commit(&stype); sptr = &sendarray[0][myrank]; MPI_Gatherv(sptr, 1, stype, rbuf, rcounts, displs, MPI_INT, root, comm);
Example
Process i sends num ints from the i-th column of a
100 × 150 int array, in C. The complicating factor is that
the various values of num are not known to root, so a
separate gather must first be run to find these out. The data is
placed contiguously at the receiving end.
MPI_Comm comm; int gsize,sendarray[100][150],*sptr; int root, *rbuf, myrank; MPI_Datatype stype; int *displs,i,*rcounts,num; ... MPI_Comm_size(comm, &gsize); MPI_Comm_rank(comm, &myrank); /* First, gather nums to root */ rcounts = (int *)malloc(gsize*sizeof(int)); MPI_Gather(&num, 1, MPI_INT, rcounts, 1, MPI_INT, root, comm); /* root now has correct rcounts, using these we set displs[] so * that data is placed contiguously (or concatenated) at receive end */ displs = (int *)malloc(gsize*sizeof(int)); displs[0] = 0; for (i=1; i<gsize; ++i) { displs[i] = displs[i-1]+rcounts[i-1]; } /* And, create receive buffer */ rbuf = (int *)malloc(gsize*(displs[gsize-1]+rcounts[gsize-1]) *sizeof(int)); /* Create datatype for one int, with extent of entire row */ MPI_Type_create_resized( MPI_INT, 0, 150*sizeof(int), &stype); MPI_Type_commit(&stype); sptr = &sendarray[0][myrank]; MPI_Gatherv(sptr, num, stype, rbuf, rcounts, displs, MPI_INT, root, comm);


Vehicle Dynamics - Lateral: Open Source Simulation Package for MATLAB
This package is an open source initiative that provides vehicle models and graphics features for lateral dynamics simulation of simple and articulated vehicles.
Contents
Examples
To make the first steps easier, two template scripts are available covering the simulation of simple and articulated vehicles. We encourage the users to run and explore the examples TemplateSimple.m and TemplateArticulated.m.
Alternatively, for users familiar with Simulink, two template applications are available for running the models of the package in Simulink. Run and explore the examples TemplateSimpleSimulink.m and TemplateArticulatedSimulink.m.
| Name | Description |
|---|---|
| Kalman Filter - Simple vehicle | Kalman Filter application. |
| Multi-axle steering articulated | Steering all axles of an articulated vehicle. |
| Multi-axle steering simple | Steering both axles of a simple vehicle. |
| OpenLoop Steering Articulated | Articulated vehicle maneuver with sinusoidal open-loop steering angle input. |
| OpenLoop Steering Simple | Simple vehicle maneuver with sinusoidal open-loop steering angle input. |
| Skid Pad Simple | Simple vehicle moving in circle. |
| Skid Pad Simple 4DOF | Simple vehicle with roll dynamics moving in circle. |
| Steering Control Simple | Double lane change maneuver. |
| Template Articulated | Articulated vehicle simulation. |
| Template Articulated Simulink | Simulate the articulated vehicle model in Simulink. |
| Template Simple | Simple vehicle simulation. |
| Template Simple Simulink | Simulate the simple vehicle model in Simulink. |
| Tire Comparison | Comparison of tire models. |
Description
The general structure of the package is illustrated below. All classes of the package are categorized into Vehicle model, Tire model and Graphics. One Vehicle model and one Tire model are combined to form the System. The integration of the System, with the apropriate parameters and initial conditions, is performed through the standard ode45 function of MATLAB®. The resulting data can be ploted as Frame and Animation with the Graphics features.
This package uses an object-oriented programming architecture. For more details see Object-Oriented Programming in MATLAB
Description page of the available models and graphics:
Tire model
Vehicle model
Graphics
Installation
The first thing you have to do is install the package according to the following steps:
API Documentation
Help and documentation on-the-fly are available through the "doc" and "help" commands, as usual. For instance, run:
help VehicleDynamicsLateral.VehicleSimpleLinear


---
layout: post
title: Tooth Paste ?
date: '2007-01-25T08:38:00.000Z'
author: tknv
tags:
modified_time: '2007-01-25T08:42:37.625Z'
thumbnail: http://4.bp.blogspot.com/_dszryEfCgyA/Rbhs8nVj5uI/AAAAAAAAAAg/zas3c-goDUY/s72-c/DSC00097.JPG
blogger_id: tag:blogger.com,1999:blog-11459759.post-7758020422170092933
blogger_orig_url: http://phichyudebow.blogspot.com/2007/01/tooth-paste.html
---
Maybe Tooth Paste...
The flavor was sweet...
at Kazakhstan Almaty


- Implemented by Apereo CAS
- JSON- or XML-based
- Backchannel required
- Suitable for all kinds of apps
Credits
Keycloak servlet filter
@Component(
immediate = true,
service = Filter.class,
property = {
CONFIG_FILE_PARAM + "=" + "keycloak.json",
SKIP_PATTERN_PARAM + "=" + "/public/.*",
HTTP_WHITEBOARD_FILTER_PATTERN + "=" + "/",
HTTP_WHITEBOARD_CONTEXT_SELECT + "="
+ "(osgi.http.whiteboard.context.name=org.apache.sling)"
})
public class KeycloakFilter extends KeycloakOIDCFilter { }
Keycloak Sling AuthenticationHandler
public class KeycloakAuthenticationHandler implements
org.apache.sling.auth.core.spi.AuthenticationHandler {
// ....
public AuthenticationInfo extractCredentials(
HttpServletRequest req, HttpServletResponse res) {
KeycloakSecurityContext ctx = (KeycloakSecurityContext)
req.getSession()
.getAttribute("org.keycloak.KeycloakSecurityContext");
return new AuthenticationInfo("KEYCLOAK",
"admin", "admin".toCharArray());
}
// ....
}
User provisioning? What is it?
User provisioning? What is it?
User provisioning? What is it?
Do I really need it?
| YES: |
NO: |
- You’re relying on the users’ existence in the underlying JCR;
- If you make heavy use of JCR ACLs.
|
- You connect the underlying DB using a service account;
- Access control is on the application level
- You’re OK to go with a single account for JCR
|
User provisioning: approaches
User provisioning: push
User provisioning: pull
User provisioning: shared store
Can I have push/pull now?
LDAP to the rescue (present)