text:
# BY-LAWS OF PREVENT HIV OKLAHOMA

## ARTICLE I. NAME

### 1.1 Name

The name of this corporation shall be Prevent HIV OK Syndicate (hereinafter, “Syndicate”). The business of the corporation may be conducted as Prevent HIV Oklahoma, Prevent HIV OK, or the acronym PHOK.

## ARTICLE II. PURPOSES AND POWERS

### 2.1 Purpose

The Syndicate is a non-profit public benefit corporation (hereinafter, “non-profit”) and shall be operated exclusively for educational and charitable purposes within the meaning of Section 501(c)(3) of the United States (hereinafter, “U.S.”) Internal Revenue Code of 1986 or the corresponding section of any future Federal tax code (hereinafter, “Tax Code”).

The Syndicate’s purpose is to address, educate, coordinate, and provide aid, and relief to human immunodeficiency virus (hereinafter, “HIV”) and sexually transmittable infections (hereinafter, “STI” or “STIs”) on a local and global level.

We utilizing social media channels and the corporation’s website to provide facts, statistics, and other related data on causes, current efforts, and solutions to eradicating HIV and STIs.

Our programs include location-based, low-cost HIV and STI testing facilities locator, medically-accurate information about HIV & STI prevention techniques, and the reduction of stigma for persons living with HIV.

To maximize our impact on current efforts, we may seek to collaborate with other non-profit organizations which fall under Section 501(c)(3) of The Tax Code.

At times, per the discretion of the managing body of the corporation (hereinafter, “Board of Directors”), we may provide internships or volunteer opportunities which shall provide opportunities for involvement in aforementioned activities and programs in order to have a greater impact for change.

### 2.2 Powers

Syndicate shall have the power, directly or indirectly, alone or in conjunction or cooperation with others, to do any and all lawful acts that may be necessary or convenient to affect the charitable purposes, for which the corporation is organized, and to aid or assist other organizations or persons whose activities further accomplish, foster, or attain such purposes.

The powers of Syndicate may include, but are not be limited to, the acceptance of contributions from the public and private sectors, whether financial or in-kind.

### 2.3 Nonprofit Status and Exempt Activities Limitation.

#### 2.3.1 Nonprofit Legal Status

Syndicate is an Oklahoma non-profit, recognized as tax exempt under Tax Code.

#### <IP_ADDRESS> Exempt Activities Limitation

Notwithstanding any other provision of these By-laws, no director, officer, employee, member, or representative of this corporation shall take any action or carry on any activity by or on behalf of the corporation not permitted to be taken or carried on by an organization exempt under Section 501(c)(3) of Tax Code as it now exists or may be amended, or by any organization contributions to which are deductible under Section 170(c)(2) of such Code and Regulations as it now exists or may be amended. No part of the net earnings of the corporation shall inure to the benefit of or be distributable to any director, officer, member, or other private person, except that the corporation shall be authorized and empowered to pay reasonable compensation for services rendered and to make payments and distributions in furtherance of the purposes set forth in the Articles of Incorporation and these By-laws.

#### <IP_ADDRESS> Distribution upon Dissolution

Upon termination or dissolution of Syndicate, any assets lawfully available for distribution shall be distributed to one (1) or more qualifying organizations described in Section 501(c)(3) of Tax Code which, at least generally, includes a purpose similar to the terminating or dissolving corporation.

The organization to receive the assets of Syndicate hereunder shall be selected at the discretion of a simple majority of Board of Directors, and if its members cannot so agree, then the recipient organization shall be selected pursuant to a verified petition in equity filed in a court of proper jurisdiction against Syndicate by one (1) or more of its Board of Directors which verified petition shall contain such statements as reasonably indicate the applicability of this section. The court, upon a finding that this section is applicable, shall select the qualifying organization or organizations to receive the assets to be distributed, giving preference, if practicable, to organizations located within the State of Oklahoma.

In the event that the court shall find that this section is applicable but that there is no qualifying organization known to it which has a charitable purpose, which, at least generally, includes a purpose similar to Syndicate, then the court shall direct the distribution of its assets lawfully available for distribution to the State Department of Health or the Oklahoma HIV and Hepatitis Policy Council, if compliant with current statutes, or, as a last resort, the Treasurer of the State of Oklahoma to be added to the general fund.

## ARTICLE III. MEMBERSHIP

### 3.1 No Membership Classes

Syndicate shall have no members who have any right to vote or title or interest in or to Syndicate, its properties and franchises.

### 3.2 Non-Voting Affiliates

Board of Directors may approve classes of non-voting affiliates with rights, privileges, and obligations established by it. Affiliates may be individuals, businesses, and other organizations that seek to support the mission of Syndicate. Board of Directors, a designated committee of Board of Directors, or any duly elected officer in accordance with Board of Directors policy, shall have authority to admit any individual or organization as an affiliate, to recognize representatives of affiliates, and to make determinations as to affiliates’ rights, privileges, and obligations. At no time shall affiliate information be shared with or sold to other organizations or groups without the affiliate’s consent. At the discretion of Board of Directors, affiliates may be given endorsement, recognition, and media coverage at fundraising activities, clinics, other events, or on Syndicate’s website or websites (hereinafter, “Website”). Affiliates have no voting rights and are not members of Syndicate.

### 3.3 Dues

Any dues for affiliates shall be determined by Board of Directors.

## ARTICLE IV. BOARD OF DIRECTORS

### 4.1 Number of Directors

The Syndicate shall have a Board of Directors consisting of at least 1, or the minimum required by State law, and no more than 15 directors. Within these limits, Board of Directors may increase or decrease the number of directors serving on Board of Directors, including for the purpose of staggering the terms of directors, and shall comprise an odd number of directors.

### 4.2 Powers

All corporate powers shall be exercised by or under the authority of Board of Directors and the affairs of Syndicate shall be managed under the direction of Board of Directors, except as otherwise provided by law.

### 4.3 Terms

#### 4.3.1 Term Length

All directors shall be elected to serve a two-year (2) term, however the term may be extended until a successor has been elected.

4.3.2 Staggering Terms

Director terms shall be staggered so that approximately half the number of directors will end their terms in any given year.

#### 4.3.3 Term Succession

Directors may serve terms in succession or perpetuity.

#### 4.3.4 Term Dates

The term of office shall be considered to begin July 1 and June 30 of the second year in office, unless the term is extended until such time as a successor has been elected. The term of the successor shall end on June 30, even if they have not completed a complete term, for the sake of simplifying and easing Board of Directors election process.

### 4.4 Qualifications and Election of Directors

In order to be eligible to serve as a director on Board of Directors, the individual must be 18 years of age, or 16 years of age, with consent of a parent, guardian, or others serving in parentis loco, and an affiliate within affiliate classifications created by Board of Directors. Directors may be elected at any board meeting by the majority vote of the existing Board of Directors. The election of directors to replace those who have fulfilled their term of office shall take place within the first week of June of each year, unless another time is selected by Board of Directors, allowing for a sufficient time for onboarding, with a simple majority vote.

### 4.5 Vacancies

Board of Directors may fill vacancies due to the expiration of a director’s term of office, resignation, death, or removal of a director or may appoint new directors to fill a previously unfilled board position, subject to the maximum number of directors under these By-laws.

#### 4.5.1 Unexpected Vacancies

Vacancies in Board of Directors due to resignation, death, or removal shall be filled by Board of Directors for the balance of the term of the director being replaced.

### 4.6 Removal of Directors

A director may be removed by two-thirds (2/3) vote of the board of directors then in office, if the director is absent and unexcused from two (2) or more mandatory meetings of Board of Directors in a twelve (12) month period or three (3) or more mandatory meetings in a two-year (2) period. The president of Board of Directors (“President”) or a simple majority vote of the executive committee (hereinafter, “Executive Committee”) is empowered to excuse directors from attendance for a reason deemed by either party. President shall not have the power to excuse themselves from Board of Director meeting attendance and, in that case, the board vice president (hereinafter, “Vice President”) shall excuse President.

For cause or no cause, if before any meeting of Board of Directors at which a vote on removal will be made, the director in question is given electronic or written notification of Board of Director’s intention to discuss their case and shall be given the opportunity to be heard at a meeting of Board of Directors. If the director in question attempts to filibuster the vote, which shall be defined by President, President shall be empowered to call for a vote, passed by a simple majority, to end the director’s opportunity to speak and the resolution shall be tabled until such a time that Board of Directors may again convene to discuss the director in question’s removal. On such an occasion, the director in question shall be given no more than ten (10) minutes to speak.

### 4.7 Board of Directors Meetings

#### 4.7.1 Regular Meetings
The board of directors shall have a minimum of four (4) regular meetings each calendar year at times and places fixed by the board. Board meetings shall be held upon four (4) days notice by first-class mail, electronic mail, or facsimile transmission or forty-eight (48) hours notice delivered personally or by telephone. If sent by mail, facsimile transmission, or electronic mail, the notice shall be deemed to be delivered upon its deposit in the mail or transmission system. Notice of meetings shall specify the place, day, and hour of meeting. The purpose of the meeting need not be specified.

#### 4.7.2 Special Meetings
Special meetings of the board may be called by President, Vice President, Secretary, Treasurer, or any two (2) other directors of Board of Directors. A special meeting must be preceded by at least three (3) days’ notice to each director of the date, time, and place, but not the purpose, of the meeting.

#### 4.7.3. Waiver of Notice
Any director may waive notice of any meeting in accordance with Oklahoma law.

### 4.8 Manner of Acting

#### 4.8.1 Quorum

A majority of the directors in office immediately before a meeting shall constitute a quorum for the transaction of business at that meeting of the board. No business shall be considered by the board at any meeting at which a quorum is not present.

#### 4.8.2 Majority Vote

Except as otherwise required by law or by the articles of incorporation, the act of the majority of the directors present at a meeting at which a quorum is present shall be the act of the board.

#### 4.8.3 Hung Board Decisions

On the occasion that Board of Directors are unable to make a decision based on a tied number of votes, President or acting President shall have the power to swing the vote based on their discretion or table the vote for further discussion at a special meeting.

#### 4.8.4 Participation

Except as otherwise required by law, Articles of Incorporation, or these By-laws, directors may participate in a regular or special meeting through the use of any means of communication by which all directors participating may simultaneously see and hear each other during the meeting, including in person or internet video meeting.

### 4.9 Compensation for Board Service

Directors shall receive no compensation for carrying out their duties as directors. The board may adopt policies providing for reasonable reimbursement of directors for expenses incurred in conjunction with carrying out board responsibilities, such as travel expenses to attend board meetings.

### 4.10 Compensation for Professional Services by Directors

Directors are not restricted from being remunerated for professional services provided to Syndicate. Such remuneration shall be reasonable and fair and must be reviewed and approved in accordance with Board of Directors’ Conflict of Interest policy and applicable State law.

## ARTICLE V. COMMITTEES

### 5.1 Committees

The board of directors may, by the resolution adopted by a majority of the directors then in office, designate one or more committees, each consisting of two or more directors, to serve at the pleasure of the board. Any committee, to the extent provided in the resolution of the board, shall have all the authority of the board, except that no committee, regardless of board resolution, may:

1. take any final action on matters which also requires board members’ approval or approval of a majority of all members;
2. fill vacancies on the board of directors of in any committee which has the authority of the board;
3. amend or repeal Bylaws or adopt new Bylaws;
4. amend or repeal any resolution of the board of directors which by its express terms is not so amendable or repealable;
5. appoint any other committees of the board of directors or the members of these committees;
6. expend corporate funds to support a nominee for director; or
7. approve any transaction;
  1. to which the corporation is a party and one or more directors have a material financial interest; or
  2. between the corporation and one or more of its directors or between the corporation or any person in which one or more of its directors have a material financial interest.

### 5.2  Meetings and Action of Committees
Meetings and action of the committees shall be governed by and held and taken in accordance with, the provisions of Article IV of these Bylaws concerning meetings of the directors, with such changes in the context of those Bylaws as are necessary to substitute the committee and its members for the board of directors and its members, except that the time for regular meetings of committees may be determined either by resolution of the board of directors or by resolution of the committee. Special meetings of the committee may also be called by resolution of the board of directors. Notice of special meetings of committees shall also be given to any and all alternate members, who shall have the right to attend all meetings of the committee. Minutes shall be kept of each meeting of any committee and shall be filed with the corporate records. The board of directors may adopt rules for the governing of the committee not inconsistent with the provision of these Bylaws.

### 5.3 Informal Action by Board of Directors
Any action required or permitted to be taken by the board of directors at a meeting may be taken without a meeting if consent in writing, setting forth the action so taken, shall be agreed by the consensus of a quorum. For purposes of this section an e-mail transmission from an e-mail address on record constitutes a valid writing. The intent of this provision is to allow the board of directors to use email to approve actions, as long as a quorum of board members gives consent.

## ARTICLE VI. OFFICERS

### 6.1 Board Officers

The officers of the corporation shall be a board president, vice-president, secretary, and treasurer, all of whom shall be chosen by, and serve at the pleasure of, the board of directors. Each board officer shall have the authority and shall perform the duties set forth in these Bylaws or by resolution of the board or by direction of an officer authorized by the board to prescribe the duties and authority of other officers. The board may also appoint additional vice-presidents and such other officers as it deems expedient for the proper conduct of the business of the corporation, each of whom shall have such authority and shall perform such duties as the board of directors may determine. One person may hold two or more board offices, but no board officer may act in more than one capacity where action of two or more officers is required.

### 6.2 Term of Office

Each officer shall serve a one-year term of office and may not serve more than three (3) consecutive terms of office. Unless unanimously elected by the board at the end of his/her three (3) year terms or to fill a vacancy in an officer position, each board officer’s term of office shall begin upon the adjournment of the board meeting at which elected and shall end upon the adjournment of the board meeting during which a successor is elected.

### 6.3 Removal and Resignation

The board of directors may remove an officer at any time, with or without cause. Any officer may resign at any time by giving written notice to the corporation without prejudice to the rights, if any, of the corporation under any contract to which the officer is a party. Any resignation shall take effect at the date of the receipt of the notice or at any later time specified in the notice, unless otherwise specified in the notice. The acceptance of the resignation shall not be necessary to make it effective.

### 6.4 President

The board president shall be the chief volunteer officer of the corporation. The board president shall lead the board of directors in performing its duties and responsibilities, including, if present, presiding at all meetings of the board of directors, and shall perform all other duties incident to the office or properly required by the board of directors.

### 6.5 Vice President

In the absence or disability of the board president, the ranking vice-president or vice-president designated by the board of directors shall perform the duties of the board president. When so acting, the vice-president shall have all the powers of and be subject to all the restrictions upon the board president. The vice-president shall have such other powers and perform such other duties prescribed for them by the board of directors or the board president. The vice-president shall normally accede to the office of board president upon the completion of the board president’s term of office.

### 6.6 Secretary

The secretary shall keep or cause to be kept a book of minutes of all meetings and actions of directors and committees of directors. The minutes of each meeting shall state the time and place that it was held and such other information as shall be necessary to determine the actions taken and whether the meeting was held in accordance with the law and these Bylaws. The secretary shall cause notice to be given of all meetings of directors and committees as required by the Bylaws. The secretary shall have such other powers and perform such other duties as may be prescribed by the board of directors or the board president. The secretary may appoint, with approval of the board, a director to assist in performance of all or part of the duties of the secretary.

### 6.7 Treasurer

The treasurer shall be the lead director for oversight of the financial condition and affairs of the corporation. The treasurer shall oversee and keep the board informed of the financial condition of the corporation and of audit or financial review results. In conjunction with other directors or officers, the treasurer shall oversee budget preparation and shall ensure that appropriate financial reports, including an account of major transactions and the financial condition of the corporation, are made available to the board of directors on a timely basis or as may be required by the board of directors. The treasurer shall perform all duties properly required by the board of directors or the board president. The treasurer may appoint, with approval of the board a qualified fiscal agent or member of the staff to assist in performance of all or part of the duties of the treasurer.

### 6.8 Non-Director Officers

The board of directors may designate additional officer positions of the corporation and may appoint and assign duties to other non-director officers of the corporation.

## ARTICLE VII. CONTRACTS, CHECKS, LOANS, INDEMNIFICATION AND RELATED MATTERS

### 7.1 Contracts and Other Writings
Except as otherwise provided by resolution of the board or board policy, all contracts, deeds, leases, mortgages, grants, and other agreements of the corporation shall be executed on its behalf by the treasurer or other persons to whom the corporation has delegated authority to execute such documents in accordance with policies approved by the board.

### 7.2 Checks and Drafts

All checks, drafts, or other orders for payment of money, notes, or other evidence of indebtedness issued in the name of the corporation, shall be signed by such officer or officers, agent or agents, of the corporation and in such manner as shall from time to time be determined by resolution of the board.

### 7.3 Deposits

All funds of the corporation not otherwise employed shall be deposited from time to time to the credit of the corporation in such banks, trust companies, or other depository as the board or a designated committee of the board may select.

### 7.4 Loans

No loans shall be contracted on behalf of the corporation and no evidence of indebtedness shall be issued in its name unless authorized by resolution of the board. Such authority may be general or confined to specific instances.

### 7.5 Indemnification

#### 7.5.1 Mandatory Indemnification

The corporation shall indemnify a director or former director, who was wholly successful, on the merits or otherwise, in the defense of any proceeding to which he or she was a party because he or she is or was a director of the corporation against reasonable expenses incurred by him or her in connection with the proceedings.

#### 7.5.2 Permissible Indemnification

The corporation shall indemnify a director or former director made a party to a proceeding because he or she is or was a director of the corporation, against liability incurred in the proceeding, if the determination to indemnify him or her has been made in the manner prescribed by the law and payment has been authorized in the manner prescribed by law.

#### 7.5.3 Advance for Expenses

Expenses incurred in defending a civil or criminal action, suit or proceeding may be paid by the corporation in advance of the final disposition of such action, suit or proceeding, as authorized by the board of directors in the specific case, upon receipt of:
  1. a written affirmation from the director, officer, employee or agent of his or her good faith belief that he or she is entitled to indemnification as authorized in this article, and
  2. an undertaking by or on behalf of the director, officer, employee or agent to repay such amount, unless it shall ultimately be determined that he or she is entitled to be indemnified by the corporation in these Bylaws.

#### 7.5.4 Indemnification of Officers, Agents, and Employees

An officer of the corporation who is not a director is entitled to mandatory indemnification under this article to the same extent as a director. The corporation may also indemnify and advance expenses to an employee or agent of the corporation who is not a director, consistent with Oklahoma Law and public policy, provided that such indemnification, and the scope of such indemnification, is set forth by the general or specific action of the board or by contract.

## ARTICLE VIII. MISCELLANEOUS

### 8.1 Books and Records

The corporation shall keep correct and complete books and records of account and shall keep minutes of the proceedings of all meetings of its board of directors, a record of all actions taken by board of directors without a meeting, and a record of all actions taken by committees of the board. In addition, the corporation shall keep a copy of the corporation’s Articles of Incorporation and Bylaws as amended to date.

### 8.2 Fiscal Year

The fiscal year of the corporation shall be from July 1 to June 30 of each year.

### 8.3 Conflict of Interest

The board shall adopt and periodically review a conflict of interest policy to protect the corporation’s interest when it is contemplating any transaction or arrangement which may benefit any director, officer, employee, affiliate, or member of a committee with board-delegated powers.

### 8.4 Nondiscrimination Policy

The officers, directors, committee members, employees, and persons served by this corporation shall be selected entirely on a nondiscriminatory basis with respect to age, sex, race, religion, national origin, and sexual orientation. It is the policy of The Syndicate not to discriminate on the basis of race, creed, ancestry, marital status, gender, sexual orientation, age, physical disability, veteran’s status, political service or affiliation, color, religion, or national origin.

### 8.5 By-law Amendment

These Bylaws may be amended, altered, repealed, or restated by a vote of the majority of the board of directors then in office at a meeting of the Board, provided, however,

1. that no amendment shall be made to these Bylaws which would cause the corporation to cease to qualify as an exempt corporation under Section 501(c)(3) of the Internal Revenue Code of 1986, or the corresponding section of any future Federal tax code;  and,
2. that an amendment does not affect the voting rights of directors. An amendment that does affect the voting rights of directors further requires ratification by a two-thirds (2/3) vote of a quorum of directors at a Board meeting.
3. that all amendments be consistent with the Articles of Incorporation.

## ARTICLE IX. COUNTERTERRORISM AND DUE DILIGENCE POLICY

In furtherance of its exemption by contributions to other organizations, domestic or foreign, The Syndicate shall stipulate how the funds will be used and shall require the recipient to provide the corporation with detailed records and financial proof of how the funds were utilized.

Although adherence and compliance with the US Department of the Treasury’s publication the “Voluntary Best Practice for US. Based Charities” is not mandatory, The Syndicate willfully and voluntarily recognizes and puts to practice these guidelines and suggestions to reduce, develop, re-evaluate and strengthen a risk-based approach to guard against the threat of diversion of charitable funds or exploitation of charitable activity by terrorist organizations and their support networks.

The Syndicate shall also comply and put into practice the federal guidelines, suggestion, laws and limitation set forth by pre-existing U.S. legal requirements related to combating terrorist financing, which include, but are not limited to, various sanctions programs administered by the Office of Foreign Assets Control (OFAC) in regard to its foreign activities.

## ARTICLE X. DOCUMENT RETENTION POLICY

### 10.1 Purpose

The purpose of this document retention policy is establishing standards for document integrity, retention, and destruction and to promote the proper treatment of The Syndicate records.

### 10.2 Policy

#### 10.2.1 General Guidelines

Records should not be kept if they are no longer needed for the operation of the business or required by law. Unnecessary records should be eliminated from the files. The cost of maintaining records is an expense which can grow unreasonably if good housekeeping is not performed. A mass of records also makes it more difficult to find pertinent records.

From time to time, The Syndicate may establish retention or destruction policies or schedules for specific categories of records in order to ensure legal compliance, and also to accomplish other objectives, such as preserving intellectual property and cost management. Several categories of documents that warrant special consideration are identified below. While minimum retention periods are established, the retention of the documents identified below and of documents not included in the identified categories should be determined primarily by the application of the general guidelines affecting document retention, as well as the exception for litigation relevant documents and any other pertinent factors.

#### 10.2.2 Exception for Litigation Relevant Documents

The Syndicate expects all officers, directors, and employees to comply fully with any published records retention or destruction policies and schedules, provided that all officers, directors, and employees should note the following general exception to any stated destruction schedule: If you believe, or the The Syndicate informs you, that corporate records are relevant to litigation, or potential litigation (i.e. a dispute that could result in litigation), then you must preserve those records until it is determined that the records are no longer needed. That exception supersedes any previously or subsequently established destruction schedule for those records.

#### 10.2.3 Minimum Retention Periods for Specific Categories

##### <IP_ADDRESS> Corporate Documents

Corporate records include the corporation’s Articles of Incorporation, By-Laws and IRS Form 1023 and Application for Exemption.** Corporate records should be retained permanently. IRS regulations require that the Form 1023 be available for public inspection upon request.

##### <IP_ADDRESS> Tax Records

Tax records include, but may not be limited to, documents concerning payroll, expenses, proof of contributions made by donors, accounting procedures, and other documents concerning the corporation’s revenues. Tax records should be retained for at least seven years from the date of filing the applicable return.

##### <IP_ADDRESS> Employment Records/Personnel Records

State and federal statutes require the corporation to keep certain recruitment, employment and personnel information.** The corporation should also keep personnel files that reflect performance reviews and any complaints brought against the corporation or individual employees under applicable state and federal statutes. The corporation should also keep in the employee’s personnel file all final memoranda and correspondence reflecting performance reviews and actions taken by or against personnel. Employment applications should be retained for three years. Retirement and pension records should be kept permanently. Other employment and personnel records should be retained for seven years.

##### <IP_ADDRESS> Board and Board Committee Materials

Meeting minutes should be retained in perpetuity in the corporation’s minute book. A clean copy of all other Board and Board Committee materials should be kept for no less than three years by the corporation.

##### <IP_ADDRESS> Press Releases and Public Filings

The corporation should retain permanent copies of all press releases and publicly filed documents under the theory that the corporation should have its own copy to test the accuracy of any document a member of the public can theoretically produce against the corporation.

##### <IP_ADDRESS>. Legal Files

Legal counsel should be consulted to determine the retention period of particular documents, but legal documents should generally be maintained for a period of ten years.

##### <IP_ADDRESS>. Marketing and Sales Documents

The corporation should keep final copies of marketing and sales documents for the same period of time it keeps other corporate files, generally three years. An exception to the three-year policy may be sales invoices, contracts, leases, licenses, and other legal documentation. These documents should be kept for at least three years beyond the life of the agreement.

##### <IP_ADDRESS> Development/Intellectual Property and Trade Secrets

Development documents are often subject to intellectual property protection in their final form (e.g., patents and copyrights). The documents detailing the development process are often also of value to the corporation and are protected as a trade secret where the corporation:
1. derives independent economic value from the secrecy of the information; and
2. has taken affirmative steps to keep the information confidential.
The corporation should keep all documents designated as containing trade secret information for at least the life of the trade secret.

##### <IP_ADDRESS>. Contracts

Final, execution copies of all contracts entered into by the corporation should be retained. The corporation should retain copies of the final contracts for at least three years beyond the life of the agreement, and longer in the case of publicly filed contracts.

##### <IP_ADDRESS> Correspondence

Unless correspondence falls under another category listed elsewhere in this policy, correspondence should generally be saved for two years.

##### <IP_ADDRESS> Banking and Accounting

Accounts payable ledgers and schedules should be kept for seven years. Bank reconciliations, bank statements, deposit slips and checks (unless for important payments and purchases) should be kept for three years. Any inventories of products, materials, and supplies and any invoices should be kept for seven years.

##### <IP_ADDRESS> Insurance

Expired insurance policies, insurance records, accident reports, claims, etcetera should be kept permanently.

##### <IP_ADDRESS> Audit Records

External audit reports should be kept permanently. Internal audit reports should be kept for three years.

#### ##### 10.2.4 Electronic Mail.

Email that needs to be saved should be either:

1. printed in hard copy and kept in the appropriate file; or
2. downloaded to a computer file and kept electronically or on disk as a separate file. The retention period depends upon the subject matter of the email, as defined by Board of Directors.

## ARTICLE XI. Transparency and Accountability.

### 11.1 Purpose

By making full and accurate information about its mission, activities, finances, and governance publicly available, The Syndicate practices and encourages transparency and accountability to the general public. This policy will:

1. indicate which documents and materials produced by the corporation are presumptively open to staff and/or the public
2. indicate which documents and materials produced by the corporation are presumptively closed to staff and/or the public
3. specify the procedures whereby the open/closed status of documents and materials can be altered.

### 11.2 Financial and IRS documents

The Syndicate shall provide its Internal Revenue forms 990, 990-T, 1023 and 5227, By-laws, conflict of interest policy, and financial statements to the general public for inspection free of charge.

### 11.3 Means and Conditions of Disclosure

The Syndicate shall make _widely available_ the aforementioned documents on its internet website, PreventHIVOK.org, to be viewed and inspected by the general public.

#### 11.3.1

The documents shall be posted in a format that allows an individual using the Internet to access, download, view and print them in a manner that exactly reproduces the image of the original document filed with the IRS (except information exempt from public disclosure requirements, such as contributor lists).

#### 11.3.2

The website shall clearly inform readers that the document is available and provide instructions for downloading it.

#### 11.3.3

Syndicate shall not charge a fee for downloading the information. Documents shall not be posted in a format that would require special computer hardware or software (other than software readily available to the public free of charge).
4. The Syndicate shall inform anyone requesting the information where this information can be found, including the web address. This information must be provided immediately for in-person requests and within 7 days for mailed requests.

### 11.4 IRS Annual Information Returns

The Syndicate shall submit the Form 990 to its board of directors prior to the filing of the Form 990. While neither the approval of the Form 990 or a review of the 990 is required under Federal law, the corporation’s Form 990 shall be submitted to each member of the board of director’s via (hard copy or email) at least 10 days before the Form 990 is filed with the IRS.

### 11.5 Board

#### 11.5.1

All board deliberations shall be open to the public except where the board passes a motion to make any specific portion confidential.

#### 11.5.2

All board minutes shall be open to the public once accepted by the board, except where the board passes a motion to make any specific portion confidential.

#### 11.5.3

All papers and materials considered by the board shall be open to the public following the meeting at which they are considered, except where the board passes a motion to make any specific paper or material confidential.

### 11.6 Staff Records

#### 11.6.1 Availability of Staff Records to Individuals

All staff records shall be available for consultation by the staff member concerned or by their legal representatives.

#### 11.6.2 Availability of Staff Records to Outside Agents

No staff records shall be made available to any person outside Syndicate except authorized governmental agencies.

#### 11.6.3 Availability of Staff Records to Authorized Personnel

Within Syndicate, staff records shall be made available only to those persons with managerial or personnel responsibilities for that staff member.

#### 11.6.4 Availability of Staff Records to Board of Directors

Staff records shall be made available to the board when requested.

### 11.7 Donor Records

#### 11.7.1 Donor Record Availability

All donor records shall be available for consultation by the members and donors concerned or by their legal representatives. No donor records shall be made available to any other person outside Syndicate except the authorized governmental agencies or allowed by individual donors.

#### 11.7.2 Review of Donor Records

Within Syndicate, donor records shall be made available only to those persons with managerial or personnel responsibilities for dealing with those donors; donor records shall be made available to directors when requested or as otherwise required by State and Federal law.

## ARTICLE XII. CODES OF ETHICS AND WHISTLEBLOWER POLICY

### 12.1 Purpose

The Syndicate requires and encourages directors, officers and employees to observe and practice high standards of business and personal ethics in the conduct of their duties and responsibilities. The employees and representatives of the corporation must practice honesty and integrity in fulfilling their responsibilities and comply with all applicable laws and regulations. It is the intent of The Syndicate to adhere to all laws and regulations that apply to the corporation and the underlying purpose of this policy is to support the corporation’s goal of legal compliance. The support of all corporate staff is necessary to achieving compliance with various laws and regulations.

### 12.2 Reporting Violations

If any director, officer, staff or employee reasonably believes that some policy, practice, or activity of The Syndicate is in violation of law, a written complaint must be filed by that person with the vice president or the board president.

### 12.3 Acting in Good Faith

Anyone filing a complaint concerning a violation or suspected violation of the Code must be acting in good faith and have reasonable grounds for believing the information disclosed indicates a violation of the Code. Any allegations that prove not to be substantiated and which prove to have been made maliciously or knowingly to be false shall be viewed as a serious disciplinary offense.

### 12.4 Retaliation

Said person is protected from retaliation only if she/he brings the alleged unlawful activity, policy, or practice to the attention of The Syndicate and provides the The Syndicate with a reasonable opportunity to investigate and correct the alleged unlawful activity. The protection described below is only available to individuals that comply with this requirement.

The Syndicate shall not retaliate against any director, officer, staff or employee who in good faith, has made a protest or raised a complaint against some practice of The Syndicate or of another individual or entity with whom The Syndicate has a business relationship, on the basis of a reasonable belief that the practice is in violation of law, or a clear mandate of public policy.

The Syndicate shall not retaliate against any director, officer, staff or employee who disclose or threaten to disclose to a supervisor or a public body, any activity, policy, or practice of The Syndicate that the individual reasonably believes is in violation of a law, or a rule, or regulation mandated pursuant to law or is in violation of a clear mandate of public policy concerning the health, safety, welfare, or protection of the environment.

### 12.5 Confidentiality

Violations or suspected violations may be submitted on a confidential basis by the complainant or may be submitted anonymously. Reports of violations or suspected violations shall be kept confidential to the extent possible, consistent with the need to conduct an adequate investigation.

### 12.6 Handling of Reported Violations

The board president or vice president shall notify the sender and acknowledge receipt of the reported violation or suspected violation within five business days. All reports shall be promptly investigated by the board and its appointed committee and appropriate corrective action shall be taken if warranted by the investigation.

This policy shall be made available to all directors, officers, staffs or employees and they shall have the opportunity to ask questions about the policy.

## ARTICLE XIII. AMENDMENT OF ARTICLES OF INCORPORATION

### 13.1 Amendment

Any amendment to Articles of Incorporation may be adopted by approval of two-thirds (2/3) of Board of Directors.

## CERTIFICATE OF ADOPTION OF BY-LAWS

I do hereby certify that the above stated Bylaws of Syndicate were approved by Board of Directors on ____________, __________ ___, 20___ and constitute a complete copy of the By-laws of Syndicate.

Secretary: __________________________
Date: ______________________________

repository: PreventHIVOK/Governing-Docs-Old

repo_name: PreventHIVOK/Governing-Docs-Old


text:
# RenderDoc extension to dump raw binary data of textures

Added an extension to read the binary data of a texture and dump it into a file.

Main use-case: when sending binary data to a shader as a texture and it gets corrupt in the driver level.

With this you can compare between the texture binary data you send to the shader vs the data the shader is actually using

## installation

if you use Linux or Cygwin in Windows you can run the install.sh to install the extension
if not you can follow these steps:
- copy the directory `raw_texture_dump` to `%APPDATA%\qrenderdoc\extensions\`
- start render doc and enabled the extension https://renderdoc.org/docs/how/how_python_extension.html#enabling-extensions
- then go to the TextureViewer panel when viewing the texture you want to export
- click the puzzel button in the Action Panel
- choose `Save Texture as Binary`

if you don't see `Save Texture as Binary` make sure you enabled the extension correctly

license: MIT

repository: ranlor/RenderDocRawTexture

branch_name: refs/heads/main

extension: md

license_type: permissive

repo_name: ranlor/RenderDocRawTexture


text:
# Bee Tracker
> I created this device to support HoneyBee health through detecting varroa mites and other invaders.  Given the urgency with the Giant Asian Hornet, I've quickly adapted this to detect them as well.  My friend [marlinspike](https://github.com/marlinspike) and I wrote the code in python to bring it altogether.  This app uses TensorFlow machine learning models to perform image classification locally at the device. All telemetry data is sent to **Azure IoT Central**.

### Required Hardware
- [Raspberry Pi Zero W](https://amzn.to/3sxi9aU)  (The pi zero is substantially slower for image recognition, but also consumes way less power.)

	- [Raspberry Pi Powersupply (for Zero or Pi 3)](https://amzn.to/2XO5uCn)

	- [Pi Zero camera ribbon](https://amzn.to/3bTHdmN)

- [Raspberry Pi 3 B+](https://amzn.to/3ilsYYZ)

- [Raspberry Pi 4 (4GB)](https://amzn.to/3qsTfr5)

	- [Raspberry Pi Powersupply (for Pi 4)](https://amzn.to/3ilvDSt)

- [Arducam 5MP camera](https://amzn.to/3oU6hh4)

- [32 GB SD Card](https://amzn.to/3ing7p7)

- [Jumper wires for connecting led and VCNL4010 motion sensor](https://amzn.to/39EB0rX)

- [20 ohm resistor for led](https://amzn.to/3qv0Nty)

- [3v white LED for camera flash](https://amzn.to/2XNUSTV)

**Motion Sensor:**

- [Adafruit VCNL4040 motion sensor](https://www.adafruit.com/product/4161)

	- [Jumper wire for VCNL4040](https://www.adafruit.com/product/4397)

OR

- [Adafruit VCNL 4010 motion sensor](https://www.adafruit.com/product/466)

## Getting Started
### Software Installation (Raspberry Pi3 & Raspberry Pi4)
1. Download Latest version of [Raspberry Pi OS](https://www.raspberrypi.org/software/operating-systems/):
At the time of writing this we're using Kernel version 5.4

2. Install the OS using [Win32 Disk Imager](https://win32diskimager.org/)
3. Booth the Pi and setup all initial configuration:

	- Keyboard, Language, Timezone, Wifi

	- Update the pi (Sudo apt-get update) This might take ~40 - 60min

	- Sudo raspi-config

		   	i. System Option -> HostName -> BeeTracker

		   	ii. Interface Options -> Camera -> Enabled

		  	iii. Interface Options -> SSH -> Enabled

		  	iv. Interface Options -> I2C -> Enabled

		  	v. Finish / Reboot

4. SSH into your new pi
5. mkdir src
6. cd src
7. git clone https://github.com/prettyflyforabeeguy/BeeTracker.git
8. pip3 install -r ~/src/BeeTracker/requirements.txt
9. sudo apt-get install libatlas-base-dev

### Beebooth Assembly
1. Solder the resistor to the Anode side of the led (the slightly longer side) and attach a jumper wire to each end.  I used a little shrink tubing to keep things more tidy but you don't have to do this.
2. Slide the LED into the opening near the top of the booth.  The idea is to bend the LED bulb to be right next to the camera lens to act as a flash.  Careful not to block the camera lens with the LED.

![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/lens_and_led.jpg)
![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/led1.jpg)

3. Slip the jumper wires through the slot on the lower right hand side of the booth.  Note it's probably easier to first attach the jumper wires to the sensor before slipping them through.(see wiring instructions below)  Use a small zip tie or hot glue to hold the motion sensor in place.

![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/sensor_booth1.jpg)
![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/sensor_booth2.jpg)

4. Carefully attach the camera ribbon to the camera. Take care to insert the ribbon the proper direction.  Usually the little black slider clip on the camera will be up against the colored strip on the ribbon.
5. Insert the Arducam face down into the 3D printed bee booth (lens facing into the booth opening). Note the ribbon should be sticking out toward the square opening (the front) of the bee booth
![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/boothcamera.jpg)

6. Snap the Raspberry Pi into the 3d printed holder, and slide it into the slot on top of the booth. It should fit all the way forward so the flat pack of the Pi case is flush with the flat back of the bee booth.
![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/caseattach1.jpg)
![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/caseattach2.jpg)

7. Attach the camera ribbon to the Raspberry Pi
8. Attach a jumper wire to the cathode (short end) from the LED to pin14 (Ground) on the Pi and the anode (long end  with resistor) with a jumper wire to pin16 (GPIO23) on the pi.

### Hardware wiring
For the VCNL 4010 Sensor:
1. Attach the red wire to the Vin pin on the sensor, and connect the other end to pin 1 on the Raspberry Pi (3.3v)
2. Attach the black wire to the GND pin on the sensor, and connect the other end to 9 on the Raspberry Pi (Ground)
3. Attach the blue wire to the SCL pin on the sensor, and connect the other end to pin 5 on the Raspberry Pi (GPIO3)
4. Attach the Yellow wire to the SDA pin on the sensor, and connect the other end to pin 3 on the Raspberry Pi (GPIO2)
5. 3vo and INT pins are not used on the motion sensor.
![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/sensor_wires.jpg)

### Hardware wiring
For the VCNL 4040 Sensor:
6. Attach the 4 pin female to female pin to either socket on the motion sensor
7. Attach the red wire to the Vin pin on the sensor, and connect the other end to pin 1 on the Raspberry Pi (3.3v)
8. Attach the black wire to the GND pin on the sensor, and connect the other end to 9 on the Raspberry Pi (Ground)
9. Attach the blue wire to the SCL pin on the sensor, and connect the other end to pin 3 on the Raspberry Pi (GPIO2)
10. Attach the Yellow wire to the SDA pin on the sensor, and connect the other end to pin 5 on the Raspberry Pi (GPIO3)
11. Note the blue and yellow wires are in reversed positions compared to using the VCNL4010 sensor.

![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/vcnl4040.jpg)

Once everything is attached should look something like this:

![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/final_setup1.jpg)

If you want to add the weather protection cover it should slip right over everything like this:

![alt text](https://raw.githubusercontent.com/prettyflyforabeeguy/BeeTracker/master/assembly_imgs/final_setup2.jpg)

### Azure Resources Required
- Azure IoT Hub: Your device will need to be enrolled, and it's connection string updated in the **creds.json** file discussed below
- Azure Storage: Optionally used to archive telemetry data from the device
- Azure Stream Analytics: Optionally used for telemetry analysis

### Configuring the Credentials file (creds.json)
This app needs a **creds.json** file to store certain required credential and status info. It's not contained in the repo for obvious reasons.  If you want to connect to our global dashboard please contact me separately so your device can be added.
here's the structure you'll need:

```json
{
    "device_id" : "CommunityDevicesFromGithub",
    "latitude" : "",
    "longitude" : "",
    "owner_email" : "",
    "provisioning_host": "global.azure-devices-provisioning.net",
    "registration_id": "CommunityDevicesFromGithub",
    "id_scope": "0ne00146FA6",
    "symmetric_key": "Please Contact me for this public dashboard key",
    "blob_token": "",
    "tf_models": ""
}
```
Save this in a file called **creds.json** in the root folder of the application.

## Download the tensor flow models
You'll want to download both the Tier1 and Tier2 models and save them in BeeTracker/tier1 and BeeTracker/teir2 accordingly.
As our community grows, we'll have new image data to further improve the training of these learning models and will publish updated versions.

TIER1: https://1drv.ms/u/s!Aok2ArNyzY-zvSVIRDXiCsHZr5i3?e=CafR22

TIER2: https://1drv.ms/u/s!Aok2ArNyzY-zvSbGrdxlGFCBOBW1?e=veEdGo

## Running the app
Depending which sensor you're using, run the app using the command:
```bash
 python3 motion.py --sensor vcnl4010
 python3 motion.py --sensor vcnl4040
 ```
There are options to upload your images to a cloud storage container.  This is disabled by default.
If you enable this, your images will contribute to future model training.

Note that the initial startup time for the app is approx 30-45 seconds, as it loads the TensorFlow model. Performing image classification on the first image takes substantially longer (30s), than every subsequent image (1.1s).

## Running in TEST Mode
Test mode tells the app to use the sample images in the **img_test** folder instead of ones it takes with the camera. These images are not ones used to train the model used, but ones that will test the classification and allow the app to run without the need for Bees to look at!

**To run in TEST Mode:**
```bash
Python3 motion.py --test True
```

repository: NicoJuicy/BeeTracker

branch_name: refs/heads/master

repo_name: NicoJuicy/BeeTracker


text:
# VL53L0X Time-of-Flight Laser Ranging Sensor

Code for getting started with a VL53L0X ToF (Time-of-Flight) Laser Ranging sensor.

![sensor](assets/vl53l0x-sensor.jpg)

The VL53L0X sensor uses a small laser and a matching detector sensor. The VL53L0X detects how long it takes the laser light to bounce off a surface back to the sensor. Since it is using a very narrow light source, it only detects the distance of surfaces directly in front of the sensor.

The VL53L0X uses the I2C serial protocol.

## Boards

Setup instructions and starter code for different development boards

| Board | Folder |
| --- | --- |
| Arduino Uno | [arduino-uno/](arduino-uno/) |
| Arduino MKR WiFi 1010 | For MKR WiFi 1010 follow instructions for Arduino Uno [arduino-uno/](arduino-uno/) |
| Arduino Nano 33 BLE | For Nano 33 BLE follow instructions for Arduino Uno [arduino-uno/](arduino-uno/) |
| ESP32 | For ESP32 boards, follow instructions for ESP8266 [esp8266/](esp8266/) |
| ESP8266 | [esp8266/](esp8266/) |
| Jetson Nano | For Jetson Nano, follow instructions for Raspberry Pi [raspberry-pi/](raspberry-pi/) |
| Raspberry Pi | [raspberry-pi/](raspberry-pi/) |
|  |  |

## Other Files and Folders

| File/Folder | Description |
|--- | --- |
| [additional-libraries/](additional-libraries/) | Folder contains libraries needed for Arduino sketches. They are included as submodules. Use either `git clone --recursive` or `git submodule init` after cloning. |
| [docs/vl53l0x.pdf](docs/vl53l0x.pdf) | Data sheet for sensor |
|  |  |

## Branches

**main**: main branch. currently not using other branches.

## References

- Manufacturer: https://www.st.com/en/imaging-and-photonics-solutions/vl53l0x.html
- Datasheet: https://www.st.com/resource/en/datasheet/vl53l0x.pdf
- https://learn.adafruit.com/adafruit-vl53l0x-micro-lidar-distance-sensor-breakout/overview


text:
---
external help file: d365fo.integrations-help.xml
Module Name: d365fo.integrations
online version:
schema: 2.0.0
---

# Get-D365DmfMessageStatus

## SYNOPSIS
Get Message Status from the DMF

## SYNTAX

```
Get-D365DmfMessageStatus [-MessageId] <String> [[-Tenant] <String>] [[-Url] <String>] [[-SystemUrl] <String>]
 [[-ClientId] <String>] [[-ClientSecret] <String>] [-WaitForCompletion] [[-Token] <String>] [-EnableException]
 [<CommonParameters>]
```

## DESCRIPTION
Get the Message Status based on the MessageId from the DMF Endpoint of the Dynamics 365 for Finance & Operations environment

## EXAMPLES

### EXAMPLE 1
```
Get-D365DmfMessageStatus -MessageId "84a383c8-336d-45e4-9933-0c3e8bfb734a"
```

This will get the message status through the DMF endpoint.
It will use "84a383c8-336d-45e4-9933-0c3e8bfb734a" as the MessageId parameter passed to the DMF endpoint.

It will use the default OData configuration details that are stored in the configuration store.

### EXAMPLE 2
```
Get-D365DmfMessageStatus -MessageId "84a383c8-336d-45e4-9933-0c3e8bfb734a" -Tenant "e674da86-7ee5-40a7-b777-1111111111111" -Url "https://usnconeboxax1aos.cloud.onebox.dynamics.com" -ClientId "dea8d7a9-1602-4429-b138-111111111111" -ClientSecret "Vja/VmdxaLOPR+alkjfsadffelkjlfw234522"
```

This will import a package into the 123456789 job through the DMF endpoint.
It will use "84a383c8-336d-45e4-9933-0c3e8bfb734a" as the MessageId parameter passed to the DMF endpoint.
It will use "e674da86-7ee5-40a7-b777-1111111111111" as the Azure Active Directory guid.
It will use "https://usnconeboxax1aos.cloud.onebox.dynamics.com" as the base D365FO environment url.
It will use "dea8d7a9-1602-4429-b138-111111111111" as the ClientId.
It will use "Vja/VmdxaLOPR+alkjfsadffelkjlfw234522" as ClientSecret.

### EXAMPLE 3
```
$token = Get-D365ODataToken
```

PS C:\\\> Get-D365DmfMessageStatus -MessageId "84a383c8-336d-45e4-9933-0c3e8bfb734a" -Token $token

This will get the message status through the DMF endpoint.
It will get a fresh token, saved it into the token variable and pass it to the cmdlet.
It will use "84a383c8-336d-45e4-9933-0c3e8bfb734a" as the MessageId parameter passed to the DMF endpoint.

It will use the default OData configuration details that are stored in the configuration store.

## PARAMETERS

### -MessageId
MessageId of the message that you want to query the status for

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: True
Position: 1
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```

### -Tenant
Azure Active Directory (AAD) tenant id (Guid) that the D365FO environment is connected to, that you want to access through DMF

```yaml
Type: String
Parameter Sets: (All)
Aliases: $AadGuid

Required: False
Position: 2
Default value: $Script:ODataTenant
Accept pipeline input: False
Accept wildcard characters: False
```

### -Url
URL / URI for the D365FO environment you want to access through DMF

```yaml
Type: String
Parameter Sets: (All)
Aliases: Uri

Required: False
Position: 3
Default value: $Script:ODataUrl
Accept pipeline input: False
Accept wildcard characters: False
```

### -SystemUrl
URL / URI for the D365FO instance where the OData endpoint is available

If you are working against a D365FO instance, it will be the URL / URI for the instance itself, which is the same as the Url parameter value

If you are working against a D365 Talent / HR instance, this will to be full instance URL / URI like "https://aos-rts-sf-b1b468164ee-prod-northeurope.hr.talent.dynamics.com/namespaces/0ab49d18-6325-4597-97b3-c7f2321aa80c"

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: 4
Default value: $Script:ODataSystemUrl
Accept pipeline input: False
Accept wildcard characters: False
```

### -ClientId
The ClientId obtained from the Azure Portal when you created a Registered Application

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: 5
Default value: $Script:ODataClientId
Accept pipeline input: False
Accept wildcard characters: False
```

### -ClientSecret
The ClientSecret obtained from the Azure Portal when you created a Registered Application

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: 6
Default value: $Script:ODataClientSecret
Accept pipeline input: False
Accept wildcard characters: False
```

### -WaitForCompletion
Instruct the cmdlet to wait until the Message Status is in a terminating state

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```

### -Token
Pass a bearer token string that you want to use for while working against the endpoint

This can improve performance if you are iterating over a large collection/array

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: 7
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -EnableException
This parameters disables user-friendly warnings and enables the throwing of exceptions
This is less user friendly, but allows catching exceptions in calling scripts

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

## OUTPUTS

## NOTES
Tags: Import, Upload, DMF, Package, Packages, Message, MessageId, Message Status

Author: Mötz Jensen (@Splaxi)

## RELATED LINKS

[Add-D365ODataConfig]()

[Get-D365ActiveODataConfig]()

[Import-D365DmfPackage]()

[Set-D365ActiveODataConfig]()

branch_name: refs/heads/development

gha_language: PowerShell

gha_license_id: MIT


text:
You can get the data from the
[SEG-website](https://wiki.seg.org/wiki/SEG/EAGE_Salt_and_Overthrust_Models)
or via the
[direct link](https://s3.amazonaws.com/open.source.geoscience/open_data/seg_eage_models_cd/Salt_Model_3D.tar.gz).
The zip-file is 513.1 MB big. Unzip the archive and proceed.

Copy the `'Salt_Model_3D/3-D_Salt_Model/SURFACES/'` folder to the `'./data/'`
directory in this repository

Copy the `'Salt_Model_3D/3-D_Salt_Model/VEL_GRIDS/'` folder to the `'./data/'`
directory in this repository


text:
---
layout: post
title: 'PyScript'
description:
headline:
modified: 2022-05-24
category: webdevelopment
imagefeature:
tags: [PyScript]
mathjax:
chart:
share: true
comments: true
featured: true
disqus:
---

# Record

## 목차

-   [](#)

## 개념

-   [https://velog.io/@taekkim/PyScript-%EB%9E%80](https://velog.io/@taekkim/PyScript-%EB%9E%80)
-   [https://pyscript.net/](https://pyscript.net/)
-   [https://github.com/pyscript/pyscript](https://github.com/pyscript/pyscript)


text:
flickr-simple-reorder-server
============================

A simple tool to help reorder photos in galleries (photosets).

IMPORTANT!!!
------------

This is a mini-app for using in controlled environment.  All authentication & authorization jobs will be done in browser-side.  The server is just a semi-proxy to bypass the CORS limitation of Flickr's OAuth API, which means the auth token / secret will be passing between browser & server.

If you really care about your account security, **ONLY** use this application in well controlled environment (e.g. HTTPS, local, intranet).

Flickr used to have 2 auth method: legacy API & newer OAuth 1.0a API.  Although Flickr officially recommends the OAuth one, but since OAuth API has CORS limitation, it must be requested from server, not browser.  I don't want to write a server because this application is intent to be very simple & lightweight.  OAuth is more secure than legacy one only when with a heavy server-side with DB or stateful session (so it can save some sensitive data like token secret at server).  As a result, in the previous version this application uses Flickr's legacy auth API.

But on 2017/6/8 Flickr suddenly removed the legacy auth API without a notice.  This forced me to write a server for the OAuth API.  But still I don't want to write a very heavy server because I believe it's way more overkill to what I want.  So I decided to pass all sensitive data (except API key) to user's browser.  Let browser to do the business and leave this service a proxy & signer.

Author
------

[**Gino Zhang (a.k.a. WhiteTrefoil)**](http://en.gravatar.com/whitetrefoil)

Email<EMAIL_ADDRESS>
Location: Shanghai, China

License
-------

[Apache License 2.0](https://github.com/whitetrefoil/flickr-simple-reorder-server/blob/master/LICENSE)

Links
-----

* Project Home - https://github.com/whitetrefoil/flickr-simple-reorder-server
* Report Issue - https://github.com/whitetrefoil/flickr-simple-reorder-server/issues
* The front-end - https://github.com/whitetrefoil/flickr-simple-reorder
* Author's Flickr - https://www.flickr.com/whitetrefoil

Changelog
---------

### v0.2.4

* Export API types.

### v0.2.3

* Set response header `X-Accel-Buffering: no` to disable nginx proxy buffer.

### v0.2.2

* Fix missing bin file.

### v0.2.1

* Fix build process.

### v0.2.0

* Add a new "bulk_reorder" API.

### v0.1.11

* Update some dependencies.
* Fix wrong version number in `package-lock.json`.

### v0.1.10

* Fix config file generation.

### v0.1.9

* Add missing bin file.

### v0.1.8

* Better help message.
* Don't format "package.json" to be compatible with newest NPM standard.
* Fix wrong version number in "package.json".

### v0.1.7

* Lite some big logs.

### v0.1.6

* Export reorder result.

### v0.1.5

* Export photoset primary photo width & height.

### v0.1.4

* Fix missing IPhotoset model.

### v0.1.3

* Small tweaks.

### v0.1.2

* Fix bug about env read from config file.

### v0.1.1

* Prefix all endpoints with `/api`.

### v0.1.0

* Initial release.


text:
Title: Mocking AWS in Unit Tests
Date: 2019-09-23 9:00
Category: Python
Tags: python, pytest, tests, aws, mock, mocking

[TOC]

## Overview

This post covers a technique for mocking AWS in unit tests so that you can test functionality that normally
requires API calls and handling responses, by mocking those responses instead of making actual API calls.

## A Simple Example: Mocking API Responses

### The Genuine AWS Call

Let's start with an example of an AWS API call. Here's how our program will be structured:
start with a driver `lister.py` that creates an AWS secrets manager client and defines a
function to list secrets using the secrets manager client, then a test for it in `test_lister.py`
that mocks the AWS call.

This example is simple and uses just one function, `list_secrets()`,
which returns a JSON response that looks something like this:

```text
{
  "SecretList": [
    {
      "ARN": "arn:aws:secretsmanager:us-east-1:000000000000:secret:prefix/secret1-abc123",
      "Name": "prefix/es_source_ip",
      "LastChangedDate": "2019-09-23 17:29:16.267000-07:00",
      "LastAccessedDate": "2019-09-23 17:00:00-07:00",
      "SecretVersionsToStages": {
        "658c3b41-0806-48b9-b05d-ea7dc2dbf237": [
          "AWSCURRENT"
        ],
        "f37ccfe2-16e0-4305-a250-ef89d2c47ece": [
          "AWSPREVIOUS"
        ]
      }
    },
    {
      "ARN": "arn:aws:secretsmanager:us-east-1:000000000000:secret:prefix/secret2-def789",
      "Name": "prefix/secret2",
      "LastChangedDate": "2019-09-22 17:05:01.431000-07:00",
      "LastAccessedDate": "2019-09-22 17:00:00-07:00",
      "SecretVersionsToStages": {
        "95AE5F8B-34E7-4EDF-A672-9E3AF1A4732E": [
          "AWSCURRENT"
        ],
        "F29E224A-BC03-4780-B64E-EA666B99D952": [
          "AWSPREVIOUS"
        ]
      }
    }
  ]
}
```

Using the secrets manager API:

**`lister.py`**:

```python
import boto3

sm_client = boto3.client('secretsmanager')

def print_secret_names():
    s = sm_client.list_secrets()
    for secret in s['SecretList']:
        if 'Name' in secret and 'LastAccessedDate' in secret:
            print(f"Secret Name: {secret['Name']} (last accessed: {secret['LastAccessedDate']})")

if __name__=="__main__":
    print_secret_names()
```

If we run this file, we'll see a list of secrets in the real secrets manager -
that is, the secrets manager that is linked to the boto credentials in `~/.aws`,
so the secrets we see are the actual secrets in the secret manager:

```text
$ python lister.py
Secret Name: prefix/secret1 (last accessed: 2019-09-23 17:00:00-07:00)
Secret Name: prefix/secret2 (last accessed: 2019-09-23 17:00:00-07:00)
Secret Name: prefix/secret3 (last accessed: 2019-09-23 17:00:00-07:00)
```

### The Mocked AWS Call

It is important to only mock the functionality we need.
We should mock the returned JSON, but only the `Name`
and `LastAccessedDate` fields.

To mock the call to `list_secrets()`, we start by importing
`mock` from `unittest`. Then we import the file that has the
function we want to test. We also import any other modules
we need.

Next, we are mocking a call to a method of an object,
which we can do by creating a context via `with mock.patch()`
(and passing it a string with the name of the object we want
to mock, or patch).

```python
import unittest
from unittest import mock
import lister
import datetime

class TestMo(unittest.TestCase):
    def test_main(self):
        with mock.patch("mo.sm_client") as sm:
            ...
            sm_client.list_secrets = mock.MagicMock( ... )
            ...
```

Any calls made to `sm_client` in the `mo` module will be mocked
using the `mock.MagicMock` object that we define in the context,
so we craft the response we want before we call the method we
want to test (which in turn will call `sm_client.list_secrets()`).

The full version of the test looks like this:

**`test_lister.py`**:

```python
import unittest
from unittest import mock
import lister
import datetime

class TestLister(unittest.TestCase):
    def test_main(self):
        with mock.patch("lister.sm_client") as sm:
            return_json = {
                "SecretList": [
                    {
                        "Name": "fakesecret1",
                        "LastAccessedDate": datetime.datetime.now()
                    },
                    {
                        "Name": "fakesecret2",
                        "LastAccessedDate": datetime.datetime.now()
                    }
                ]
            }
            sm.list_secrets = mock.MagicMock(return_value = return_json)
            lister.print_secret_names()

if __name__=="__main__":
    unittest.main()
```

When the test file is run via Python, we see the fake secrets:

```text
$ python test_lister.py
Secret Name: fakesecret1 (last accessed: 2019-09-23 20:31:49.186874)
Secret Name: fakesecret2 (last accessed: 2019-09-23 20:31:49.186880)
.
----------------------------------------------------------------------
Ran 1 test in 0.000s

OK
```

branch_name: refs/heads/source

gha_language: HTML


text:
---
title: Build Notifications
layout: page
tags:
  - administration
  - notifications

redirect_from:
  - /administration/notifications/
  - /basic/getting-started/webhooks/
  - /integrations/webhooks/
weight: 2
---

* include a table of contents
{:toc}

## Configuring Build Notifications

To configure build notifications, go to your *Project Settings* and then click into the **Notifications** tab.

## Email notification

By default anyone who either owns a project or was added as a team member will receive an email whenever a build fails and if a build on a branch passes when the previous one failed. Therefore, whenever a branch is back to OK you will be notified.

### Disable Email

If you don't want to receive any emails you can set that on your [account page](https://www.codeship.com/user/edit).

### Receive emails when I am involved

In your project's notification settings you can set the option that you only receive an email when the build was on the master branch or if you started this build.

## Notification Integrations

You will get notifications whenever a build starts and finishes. All information about the result and a link to it will be in the message.

We have support for the following chat notification systems. Currently you can't customize the messages sent by Codeship.

* Hipchat
* Slack
* Flowdock
* Grove.io
* Campfire

* include a table of contents
{:toc}

## Shipscope - Chrome Extension

Monitor your Codeship projects and builds with [Shipscope](https://chrome.google.com/webstore/detail/shipscope/jdedmgopefelimgjceagffkeeiknclhh). Shipscope lists all of your Codeship projects and presents the status of recent builds in the Chrome toolbar. You can restart a build or go straight to the build details on the Codeship service.

The Shipscope notifications presented by Chrome will end up in the Notification Center. If you would like to prevent Shipscope notifications in the Notification Center, simply:

1. Click the bell icon in the lower right corner of your computer screen (on Windows) or the upper right of your computer screen (on Mac) to open the Notifications Center.

2. In the Notifications Center, click the gear icon  on the bottom right corner (on Windows) or the upper right corner (on Mac).

3. Uncheck the box next to "Shipscope".

Shipscope is open source and lives on [GitHub](https://github.com/codeship/shipscope).

## Webhooks For Custom Notifications

Go to the _Notification_ settings of your project and enter the HTTP endpoint of the service you want to notify.

![Webhooks]({{site.baseurl}}/images/integrations/webhooks.png)

### Webhooks Payload

We send you a POST request containing the following build data

```json
{
  "build": {
    "build_url":"https://www.codeship.com/projects/10213/builds/973711",
    "commit_url":"https://github.com/codeship/docs/
                  commit/96943dc5269634c211b6fbb18896ecdcbd40a047",
    "project_id":10213,
    "build_id":973711,
    "status":"testing",
    # PROJECT_FULL_NAME IS DEPRECATED AND WILL BE REMOVED IN THE FUTURE
    "project_full_name":"codeship/docs",
    "project_name":"codeship/docs",
    "commit_id":"96943dc5269634c211b6fbb18896ecdcbd40a047",
    "short_commit_id":"96943",
    "message":"Merge pull request #34 from codeship/feature/shallow-clone",
    "committer":"beanieboi",
    "branch":"master"
  }
}
```

The _status_ field can have one of the following values:

- `testing` for newly started build
- `error` for failed builds
- `success` for passed builds
- `stopped` for stopped builds
- `waiting` for waiting builds
- `ignored` for builds ignored because the account is over the monthly build limit
- `blocked` for builds blocked because of excessive resource consumption
- `infrastructure_failure` for builds which failed because of an internal error on the build VM

## GitHub, Bitbucket and Gitlab Status API

We will automatically use the status API for pull requests on Github, Bitbucket and Gitlab. This does not need to be explicitly enabled, although it can be disabled via your *Project Settings*.

repository: barkinet/documentation

repo_name: barkinet/documentation


text:
---
layout: page
title: Contexts
parent: python_manual
---

### Interface

#### Properties

Python property | Brief description | Equivalent C++ functions
--------------- | ----------------- | ------------------------
`dimensions`{:.prop} | Gets/sets the dimensions of the context. | `GetDimensions()`, `SetDimensions()`
`documents`{:.prop} | Retrieves a document within the interface. | `GetDocument()`, `GetNumDocuments()`
`focus_element`{:.prop} | Retrieves the context's focus element. | `GetFocusElement()`
`hover_element`{:.prop} | Retrieves the element under the context's cursor. | `GetHoverElement()`
`root_element`{:.prop} | Retrieves the context's root element. | `GetRootElement()`
`name`{:.prop} | Retrieves the context's name. | `GetName()`

##### Retrieving documents

The documents property on the context can be referenced in several ways. For example, as an array:

```python
for document in context.documents:
	print document.title

index = 0
while index < len(context.documents):
	print str(index) + ": " + context.documents[index].title
```

Or as a dictionary, looking documents up by their ID:

```python
try:
	document = context.documents["highscores"]
except KeyError:
	print "No document found!"
```

Or accessing documents as attributes on the documents property itself:

```python
try:
	document = context.documents.highscores
except AttributeError:
	print "No document found!"
```

#### Methods

The following methods are exported from the C++ interface.

Python method | Brief description
`AddEventListener()` | Attaches an inline event listener to the root of the context.
`AddMouseCursor()` | Adds a previously-loaded mouse cursor to the document.
`CreateDocument()` | Creates a new document.
`LoadDocument()` | Loads a document from an external RML file.
`LoadMouseCursor()` | Loads a mouse cursor from an external RML file.
`Render()` | Renders the context.
`ShowMouseCursor()` | Shows or hides the mouse cursor.
`UnloadAllDocuments()` | Unloads all loaded documents within the context.
`UnloadAllMouseCursors()` | Unloads all of the context's mouse cursors.
`UnloadDocument()` | Unloads one of the context's documents.
`UnloadMouseCursor()` | Unloads one of the context's cursors.
`Update()` | Updates the context.

### Creating contexts

Contexts can be created in Python with the `CreateContext()` function in the {{page.lib_name}} module. This function takes the name of the context as a string and the dimensions as an `Vector2i` type.

```python
new_context = rocket.CreateContext("hud", rocket.Vector2i(1024, 768))
```

### Accessing contexts

Existing contexts can be accessed in Python via the contexts member on the rocket module. They can then be accessed via name or index.

```python
context = rocket.contexts["hud"]
```

List all contexts

```python
for context in rocket.contexts:
  print context.name
```

repository: barotto/libRocketDoc

gha_language: Ruby

repo_name: barotto/libRocketDoc


text:
# Mongo-Express-Mongo-Basic-CRUD-employees
The repo contains source code for the simplest basic CRUD operations applications using MongoDB, Express and Node to create REST apis.

* npm i

* nodemon run start/ npm start

Example: GET http://localhost:9000/employees using POSTMAN


text:
#Request Priority
Request’s priority can be changed through the HTTPRequest’s Priority property. Higher priority requests will be picked from the request queue sooner than lower priority requests.

```csharp
var request = new HTTPRequest(new Uri("https://google.com"), ...);
request.Priority = -1;
request.Send();
```

url: https://raw.githubusercontent.com/gazsoka85/BestHTTP-Documentation/f7f6fad8eece7f66ba568876a0cb1b555d496f1b/docs/1. HTTP Request/1.2. Advanced Topics/Request Priority.md

filename: Request Priority.md


text:
# MachineLearningRegressionBenchmark

This repository holds benchmark for regression algorithms using an agent with learning capabilities on a non linear function affected by noise.

# Introduction

This application is developed using python 3.7+. To be able to run it you need to install the packages from [requirements.txt](https://github.com/IulianOctavianPreda/MachineLearningRegressionBenchmark/blob/master/requirements.txt). You can install them using:

`$ pip install -r requirements.txt`

These packages are:

-   Pandas
-   Numpy
-   Matplotlib
-   Scikit-learn
-   Joblib
-   Pysimplegui
-   Pyinstaller

# Architecture

The code is split in multiple packages:

-   main - the main entry point in the application
-   src - package containing the main classes used by the application
-   enums - contains the enums used by the gui, scaler and models
-   helpers - is the package that contains static methods useful for the classes found in the src package

# Application flow

-   The number of variables, their exponent and their coefficient can be user defined, otherwise are picked randomly
-   The function is composed based on the selected values
-   The application then will pick random values for each variable. This will be the dataset. It can be loaded from a CSV too filling in the parameters automatically.
-   Using the dataset we create the test sets in a ratio of 20-80 and then the data will be scaled using the Scaler
-   Then a Model is selected and trained.


text:
---
title: "Using Machine Learning to Predict Bike Rentals Based on Weather Conditions"
date: 2020-07-29
---

import numpy as np

import matplotlib.pyplot as plt

import pandas as pd

dataset = pd.read_csv('bikeshare_data.csv')

dataset = dataset[dataset.holiday != 1]

dataset = dataset[dataset.workingday != 0]

dataset = dataset[dataset.hr.isin([9, 10, 11, 12, 13, 14, 15, 16, 17])]

dataset = dataset[['temp', 'hum', 'windspeed', 'cnt']]

x_train = dataset.iloc[:,0:3]

y_train = dataset[['cnt']]

prediction_data = pd.read_csv('topredict.csv')

x_test = prediction_data.iloc[:,0:3]

from sklearn.linear_model import LinearRegression

regressor = LinearRegression()

regressor.fit(x_train, y_train)

y_pred = regressor.predict(x_test)

y_pred[y_pred < 170] = 0

y_pred[y_pred >= 170] = 1

final_prediction = pd.DataFrame(data=y_pred)

final_prediction.columns = ['final_prediction']

final_prediction.index.names = ['index']

final_prediction.to_csv('predictions.csv')


text:
# dotfiles

These dotfiles are inspired by [Mach-OS/Machfiles](https://github.com/Mach-OS/Machfiles/blob/master/README.md), and target macOS.

## Installing

You will need `git` and GNU `stow`:

```bash
brew install stow
```

Clone into your `$HOME` directory or `~`:

```bash
git clone git@github.com:gohanlon/dotfiles.git ~
```

Run `stow` to symlink everything or just select what you want:

```bash
stow */ # Everything (the '/' ignores the README)
```

```bash
stow zsh # Just my zsh config
```

repository: gohanlon/dotfiles

repo_name: gohanlon/dotfiles


text:
---
title: Norwegian Soft Autumn Styled Shoot
excerpt: "Today I will share with you an absolutely blissful styled shoot from beautiful Norway"

image_url: /img/blog/norwegian-soft-autumn-styled-shoot.jpg
image_description: "Bride leaning against groom in nature"

categories: inspiration
---
Today I will share with you an absolutely blissful styled shoot sent by the talented [@ingvildkolnes](https://www.instagram.com/ingvildkolnes/), and I know you will find it as magical as I did.

Because the unexpected combination of the dramatic fjords, the crystalline water with the soft hues of blue and dusty pink on an evening at dusk will most certainly produce a lasting effect that evokes a gentle and eerie like- silence that Ingvild so skilfully caught.

Norway is a sought-after spot nowadays for wedding destinations and elopements due to its nature's abundance and diversity. The wild landscapes provide the most beautiful and secluded locations for the gorgeous wedding portraits that seem to be in trend now.

Autumn is known for its opulence built by vibrant colors, fresh produce, statement decor, the famous and delicious looking harvest stations, the brimming tables with flowers and metal touches but this is not the backbone of this shoot.  On the contrary, the creatives played with neutrals, with light and minimalistic decor. The fullness of the shoot and its serenity comes through the ingenious overlapping of nature's organic colors and the created decor: the silver mist dress is one with the evening sky, and the table decor palette is following the sun descending tones.

Come and enjoy with me this early September evening on the shore of Norway´s largest lake, Mjøsa, area known as the Tuscany of Norway.

        {% for i in (1..40) %}

        {% endfor %}

## Vendors
- Photographer: [Ingvild Kolnes](http://www.ingvildkolnes.no), [@ingvildkolnes](https://www.instagram.com/ingvildkolnes/)
- Workshop speakers: [Koby & Elizabeth Brown](http://kobybrown.com/)
- Editor, Stylist & Workshop Hostess: [Norwegian Wedding Magazine](http://www.norwegianweddingblog.com/), [@norwegianweddingblog](https://www.instagram.com/norwegianweddingblog/)
- Floral Artist: [Eucalyptus](http://eucalyptus.no/) [@eucalyptusblomster](https://www.instagram.com/eucalyptusblomster/)
- Hair & Make Up: [Hawwa Make Up](https://hawwamakeup.com/)
- Wardrobe & shoes: [Norwegian Wedding Magazine](http://www.norwegianweddingblog.com/), [@norwegianweddingblog](https://www.instagram.com/norwegianweddingblog/)
- Location: [Hoel Gård - En perle ved Mjøsa](http://www.hoel-gaard.no/), [@hoelgard](https://www.instagram.com/hoelgard/)
- Models: [Jannike Berg](https://www.instagram.com/misstrueredhead/) & [Anton Lundgren](https://www.instagram.com/antonlundgreen/)

repository: tiepdotme/wedding-season

repo_name: tiepdotme/wedding-season


text:
# Benchmarks for Neural Network Robustness to Common Distortions and Styles

This repository contains the datasets and some code for the paper _Benchmarks for Neural Network Robustness to Common Distortions and Styles_ by Dan Hendrycks and Tom Dietterich.

Requires Python 3+ and PyTorch 0.3+.

## ImageNet-D

[Download ImageNet-D here.](https://drive.google.com/drive/folders/1HDVw6CmX3HiG0ODFtI75iIfBDxSiSz2K?usp=sharing)

## Icons-50

[Download Icons-50 here.](https://drive.google.com/file/d/1TN5Igft9q01HZOuFlW7e8L1u5ksgVkn-/view?usp=sharing)

## Citation

If you find this useful in your research, please consider citing:

    @article{hendrycks2018robustness,
      title={Benchmarks for Neural Network Robustness to Common Distortions and Styles},
      author={Dan Hendrycks and Thomas Dietterich},
      journal={arXiv preprint},
      year={2018}
    }

repository: ml-lab/robustness

repo_name: ml-lab/robustness


text:
# Examples

To run this examples, do not forget to add `I2Cbus/SPIbus` library path in the Makefile of each example.

+ **MPU-I2C**:
    Setup MPU through I2C for basic usage.

+ **MPU-SPI**:
    Setup MPU through SPI for basic usage.

+ **MPU-Real**:
  A more 'elaborated' example, shows how to:
  \- Use either SPI or I2C in the same code
  \- Use the MPU with interrupt signal
  \- Read sensor data from FIFO
  \- Perform Self-Test check
  \- Calibrate sensor data output using offset registers
  \- Calculate Tilt Angles


text:
Mirage
======
Social Network to discover moments around you. Project totally unfinished! Currently using this
project to architecture and testing experiments. Here are some examples about it's beautiful UX!

![Screenshot 1](/raw/screen1.png)
![Screenshot 2](/raw/screen2.png)
![Screenshot 3](/raw/screen3.png)
![Screenshot 4](/raw/screen4.png)
![Screenshot 5](/raw/screen5.png)
![Screenshot 6](/raw/screen6.png)
![Screenshot 7](/raw/screen7.png)

Developed By
------------
* Jorge Castillo Pérez -<EMAIL_ADDRESS>

License
-------

    Copyright 2015 Jorge Castillo Pérez

    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

repository: ppamorim/Mirage

repo_name: ppamorim/Mirage


text:
# fuzzing_black

A small set of scripts to showcase fuzzing `black` with `python-afl`
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/ambv/black)

## Slides

You can view slides online at https://talks.godoc.org/github.com/dizzy57/fuzzing_black/fuzzing_black.slide

## How to start fuzzing:

1. Split test cases into small chunks with `split_tests_into_corpus.py`.
2. Get python [grammar file](https://raw.githubusercontent.com/python/cpython/master/Grammar/Grammar).
2. Generate dictionary from the grammar with `extract_tokens_from_grammar.py > python.dict`.
3. Set up `PYTHONPATH` environment so that `import black` imports the development version of `black`.
4. Run `py-afl-fuzz -i afl_input/ -o afl_output/ -x python.dict -- python fuzz_persistent.py`.

## Trophies:

1. [Unwrapping multiple parentheses](https://github.com/python/black/issues/836)
2. [Comments and parentheses](https://github.com/python/black/issues/853)
3. [assert (\*x)](https://github.com/python/black/issues/921)
4. [Explicit line join in the first line](https://github.com/python/black/issues/922)

## License

### The [Unlicense](http://unlicense.org):

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

 IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to <http://unlicense.org/>

license: Unlicense


text:
---
layout: default
title: upload(fieldLocator,file)
parent: web
tags: command web
comments: true
---

### Description

- This command is used to upload file in web browser.
- in other words command will upload the file in web browser and pass or else fail otherwise.

### Parameters

- **fieldLocator** - this parameter is the locator of the element on clicking or selecting the windows upload dialog will open.
- **file** - this parameter is the file along with the location which has to be uploaded.

### Example

**Script**:

![](image/upload_01.png)

**Output**:

![](image/upload_02.png)

### See Also

repository: nexiality/documentation

gha_language: JavaScript

repo_name: nexiality/documentation


text:
# Project name

Project description

## Things That May Make You Twitch

### Environment

The environment is set up at `src/main/resources`

`application.properties`: Common environment. The variable `spring.profiles.active` is for selecting the environment

**Available environments:**

- `local`: Local development environment
- `ci`: CI (continuous integration) development environment

## Setting Things Up

### Create db

This project is using MySQL for db

Create new MySQL schema with this SQL command:
```sql
CREATE SCHEMA `new_schema` DEFAULT CHARACTER SET utf8 ;
```

### Change connection setting

File: `resources/application-env.properties`
```properties
spring.datasource.url=jdbc:mysql://localhost:3306/demo_db
spring.datasource.username=root
spring.datasource.password=root
```

### Running Tasks

To get a list of available tasks for a project, run `./gradlew tasks`.

Build project: `./gradlew build`

### Start server

To start a server, run the command:

```bash
$ ./gradlew bootRun
```

### Getting API documentation

Access API-doc with this URL: http://localhost:8080/swagger-ui.html

## Coding guideline

1. Create entity

Create Entity class in `entities` package, extends `BaseEntity`

2. Create repository

Create Repository interface in `repositories` package, extends `JpaRepository<{entity class}, {entity primary key}>`

This repository include CRUD based method

You can create custom sql query in this interface. Reference: [JPA Repositories - Spring](https://docs.spring.io/spring-data/jpa/docs/1.5.0.RELEASE/reference/html/jpa.repositories.html)

3. Create service

Create Service class in `services` package, extends `BaseService<{repository interface}, {entity class}, {entity primary key}>`

This service included basic CRUD method, included get paging list

All business, transaction & error handle is written in this class

4. Create data class

Input class: XXXModels in `models` package. This class include validation annotations, and can convert to entity class

Output class: XXXResponse in `responses` package. This class included formatted output, and can convert from entity class

5. Create controller class

Create Controller class in `controllers` package.

Input of controller method is Model class, output is `ResponseModel<{response class}>`

Basic operations:
```
POST /XXX/add: Insert new item
PUT (or POST) /XXX/update/{id}: Edit item by id
GET /XXX/get/{id}: Get item by id
DELETE (or POST) /XXX/delete/{id}: Delete item by id
GET /XXX/list/{size}/{page}: Get list paging of all items
```


text:
---
layout: default
---

# 1994-11-19 - Re:  Cash

## Header Data

From<EMAIL_ADDRESS><EMAIL_ADDRESS>+1-510-484-6204)

To<EMAIL_ADDRESS>Message Hash: 217bb65840c281076741155d789bfe7cd61c863ef3b02cc709ad12adaa7d3fa4

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1994-11-19 00:20:52 UTC

Raw Date: Fri, 18 Nov 94 16:20:52 PST

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS><EMAIL_ADDRESS>+1-510-484-6204)
Date: Fri, 18 Nov 94 16:20:52 PST
To<EMAIL_ADDRESS>Subject: Re:  Cash
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

> Assuming this is true, it would seem that even good, old fashioned,
> paper currency doesn't provide the level of anonymity that one
> would think.  Scary...

Hasn't really provided it for quite a while, as long as there's an
infrastructure to track serial numbers (you've presumably noticed that
each bill a unique serial number, except for counterfeits and maybe
printing glitches.)  It's quite possible to record the serial numbers of
bills before distributing them in applications such as ransom payments
or drug-buying stings, and wouldn't be too hard, with current scanning
technology, to track them at banks, tax offices, etc.

(Of course, neither AT&T GIS (aka NCR) nor Diebold currently makes
ATMs with serial-number scanners in them, but it wouldn't be hard
to require banks to scan the bills before filling the cash machines.)

During one of the "Government's going to replace our Real American
Greenbacks with Pink(o) Money" scares before the plastic-strip money
arrived, USA Today had an article in their money section showing
dollar bills with bar-codes instead of the Arabic-numeral serial number.

		Bill

{% endraw %}
```

## Thread

+ Return to [November 1994](/archive/1994/11)

+ Return to "[Christian Odhner <cdodhner@PrimeNet.Com>](/authors/christian_odhner_cdodhner_at_primenet_com_)"
+ Return to<EMAIL_ADDRESS><EMAIL_ADDRESS>+1-510-484-6204)](/authors/wcs_at_anchor_ho_att_com_bill_stewart_at_pleasantonca_ncr_com_15104846204_)"

+ 1994-11-19 (Fri, 18 Nov 94 16:20:52 PST) - Re:  Cash -<EMAIL_ADDRESS><EMAIL_ADDRESS>+1-510-484-6204)_
  + 1994-11-28 (Mon, 28 Nov 94 06:46:42 PST) - [Re: Cash](/archive/1994/11/0e6f7ee43e42373b364a768ac61fdea15a95945f5d6ecb10481e9163359f679e) - _Christian Odhner<EMAIL_ADDRESS>


text:
# pxl

A simple framework for making games in Rust.

## Crates

`pxl` consists of a number of crates:

- `pxl`: The library and runtime. Start here!
- `pxl-build`: A compile-time resource loader. Check this out if you want to use static assets, like images and sounds.
- `pxl-build-test`: Tests and usage example for `pxl-build`.

## Building

Since `pxl` programs use per-pixel rendering, building in release mode can yield dramatically improved performance. Do `cargo run --release` to build in release mode.

## Dependencies

The `pxl` runtime plays audio using `cpal`, which requires ALSA headers/libraries on Linux;

On Ubuntu, you can install them with:

```sh
sudo apt install libasound2-dev
```

## Examples

To run one of the examples, type the following:
```sh
cargo run --package pxl --release --example EXAMPLE_NAME
```

To add one of your own examples, place it in pxl/examples and modify pxl/Cargo.toml
to include it.

repository: NQNStudios/pxl

repo_name: NQNStudios/pxl


text:
---
layout: post
title: Multiple Inheritance in C++
subtitle: Best way to inherit.
published: true
categories: other
tags: [C++, Diamond problem, explicit scoping., Inheritance, Multiple Inheritance, Virtual Base class]

bigimg:
  - /img/oldblog/inheritance.jpg

---

## Introduction

 In multiple inheritance a derived class inherits from more than one class.The following figure gives an idea.

Figure 1

 In Figure 1 class D is the derived class and B,C are base classes for it.

Consider the following program:

## Problems with Multiple Inheritance

We will get an error: request for member 'display' is ambiguous.

Why this happens? Think!!!

Let's look how the compiler evaluates the above program:

After creating an object of type D when we call the function display using that object the compiler searches for display function in class D. As the compiler cannot find it then looks to see if any of the base classes have a function named display().

The problem is that 'dobject' actually contains two display() functions: one inherited from class B, and one inherited from class C. Therefore compiler cannot choose between the two and the function call is ambiguous, and will receive a compiler error.

How to solve this problem?

One way is to explicitly mention from which class the method has to be derived. This is known as explicit scoping.

```c++

	dobject.B::display(dobject.d_var);

```

And the output is:

```
	Called from B and value is 40
```

## Diamond Problem

Let's complicate things a bit more. Now have a look at the following figure:

Figure 2

   If the function display is derived from A the program looks like this:

The same problem as in the case of multiple inheritances exists and also adds more problems to it.

The compiler doesn't know whether it should have one or two copies of A and how to resolve such ambiguous references. While these problems can be solved using explicit scoping but the maintenance overhead increases.

If we create object of type D then by default compiler ends up creating two copies of class A. As shown in the figure 3.

Figure 3

Most of the times we want the compiler to create only one copy of class A.

Is it possible?

Yes, it is possible with the help of virtual base classes.

So let's make some changes to the code and make it work.

 And the Output looks like:

```
	Called from A and value is 40
```

Here Class A is constructed only once. Before finishing this topic there are few points to be remembered.

First virtual base classes are created before non-virtual base classes, which ensures all bases get created before their derived classes.

Second, note that the constructors of Classes B and C still have calls to the A's constructor. If we are creating an instance of D, these constructor calls are simply ignored because D is responsible for creating the A, not B or C. However, if we were to create an instance of B or C, the virtual keyword is ignored, those constructor calls would be used, and normal inheritance rules apply.

Third, if a class inherits one or more classes that have virtual parents, the most derived class is responsible for constructing the virtual base class.

This article is taken from my old blog.