TERMS AND CONDITIONS
PLEASE READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THIS SITE.
1.0 General Terms - By browsing and using this website you are agreeing to comply with and be bound by the following Terms and Conditions, which together with our Privacy Policy govern Copify's relationship with you in relation to this website.
1.1 The term 'Copify', 'our', 'us' or 'we' refers to the owner of the website whose registered office is:
Copify Ltd
C/O Scott & Wilkinson
Dalton House
9 Dalton Square
Lancaster
Lancashire
LA1 1WD
England
1.2 Our trading address is:
Copify Ltd
InfoLab21
Lancaster
Lancashire
LA1 4WA
England
1.3 Our company registration number in England is 0715115. The term 'you' refers to the user or viewer of our website.
1.4 The use of this website is subject to the following terms of use:
1.4.1 The content of the pages of this website is for your general information and use only. It is subject to change without notice.
1.4.2 Neither we nor any third parties provide any warranty or guarantee as to the accuracy, timeliness, performance, completeness or suitability of the information and materials found or offered on this website for any particular purpose. You acknowledge that such information and materials may contain inaccuracies or errors and we expressly exclude liability for any such inaccuracies or errors to the fullest extent permitted by law.
1.4.3 Your use of any information or materials on this website is entirely at your own risk, for which we shall not be liable. It shall be your own responsibility to ensure that any products, services or information available through this website meet your specific requirements.
1.4.4 This website contains material which is owned by or licensed to us. This material includes, but is not limited to, the design, layout, look, appearance and graphics. Reproduction is prohibited other than in accordance with the copyright notice, which forms part of these terms and conditions.
1.4.5 All trademarks reproduced in this website, which are not the property of, or licensed to the operator, are acknowledged on the website.
1.4.6 Unauthorised use of this website may give rise to a claim for damages and/or be a criminal offence.
1.4.7 From time to time this website may include links to other websites. These links are provided for your convenience to provide further information. They do not signify that we endorse the website(s). We have no responsibility for the content of the linked website(s).
1.4.8 Your use of this website and any dispute arising out of such use of the website is subject to the laws of England, Scotland and Wales.
1.4.9 By registering as a writer, you consent to being sent order notifications via email. This service can be opted out of at the point of registration, or in the notifications section of the site.
1.4.10 By registering as a client, you consent to being sent email marketing communications by Copify. These emails can be opted out of at any time.
1.4.11 Clients can pay for content orders manually, or subscribe to an automatic recurring billing package. All of these terms apply to both manually placed orders and packages.
1.5 Security and Privacy
1.5.1 We are committed to ensuring that your information is secure. In order to prevent unauthorised access or disclosure, we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect online.
1.6 How we use cookies
1.6.1 We use traffic log cookies to identify which pages are being used. This helps us analyse data about web page traffic and improve our website in order to tailor it to customer needs. We only use this information for statistical analysis purposes and then the data is removed from the system. You can choose to accept or decline cookies. Most web browsers automatically accept cookies, but you can usually modify your browser setting to decline cookies if you prefer. This may prevent you from taking full advantage of the website.
1.7 Controlling your personal information
1.7.1 You may choose to restrict the collection or use of your personal information in the following ways:
1.7.2 Whenever you are asked to fill in a form on the website, look for the box that you can click to indicate that you do not want the information to be used by anybody for direct marketing purposes if you have previously agreed to us using your personal information for direct marketing purposes, you may change your mind at any time by writing to us at our trading address or emailing us at: 'help at copify dot com'
1.7.3 We will not sell, distribute or lease your personal information to third parties unless we have your permission or are required by law to do so.
1.7.4 We may use your personal information to send you promotional information about third parties which we think you may find interesting if you tell us that you wish this to happen. You may request details of personal information which we hold about you under the Data Protection Act 1998. A small fee will be payable. If you would like a copy of the information held on you please write to:
Copify Ltd.
InfoLab21
Lancaster
Lancashire
LA1 4WA
England
1.7.4 If you believe that any information we are holding on you is incorrect or incomplete, please email or write to us as soon as possible, at the above address. We will promptly correct any information found to be incorrect.
1.8 Credit Card Information
1.8.1 Copify use an approved third party merchant to process all credit card payments. We do not store any of this credit card or billing information in our database, in sessions or in browser cookies.
1.8.2 All credit card payments are transmitted using industry standard SSL encryption.
1.9 Pricing
1.9.1 Content orders are priced at 0.03 GBP per word for standard copy and 0.05 GBP per word for professional copy, excluding VAT. Clients are given an exact payment at point of purchase, including VAT and once an order has been placed, can download an invoice for the transaction with a breakdown including VAT.
1.9.2 UK-registered companies, UK-based individuals and clients outside of the UK without a valid EU VAT number who use the service are subject to VAT on all orders at the current UK rate.
1.9.3 The amount of VAT applied to orders is displayed at the checkout, and is also stated in a receipt, which can be downloaded from the dashboard.
1.9.4 Companies based inside the European Union, but outside of the UK, are entitled to pay VAT at their country's standard rate, providing they provide their VAT number by adding it to their profile, and this is verified by the European Union's online tax service (http://ec.europa.eu/taxation_customs/vies/vatRequest.html) before they place any orders.
1.9.5 We cannot offer taxation at a different rate to clients whose VAT registration number is not recognised by this service, or to clients who are based outside of the UK who do not have a VAT number.
1.9.6 Customers who have made purchases before providing us with their Non-UK, EU VAT number are not entitled to any form of rebate on tax that has been paid above their country's standard rate.
1.9.7 We reserve the right to change the prices of orders at any time, without prior warning or consent.
2.0 Delivery Policy
2.1 Content is ordered and delivered to clients through our website. Each order must include specific details about the exact nature of the client's requirements, hereby referred to as a brief. It is the client's responsibility to ensure that the information contained within their brief(s) is an accurate reflection of their requirements. Any disputes arising from content delivered will refer back to this original brief.
2.1.1 At the point of order, customers are given an estimated delivery time when we expect your copy to be delivered. This delivery time is an estimate, not a guarantee.
2.1.2 Once an order has been processed and confirmed, we have made a contract to supply the client with the content, written to the brief outlined in the order as far as can be reasonably interpreted by the writer(s) tasked with writing the copy.
2.1.3 Once an order has been placed, clients cannot change or amend the brief that has been supplied to the writer(s).
2.1.4 Clients can make either open orders, which are available to a pool of writers, or direct orders, where the client specifies a particular writer they would like to write their copy.
2.1.5 Unless an order is placed directly with a specified writer, it is made available to the first available writer(s) at the specified quality level of either standard or professional, with the exception of any writers that the client may have previously prevented from accepting their orders.
2.1.6 We make no guarantee as to the availability of writer(s) specified in direct orders or whether they will accept the order.
2.1.7 Clients can cancel direct orders with a writer at any time.
2.1.8 If a direct order is declined by a writer, clients will be notified and given the option to make the order open to all other writers at the specified quality level. At this point, clients can also edit the brief.
2.1.9 We reserve the right to change the writer(s) tasked with working on an open order at any time, without prior consent.
2.1 Customers are entitled to a refund only after they have followed the dispute resolution process outlined in section 7.
2.2 Item return/refund policy
2.2.1 Customers are entitled to a refund only after they have followed the dispute resolution process outlined in section 7.
2.2.2 All refund requests must be made within 60 days of payment, any requests made after this time will not be considered.
2.2.3 We accept no responsibility to refund credit on client accounts from payments made erroneously.
2.3 Order Cancellation
2.3.1 We reserve the right to cancel any orders that contain references to defamatory, illegal or offensive material.
2.3.2 We reserve the right to cancel any orders that are intended for academic purposes.
2.3.3 Orders cancelled for the above reasons will be refunded in full and the client will be notified by email.
2.3.4 Refunds must be requested within the timeframe permitted by our payment provider.
2.3.5 Refund payments must be issued through the same payment method as they were made.
2.3.6 We reserve the right to close the accounts of individuals we suspect of making fraudulent or suspicious payments.
3 Writer Policy
3.1 All writers who register a writer account on the site are bound by the following conditions.
3.2 The ability of writers to accept orders is at our discretion and is subject to change at any time without prior notice or consent.
3.3 When submitting completed copy, writers agree that they are handing over legal copyright to the client and they must not publish the copy elsewhere in whole, or in part, either in print or online.
3.4 When accepting an order, writers are bound by the deadline that is stated in the brief. It is the writer's responsibility to ensure that the copy is submitted before this time, otherwise they will lose ownership of this order. We are under no obligation to pay for any copy that is written but not submitted before this deadline.
3.4.1 Once an order is completed, writers are responsible for making any edits and additions that may be requested by the client within a period of 30 days from completion of the order. If the writer is unwilling or unable to make these requests, they must notify us by email at 'help at copify dot com.'
3.4.2 Failure to make further edits and additions may result in the order being issued to another writer without notice or consent.
3.4.3 We reserve the right to withhold payment for orders should the writer not action reasonable changes requested by the client.
3.5 If a writer does not submit copy before an order deadline, they are required to email 'help at copify dot com' and state the reasons why. It is then at our discretion as to whether or not the writer will be able to continue to accept orders.
3.6 Payment for work completed is issued to a holding account once the work has been approved by the client. This money can then be withdrawn, with payments issued daily at 2pm GMT.
3.6.1 Payment for work is issued through PayPal. It is the writer's responsibility to ensure that they have access to a PayPal account in order to receive this payment.
3.6.2 Copify accepts no responsibility to payments that are missed due to incorrect PayPal account information being entered by writers.
3.7 By registering as a writer you consent to being sent communications by Copify and selected third parties.
3.8 It is the writer's responsibility to ensure that they have all of the information they need to create the copy to the specification outlined by the client prior to accepting an order. We are under no obligation to change deadlines and accept no liability for loss of earnings due to misinterpretation or understanding of this specification.
3.9 We reserve the right to reject copy that is deemed to be unfit for purpose. Should this occur we also reserve the right to withhold payment for the order.
4. Confidential Disclosure Agreement / NDA for writers
4.1 Registered writers are bound by the following confidentiality agreement.
4.2 All of the information contained within orders briefs and any attached documents is presented to writers in confidence. It is agreed that all such information shall be treated as strictly confidential by the receiving party and will not be disclosed to any third party, copied, reproduced, adapted, divulged, published or circulated in whole or in part, or combined with any other information.
4.3 The receiving party undertakes not to use the information for any purpose, other than to assist with the creation of content, as commissioned by Copify Ltd, without obtaining the written agreement of the disclosing party.
4.4 This Agreement does not apply to any information in the public domain or which the receiving party can show was either already lawfully in their possession prior to its disclosure by the other party or acquired without the involvement, either directly or indirectly, of the disclosing party.
4.5 Either party to this Agreement shall on request from the other return any documents or items connected with the disclosure and shall not retain any unauthorised copies or likenesses.
5. Messaging
5.1 The internal messaging system is intended for the purposes of essential client-writer communication relating to issues concerning specific orders on the site only.
5.2 Any attempts to solicit contact outside of the site, including but not limited to email, telephone, Skype and instant messaging services may result in a writer's account being terminated. This is at our discretion.
5.3 We reserve the right to pursue legal action for loss of earnings or damages against writers or clients who breach points 5.1 and 5.2.
6 API
6.1 Customers may use the Copify API to order content through third-party applications. Use of this API is bound by all of the prior terms and condition, plus the following specific terms.
6.2 Violation of these terms will result in a revoke of your API Key. Copify shall not be liable for any direct or indirect damages caused, including but not limited to, loss of profit, goodwill, use, data or other intangible losses, resulting from your use of the API or third-party products that access data via the API.
6.3 We reserve the right to revoke API keys at any time, at our sole discretion.
6.4 Users of the API must be a human. Accounts registered by "bots" or other automated methods are not permitted.
6.5 You are responsible for maintaining the integrity and security of your account and the subsequent use of your API key. We are not liable for any losses or damage caused by unauthorised usage of the API.
6.6 Abuse of, or excessively frequent requests to Copify via the API may result in the temporary or permanent suspension of your account's access to the API. This is at our discretion.
6.7 Copify reserves the right to at any time modify or discontinue, temporarily or permanently, the API Service (or any part thereof) with or without notice.
6.8 Copify reserves the right to change the cost of work ordered through the site at any time. It is the responsibility of publishers to make sure they are aware of current pricing before using the API to order content. Full details of the method for checking current prices are included in the API documentation.
6.9 The ordering of content through the API is dependent on users having sufficient balance in their account to cover the cost of content ordered.
6.10 Technical support for the API is available via email at the address: 'help at copify dot com'. Copify cannot guarantee a response to all queries.
7 Dispute Resolution Process
7.1 Copify will mediate all disputes arising between clients and writers and will endeavour to resolve these disputes and agree on a satisfactory outcome for all parties. If clients are unhappy with an order that has been delivered to them, they must follow this procedure before any further action can be taken. We reserve the right to uphold or reject complaints at our sole discretion.
7.2 In the first instance, clients who are unhappy with an order must offer the writer the opportunity to amend the copy based on feedback. This feedback must be clear, concise and objective.
7.2.1 If, once the writer has amended the copy, the client is still unhappy, they should escalate the case with the Copify support team by emailing 'help at copify dot com' with the order ID and details of their objections.
7.2.2 The Copify support team will review the brief issued by the the client, the copy and any communication between the two parties. If it is felt that the copy does not meet the specification of the client outlined in this brief, in the first instance they will be offered the opportunity to make their order available to another writer free of charge. If it is deemed that the copy matches the specification outlined in the first instance then we reserve the right to reject the complaint.
7.2.3 If the client is unwilling to have their copy written by another writer, we will refund the cost of their order, in full, providing this request is made no more than 60 days after the order is placed.
8 Blog Package Terms and Conditions
8.1 Clients who sign up for a blog package are bound by the following terms and conditions.
8.2 After signing up, clients will be billed for and receive the requested number of blog posts within one calendar month. They will be billed the same amount every calendar month and receive the same agreed number of blog posts until they change or cancel their subscription through the Copify website.
8.2.1 We reserve the right change the monthly billing amount of blog packages at any time, with our prior warning or consent.
8.2.2 The billing amount paid by clients includes VAT charged at the standard UK rate of 20%. Clients outside of the UK who are VAT registered within the E.U. are eligible to be billed for a blog package at their country's rate of taxation, providing they supply their company details and VAT registration number before they sign up for a package, and they ensure that the package they subscribe to is a custom package, which can be created at the following page: https://uk.copify.com/packages/tools. VAT information must be entered in the Profile section of user accounts under the 'Billing' tab. Copify is not liable to issue rebates to clients who sign up for standard blog packages or those who enter VAT information after signing up for a blog package.
8.3 Cancellation requests must be issued before the date of the client’s billing cycle, otherwise clients are liable for another month of billing and service delivery.
8.4 Clients can change their package at any time, providing this is before their monthly billing date. Requests made on this date may not be actioned until the following month.
8.5 It is the client’s responsibility to ensure that the information concerning their required blog posts is correct. Copify is not liable for mistakes arising from either misinformation, or a lack of information provided by the client.
8.6 Copify reserves the right to embellish information supplied by clients for the purposes of supplying writers with an adequate brief to write blog posts.
8.7 Copify will supply all posts in a number of formats for clients to download and publish to their blogs but accepts no responsibility for compatibility issues which may arise from unsupported platforms or content management systems.
8.7.1 Blog package clients can select an 'auto-publish' option, which enables posts to be pushed live directly to their blog.
<IP_ADDRESS> Clients who select this option consent to posts being published directly to their site with an image of our choice. Whilst every effort is made to ensure that the information and image contained in these posts is accurate and free from mistakes, Copify accepts no responsibility or liability for text or images which are deemed by clients to be inappropriate, inaccurate or offensive.
<IP_ADDRESS> Clients also consent to approve orders which are auto-published instantly, which means that once live, they wave the right to request any edits to these posts once they have been published on their blog.
8.8 Should payment be missed due to lack of funds, credit/debit card expiration or any other reason, Copify will notify the client by email and offer them the opportunity to update their billing details. Until such a time as new, correct information is issued by the client, blog posts will cease to be delivered.
8.8.1 If new billing details are entered, a new billing cycle will begin from that date.
8.9 Clients who are unhappy with orders that are delivered to them must follow the dispute resolution process, as outlined in section 7.
9 WordPress Plugin
9.1 Clients who use the Copify WordPress plugin are bound by the following terms and conditions.
9.2 Those using the Copify WordPress plugin do so at their own risk. It is the client's responsibility to carefully check all content that is published on their site. Copify accepts no responsibility for mistakes, inaccurate information or content that is deemed to be inappropriate or offensive.
9.3 Copify accepts no responsibility for technical issues, caused either by internal or external systems and their compatibility, or lack thereof, with the WordPress plugin.
9.4 It is the responsibility of clients to ensure that they have installed the latest version of the Copify WordPress plugin. Copify accepts no responsibility for lack of functionality, or issues caused as a result of clients who have an obsolete version of the plugin installed on their site.
1.0 General Terms - By browsing and using this website you are agreeing to comply with and be bound by the following Terms and Conditions, which together with our Privacy Policy govern Copify's relationship with you in relation to this website.
1.1 The term 'Copify', 'our', 'us' or 'we' refers to the owner of the website whose registered office is:
Copify Ltd
C/O Scott & Wilkinson
Dalton House
9 Dalton Square
Lancaster
Lancashire
LA1 1WD
England
1.2 Our trading address is:
Copify Ltd
InfoLab21
Lancaster
Lancashire
LA1 4WA
England
1.3 Our company registration number in England is 0715115. The term 'you' refers to the user or viewer of our website.
1.4 The use of this website is subject to the following terms of use:
1.4.1 The content of the pages of this website is for your general information and use only. It is subject to change without notice.
1.4.2 Neither we nor any third parties provide any warranty or guarantee as to the accuracy, timeliness, performance, completeness or suitability of the information and materials found or offered on this website for any particular purpose. You acknowledge that such information and materials may contain inaccuracies or errors and we expressly exclude liability for any such inaccuracies or errors to the fullest extent permitted by law.
1.4.3 Your use of any information or materials on this website is entirely at your own risk, for which we shall not be liable. It shall be your own responsibility to ensure that any products, services or information available through this website meet your specific requirements.
1.4.4 This website contains material which is owned by or licensed to us. This material includes, but is not limited to, the design, layout, look, appearance and graphics. Reproduction is prohibited other than in accordance with the copyright notice, which forms part of these terms and conditions.
1.4.5 All trademarks reproduced in this website, which are not the property of, or licensed to the operator, are acknowledged on the website.
1.4.6 Unauthorised use of this website may give rise to a claim for damages and/or be a criminal offence.
1.4.7 From time to time this website may include links to other websites. These links are provided for your convenience to provide further information. They do not signify that we endorse the website(s). We have no responsibility for the content of the linked website(s).
1.4.8 Your use of this website and any dispute arising out of such use of the website is subject to the laws of England, Scotland and Wales.
1.4.9 By registering as a writer, you consent to being sent order notifications via email. This service can be opted out of at the point of registration, or in the notifications section of the site.
1.4.10 By registering as a client, you consent to being sent email marketing communications by Copify. These emails can be opted out of at any time.
1.4.11 Clients can pay for content orders manually, or subscribe to an automatic recurring billing package. All of these terms apply to both manually placed orders and packages.
1.5 Security and Privacy
1.5.1 We are committed to ensuring that your information is secure. In order to prevent unauthorised access or disclosure, we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect online.
1.6 How we use cookies
1.6.1 We use traffic log cookies to identify which pages are being used. This helps us analyse data about web page traffic and improve our website in order to tailor it to customer needs. We only use this information for statistical analysis purposes and then the data is removed from the system. You can choose to accept or decline cookies. Most web browsers automatically accept cookies, but you can usually modify your browser setting to decline cookies if you prefer. This may prevent you from taking full advantage of the website.
1.7 Controlling your personal information
1.7.1 You may choose to restrict the collection or use of your personal information in the following ways:
1.7.2 Whenever you are asked to fill in a form on the website, look for the box that you can click to indicate that you do not want the information to be used by anybody for direct marketing purposes if you have previously agreed to us using your personal information for direct marketing purposes, you may change your mind at any time by writing to us at our trading address or emailing us at: 'help at copify dot com'
1.7.3 We will not sell, distribute or lease your personal information to third parties unless we have your permission or are required by law to do so.
1.7.4 We may use your personal information to send you promotional information about third parties which we think you may find interesting if you tell us that you wish this to happen. You may request details of personal information which we hold about you under the Data Protection Act 1998. A small fee will be payable. If you would like a copy of the information held on you please write to:
Copify Ltd.
InfoLab21
Lancaster
Lancashire
LA1 4WA
England
1.7.4 If you believe that any information we are holding on you is incorrect or incomplete, please email or write to us as soon as possible, at the above address. We will promptly correct any information found to be incorrect.
1.8 Credit Card Information
1.8.1 Copify use an approved third party merchant to process all credit card payments. We do not store any of this credit card or billing information in our database, in sessions or in browser cookies.
1.8.2 All credit card payments are transmitted using industry standard SSL encryption.
1.9 Pricing
1.9.1 Content orders are priced at 0.03 GBP per word for standard copy and 0.05 GBP per word for professional copy, excluding VAT. Clients are given an exact payment at point of purchase, including VAT and once an order has been placed, can download an invoice for the transaction with a breakdown including VAT.
1.9.2 UK-registered companies, UK-based individuals and clients outside of the UK without a valid EU VAT number who use the service are subject to VAT on all orders at the current UK rate.
1.9.3 The amount of VAT applied to orders is displayed at the checkout, and is also stated in a receipt, which can be downloaded from the dashboard.
1.9.4 Companies based inside the European Union, but outside of the UK, are entitled to pay VAT at their country's standard rate, providing they provide their VAT number by adding it to their profile, and this is verified by the European Union's online tax service (http://ec.europa.eu/taxation_customs/vies/vatRequest.html) before they place any orders.
1.9.5 We cannot offer taxation at a different rate to clients whose VAT registration number is not recognised by this service, or to clients who are based outside of the UK who do not have a VAT number.
1.9.6 Customers who have made purchases before providing us with their Non-UK, EU VAT number are not entitled to any form of rebate on tax that has been paid above their country's standard rate.
1.9.7 We reserve the right to change the prices of orders at any time, without prior warning or consent.
2.0 Delivery Policy
2.1 Content is ordered and delivered to clients through our website. Each order must include specific details about the exact nature of the client's requirements, hereby referred to as a brief. It is the client's responsibility to ensure that the information contained within their brief(s) is an accurate reflection of their requirements. Any disputes arising from content delivered will refer back to this original brief.
2.1.1 At the point of order, customers are given an estimated delivery time when we expect your copy to be delivered. This delivery time is an estimate, not a guarantee.
2.1.2 Once an order has been processed and confirmed, we have made a contract to supply the client with the content, written to the brief outlined in the order as far as can be reasonably interpreted by the writer(s) tasked with writing the copy.
2.1.3 Once an order has been placed, clients cannot change or amend the brief that has been supplied to the writer(s).
2.1.4 Clients can make either open orders, which are available to a pool of writers, or direct orders, where the client specifies a particular writer they would like to write their copy.
2.1.5 Unless an order is placed directly with a specified writer, it is made available to the first available writer(s) at the specified quality level of either standard or professional, with the exception of any writers that the client may have previously prevented from accepting their orders.
2.1.6 We make no guarantee as to the availability of writer(s) specified in direct orders or whether they will accept the order.
2.1.7 Clients can cancel direct orders with a writer at any time.
2.1.8 If a direct order is declined by a writer, clients will be notified and given the option to make the order open to all other writers at the specified quality level. At this point, clients can also edit the brief.
2.1.9 We reserve the right to change the writer(s) tasked with working on an open order at any time, without prior consent.
2.1 Customers are entitled to a refund only after they have followed the dispute resolution process outlined in section 7.
2.2 Item return/refund policy
2.2.1 Customers are entitled to a refund only after they have followed the dispute resolution process outlined in section 7.
2.2.2 All refund requests must be made within 60 days of payment, any requests made after this time will not be considered.
2.2.3 We accept no responsibility to refund credit on client accounts from payments made erroneously.
2.3 Order Cancellation
2.3.1 We reserve the right to cancel any orders that contain references to defamatory, illegal or offensive material.
2.3.2 We reserve the right to cancel any orders that are intended for academic purposes.
2.3.3 Orders cancelled for the above reasons will be refunded in full and the client will be notified by email.
2.3.4 Refunds must be requested within the timeframe permitted by our payment provider.
2.3.5 Refund payments must be issued through the same payment method as they were made.
2.3.6 We reserve the right to close the accounts of individuals we suspect of making fraudulent or suspicious payments.
3 Writer Policy
3.1 All writers who register a writer account on the site are bound by the following conditions.
3.2 The ability of writers to accept orders is at our discretion and is subject to change at any time without prior notice or consent.
3.3 When submitting completed copy, writers agree that they are handing over legal copyright to the client and they must not publish the copy elsewhere in whole, or in part, either in print or online.
3.4 When accepting an order, writers are bound by the deadline that is stated in the brief. It is the writer's responsibility to ensure that the copy is submitted before this time, otherwise they will lose ownership of this order. We are under no obligation to pay for any copy that is written but not submitted before this deadline.
3.4.1 Once an order is completed, writers are responsible for making any edits and additions that may be requested by the client within a period of 30 days from completion of the order. If the writer is unwilling or unable to make these requests, they must notify us by email at 'help at copify dot com.'
3.4.2 Failure to make further edits and additions may result in the order being issued to another writer without notice or consent.
3.4.3 We reserve the right to withhold payment for orders should the writer not action reasonable changes requested by the client.
3.5 If a writer does not submit copy before an order deadline, they are required to email 'help at copify dot com' and state the reasons why. It is then at our discretion as to whether or not the writer will be able to continue to accept orders.
3.6 Payment for work completed is issued to a holding account once the work has been approved by the client. This money can then be withdrawn, with payments issued daily at 2pm GMT.
3.6.1 Payment for work is issued through PayPal. It is the writer's responsibility to ensure that they have access to a PayPal account in order to receive this payment.
3.6.2 Copify accepts no responsibility to payments that are missed due to incorrect PayPal account information being entered by writers.
3.7 By registering as a writer you consent to being sent communications by Copify and selected third parties.
3.8 It is the writer's responsibility to ensure that they have all of the information they need to create the copy to the specification outlined by the client prior to accepting an order. We are under no obligation to change deadlines and accept no liability for loss of earnings due to misinterpretation or understanding of this specification.
3.9 We reserve the right to reject copy that is deemed to be unfit for purpose. Should this occur we also reserve the right to withhold payment for the order.
4. Confidential Disclosure Agreement / NDA for writers
4.1 Registered writers are bound by the following confidentiality agreement.
4.2 All of the information contained within orders briefs and any attached documents is presented to writers in confidence. It is agreed that all such information shall be treated as strictly confidential by the receiving party and will not be disclosed to any third party, copied, reproduced, adapted, divulged, published or circulated in whole or in part, or combined with any other information.
4.3 The receiving party undertakes not to use the information for any purpose, other than to assist with the creation of content, as commissioned by Copify Ltd, without obtaining the written agreement of the disclosing party.
4.4 This Agreement does not apply to any information in the public domain or which the receiving party can show was either already lawfully in their possession prior to its disclosure by the other party or acquired without the involvement, either directly or indirectly, of the disclosing party.
4.5 Either party to this Agreement shall on request from the other return any documents or items connected with the disclosure and shall not retain any unauthorised copies or likenesses.
5. Messaging
5.1 The internal messaging system is intended for the purposes of essential client-writer communication relating to issues concerning specific orders on the site only.
5.2 Any attempts to solicit contact outside of the site, including but not limited to email, telephone, Skype and instant messaging services may result in a writer's account being terminated. This is at our discretion.
5.3 We reserve the right to pursue legal action for loss of earnings or damages against writers or clients who breach points 5.1 and 5.2.
6 API
6.1 Customers may use the Copify API to order content through third-party applications. Use of this API is bound by all of the prior terms and condition, plus the following specific terms.
6.2 Violation of these terms will result in a revoke of your API Key. Copify shall not be liable for any direct or indirect damages caused, including but not limited to, loss of profit, goodwill, use, data or other intangible losses, resulting from your use of the API or third-party products that access data via the API.
6.3 We reserve the right to revoke API keys at any time, at our sole discretion.
6.4 Users of the API must be a human. Accounts registered by "bots" or other automated methods are not permitted.
6.5 You are responsible for maintaining the integrity and security of your account and the subsequent use of your API key. We are not liable for any losses or damage caused by unauthorised usage of the API.
6.6 Abuse of, or excessively frequent requests to Copify via the API may result in the temporary or permanent suspension of your account's access to the API. This is at our discretion.
6.7 Copify reserves the right to at any time modify or discontinue, temporarily or permanently, the API Service (or any part thereof) with or without notice.
6.8 Copify reserves the right to change the cost of work ordered through the site at any time. It is the responsibility of publishers to make sure they are aware of current pricing before using the API to order content. Full details of the method for checking current prices are included in the API documentation.
6.9 The ordering of content through the API is dependent on users having sufficient balance in their account to cover the cost of content ordered.
6.10 Technical support for the API is available via email at the address: 'help at copify dot com'. Copify cannot guarantee a response to all queries.
7 Dispute Resolution Process
7.1 Copify will mediate all disputes arising between clients and writers and will endeavour to resolve these disputes and agree on a satisfactory outcome for all parties. If clients are unhappy with an order that has been delivered to them, they must follow this procedure before any further action can be taken. We reserve the right to uphold or reject complaints at our sole discretion.
7.2 In the first instance, clients who are unhappy with an order must offer the writer the opportunity to amend the copy based on feedback. This feedback must be clear, concise and objective.
7.2.1 If, once the writer has amended the copy, the client is still unhappy, they should escalate the case with the Copify support team by emailing 'help at copify dot com' with the order ID and details of their objections.
7.2.2 The Copify support team will review the brief issued by the the client, the copy and any communication between the two parties. If it is felt that the copy does not meet the specification of the client outlined in this brief, in the first instance they will be offered the opportunity to make their order available to another writer free of charge. If it is deemed that the copy matches the specification outlined in the first instance then we reserve the right to reject the complaint.
7.2.3 If the client is unwilling to have their copy written by another writer, we will refund the cost of their order, in full, providing this request is made no more than 60 days after the order is placed.
8 Blog Package Terms and Conditions
8.1 Clients who sign up for a blog package are bound by the following terms and conditions.
8.2 After signing up, clients will be billed for and receive the requested number of blog posts within one calendar month. They will be billed the same amount every calendar month and receive the same agreed number of blog posts until they change or cancel their subscription through the Copify website.
8.2.1 We reserve the right change the monthly billing amount of blog packages at any time, with our prior warning or consent.
8.2.2 The billing amount paid by clients includes VAT charged at the standard UK rate of 20%. Clients outside of the UK who are VAT registered within the E.U. are eligible to be billed for a blog package at their country's rate of taxation, providing they supply their company details and VAT registration number before they sign up for a package, and they ensure that the package they subscribe to is a custom package, which can be created at the following page: https://uk.copify.com/packages/tools. VAT information must be entered in the Profile section of user accounts under the 'Billing' tab. Copify is not liable to issue rebates to clients who sign up for standard blog packages or those who enter VAT information after signing up for a blog package.
8.3 Cancellation requests must be issued before the date of the client’s billing cycle, otherwise clients are liable for another month of billing and service delivery.
8.4 Clients can change their package at any time, providing this is before their monthly billing date. Requests made on this date may not be actioned until the following month.
8.5 It is the client’s responsibility to ensure that the information concerning their required blog posts is correct. Copify is not liable for mistakes arising from either misinformation, or a lack of information provided by the client.
8.6 Copify reserves the right to embellish information supplied by clients for the purposes of supplying writers with an adequate brief to write blog posts.
8.7 Copify will supply all posts in a number of formats for clients to download and publish to their blogs but accepts no responsibility for compatibility issues which may arise from unsupported platforms or content management systems.
8.7.1 Blog package clients can select an 'auto-publish' option, which enables posts to be pushed live directly to their blog.
<IP_ADDRESS> Clients who select this option consent to posts being published directly to their site with an image of our choice. Whilst every effort is made to ensure that the information and image contained in these posts is accurate and free from mistakes, Copify accepts no responsibility or liability for text or images which are deemed by clients to be inappropriate, inaccurate or offensive.
<IP_ADDRESS> Clients also consent to approve orders which are auto-published instantly, which means that once live, they wave the right to request any edits to these posts once they have been published on their blog.
8.8 Should payment be missed due to lack of funds, credit/debit card expiration or any other reason, Copify will notify the client by email and offer them the opportunity to update their billing details. Until such a time as new, correct information is issued by the client, blog posts will cease to be delivered.
8.8.1 If new billing details are entered, a new billing cycle will begin from that date.
8.9 Clients who are unhappy with orders that are delivered to them must follow the dispute resolution process, as outlined in section 7.
9 WordPress Plugin
9.1 Clients who use the Copify WordPress plugin are bound by the following terms and conditions.
9.2 Those using the Copify WordPress plugin do so at their own risk. It is the client's responsibility to carefully check all content that is published on their site. Copify accepts no responsibility for mistakes, inaccurate information or content that is deemed to be inappropriate or offensive.
9.3 Copify accepts no responsibility for technical issues, caused either by internal or external systems and their compatibility, or lack thereof, with the WordPress plugin.
9.4 It is the responsibility of clients to ensure that they have installed the latest version of the Copify WordPress plugin. Copify accepts no responsibility for lack of functionality, or issues caused as a result of clients who have an obsolete version of the plugin installed on their site.
Questions?
Speak to our content team
Fill in the form with your requirements and one of our friendly team will be in touch.


Football: Real Madrid winger Vazquez breaks toe in dumbbell accident
MADRID: Real Madrid winger Lucas Vazquez has broken his toe, the club announced on Thursday (Nov 21).
Vazquez sustained the injury after dropping a dumbbell on his foot in the gym, according to reports in the Spanish press.
"After tests done today on our player Lucas Vazquez, the medical services of Real Madrid have diagnosed him with a fracture in the big toe of his left foot," read a club statement.
Madrid have not specified how long Vazquez will need to recover.
The Spaniard had just returned from a calf injury, which had kept him out for almost six weeks.


There are startling similarities to be found in the film characters John McClane in Die Hard and Ellen Ripley in Alien. In particular,
both have formative traumatic experiences in air ducts: arguably, both heroines are born within the air ducts.
Just one of many nuggets of wisdom scattered throughout “Making fists with your toes: Towards a feminist analysis of Die Hard”, an essay by Zoe Stavri, aka Another Angry Woman. Make sure you read it before watching that magnificent film for the umpteenth time.
Thanks to Roberta Mock for drawing this to my attention.


@(funName: String)
A DataFrame is a distributed collection of data, which is organized into named columns. Conceptually, it is equivalent to relational tables with good optimization techniques. A DataFrame can be constructed from an array of different sources such as Hive tables, Structured Data files, external databases, or existing RDDs. Here we are using JSON document named cars.json with the following content and generate a table based on the schema in the JSON document.
def overview = Action {
Ok(views.html.spark_overview("Your new application is ready."))
}


Portfolio
More
Projects
Home
Contact
Skill Sets
Django (Python)
Flask (Python)
React
Angular
Javascript
Html / Css
Graphics Design(Ai | Ps)
Django
Html
Css
Graphics
Angular
Flask
Css
Javascript
React


Verification Results¶
This page summarizes sample results from the testbed runs with the emphasis on verifying the estimated loss ratios by hand-calculations.
Building Inventory¶
From the entire building inventory, 98 buildings are randomly selected
(examples are shown in sample_table
and the full inventory can be accessed
here).
scatter_matrix
shows the data distributions of the built year, surface
roughness (i.e., Terrain), roof shape, number of stories, and occupancy class.
ID |
RoofShape |
FloodZone |
Area |
Longitude |
Latitude |
Terrain |
DWSII |
BuildingType |
OccupancyClass |
AvgJanTemp |
Garage |
RoofSlope |
NumberofStories |
MeanRoofHt |
YearBuilt |
1 |
Gable |
X |
478 |
-93.24 |
30.14 |
76 |
133.1 |
Wood |
RES1 |
Above |
1 |
0.03 |
1 |
12.6 |
1991 |
2 |
Gable |
X |
358 |
-93.24 |
30.14 |
24 |
133.1 |
Wood |
RES1 |
Above |
1 |
0.07 |
1 |
13.3 |
1992 |
3 |
Gable |
X |
292 |
-93.24 |
30.13 |
76 |
133.3 |
Wood |
RES1 |
Above |
1 |
0.31 |
2 |
29.6 |
1987 |
4 |
Gable |
X |
151 |
-93.24 |
30.14 |
76 |
133.2 |
Wood |
RES1 |
Above |
0 |
0.11 |
1 |
14 |
1990 |
5 |
Gable |
X |
519 |
-93.24 |
30.13 |
76 |
133.2 |
Wood |
RES1 |
Above |
0 |
0.07 |
1 |
13.2 |
1988 |
6 |
Hip |
X |
559 |
-93.24 |
30.14 |
76 |
133.1 |
Wood |
RES1 |
Above |
0 |
0.1 |
1 |
13.7 |
1989 |
7 |
Hip |
X |
427 |
-93.24 |
30.14 |
76 |
133.2 |
Wood |
RES1 |
Above |
1 |
0.22 |
1 |
15.9 |
1988 |
8 |
Hip |
X |
607 |
-93.24 |
30.14 |
76 |
133.1 |
Wood |
RES1 |
Above |
1 |
0.26 |
1 |
16.7 |
1990 |
9 |
Hip |
X |
544 |
-93.24 |
30.14 |
24 |
133.1 |
Wood |
RES1 |
Above |
0 |
0.16 |
1 |
14.9 |
1989 |
10 |
Gable |
X |
469 |
-93.24 |
30.13 |
76 |
133.2 |
Wood |
RES1 |
Above |
1 |
0.06 |
1 |
13 |
1990 |
11 |
Hip |
X |
458 |
-93.24 |
30.14 |
76 |
133.2 |
Wood |
RES1 |
Above |
0 |
0.14 |
1 |
14.6 |
1988 |
12 |
Hip |
X |
742 |
-93.24 |
30.14 |
24 |
133.1 |
Wood |
RES1 |
Above |
0 |
0.25 |
1 |
16.5 |
1992 |
13 |
Gable |
X |
524 |
-93.24 |
30.13 |
76 |
133.2 |
Wood |
RES1 |
Above |
0 |
0.17 |
2 |
27 |
1988 |
14 |
Gable |
X |
442 |
-93.24 |
30.14 |
76 |
133.1 |
Wood |
RES1 |
Above |
0 |
0.24 |
1 |
16.4 |
1991 |
15 |
Flat |
X |
515 |
-93.24 |
30.14 |
76 |
133.1 |
Wood |
RES1 |
Above |
0 |
0 |
1 |
12 |
1992 |
16 |
Gable |
X |
453 |
-93.24 |
30.13 |
76 |
133.3 |
Wood |
RES1 |
Above |
0 |
0.19 |
2 |
27.4 |
1989 |
17 |
Gable |
X |
455 |
-93.24 |
30.13 |
21 |
133.2 |
Wood |
RES1 |
Above |
0 |
0.06 |
1 |
13.1 |
1988 |
18 |
Hip |
X |
378 |
-93.24 |
30.14 |
76 |
133.1 |
Wood |
RES1 |
Above |
1 |
0.14 |
1 |
14.6 |
1987 |
19 |
Gable |
X |
507 |
-93.24 |
30.13 |
21 |
133.2 |
Wood |
RES1 |
Above |
0 |
0.32 |
1 |
17.8 |
1988 |
20 |
Gable |
X |
605 |
-93.24 |
30.14 |
21 |
133.1 |
Wood |
RES1 |
Above |
0 |
0.28 |
1 |
17 |
1987 |
Hand Calculation¶
Hand calculations of wind loss ratios are conducted using the input building information and intensity measures for the sampled buildings. Note that there are two major processes in the damage and loss assessment: (1) translating the building inventory to corresponding HAZUS building classes and (2) estimating the damage and loss given the HAZUS building class and the intensity measure (i.e., PWS in this testbed) for each building. The first process will be discussed in Verification of Rulesets. The second process is the addressed by this section with key steps:
Mapping the building inventory to HAZUS building classes using the AssetRepresentationRulesets
Fetching the individual damage fragilities and loss ratios for each building given its HAZUS building class
Sampling the PWS from nearby grid sites
Evaluating the damage states and average loss ratio given the damage and loss functions as well as the sampled PWS
Following these steps, hand_calc
compares the hand-calculated loss ratios and the simulated
results, which are in good agreement.
Verification of Rulesets¶
Following the discussion in the previous section, this section would discuss the verification process for the Rulesets introduced in Asset Representation. This verification includes two aspects: (1) verifying the implementation of Rulesets and (2) verifying the influence of rulesets. The first aspect is addressed by the pytest module in the AssetRepresentationRulesets. Each pytest examines a set of rulesets for a specific HAZUS building class to see if the resulting HAZUS classifier is as expected. The second aspect involves examinations of damage and loss results from the testbed to investigate the influence of a specific building attribute on the building performance, i.e., if the results is rational then the corresponding rulesets are verified. As an example of this process, the construction year (YearBuilt) is focused in this section.
In order to investigate the cause and rationalize potential influence of year built, a parametric study is conducted for
a single-family house (ID = 2 in bldg_inv_lc
). The original building record is expanded to 51 different buildings
by varying the year built only (i.e., from 1970 to 2020). For each building, expected loss ratio is estimated with 50
realizations to consider the uncertainty from the random sampling in the rulesets. The black curves in year_built_infl
plots the individual realizations of expected loss ratio against different year built values. The red curve shows the mean value
based on the 50 realizations at each year built. It is clear to see that the building
performance improves following major code revisions. For example, labeled by the yellow dashed line at 2000, the IRC 2000-2009
requires 8d nails (with spacing 6”/6”) for sheathing thickness of 1” (as default in this testbed) for basic wind speeds greater than
100 mph which enhances the building performance (reducing the loss ratio); while this ultimate wind speed is increased to 130 mph (just
above the DWSII of the building) after 2016 accepting the use of spacing to 6”/12” which in turns slightly degrades the
building performance. This observation highlights the particular importance of nail spacing requirements for sheathing in
reducing wind-induced losses for this class of building.
A similar study is also conducted for a multi-unit wood building (i.e., WMUH1) with year of construction varying from 1970 to 2020.
For each building, expected loss ratio is estimated with 50 realizations to consider the uncertainty from the random sampling in the rulesets.
year_built_infl_wmuh1
plots individual realizations of expected loss ratio in black and average in red. Two year divisions (1987 and 2000) are noticed where buildings are
estimated to have different performances. Further investigating the cause of this trend indicates that the building from 1988 to 2000 are classified
by our ruleset to have the second water resistance (SWR) given the roof slope is less than 0.33, whereas for the pre-1988 and post-2000 buildings
random samplings are conducted to assign SWR to the building by chances (30% for pre-1988 and 60% for post-2000, which also explains that on average
the expected loss after 2000 is lower than the expected loss before 1988).


---
layout: index
title: Elusive Truth - The Travel Chronicle
---
{% include header_new.html %}
What's this all about?
Well that's the question isn't it? Answer that question and you'll be able to
solve all the world's problems. Or maybe not. I sure don't
know the answer, so you won't find it here.
Woah, not so philosophical now!
Sorry, I get like that occasionally. My thoughts tend to wander. Speaking of wandering, that's what I do.
Wander? What do you mean?
I guess you could call it traveling, as my wandering looks sort of like that. I've been on the road in one form or another since 2006.
But it's not really traveling, you see. I'm not going anywhere.
How can you be traveling but not going anywhere?
I'm not traveling, that's the thing. I'm moving. I love to move, I can't stay still. Some might call it a compulsion, they might not be wrong.
Where are you moving?
Ah! Now this is is the question, enough of the vagaries of the mind and the abstract! Life is in the world and full of the unexpected, the unanticipated, the unimagined.
You can find where I'm living life on my map. Currently I am traveling east.
East? East from where? To where?
Well in January 2013, I found myself in the Netherlands along the North Sea coast. I began heading east by biycle and raft. I'm over in Eastern Europe now, nominally heading east. Not "to" anywhere, just east.
Bicycle, raft?!
Yeah, a few years ago in South America I discovered a passion for slow-travel.
What better slow-travel is there than the human-powered kind? The bicycle
allows me to carry everything I need to be mostly self-sufficient on the road.
Since then I've picked up an inflatable packraft that I can pack on the bike, and stow the bike on. The raft allows me to navigate lakes, rivers and, maybe even seas. I have a video demonstrating the bike — raft conversion.
Well that's the question isn't it? Answer that question and you'll be able to solve all the world's problems. Or maybe not. I sure don't know the answer, so you won't find it here.
Woah, not so philosophical now!
Sorry, I get like that occasionally. My thoughts tend to wander. Speaking of wandering, that's what I do.
Wander? What do you mean?
I guess you could call it traveling, as my wandering looks sort of like that. I've been on the road in one form or another since 2006.
But it's not really traveling, you see. I'm not going anywhere.
How can you be traveling but not going anywhere?
I'm not traveling, that's the thing. I'm moving. I love to move, I can't stay still. Some might call it a compulsion, they might not be wrong.
Where are you moving?
Ah! Now this is is the question, enough of the vagaries of the mind and the abstract! Life is in the world and full of the unexpected, the unanticipated, the unimagined.
You can find where I'm living life on my map. Currently I am traveling east.
East? East from where? To where?
Well in January 2013, I found myself in the Netherlands along the North Sea coast. I began heading east by biycle and raft. I'm over in Eastern Europe now, nominally heading east. Not "to" anywhere, just east.
Bicycle, raft?!
Yeah, a few years ago in South America I discovered a passion for slow-travel. What better slow-travel is there than the human-powered kind? The bicycle allows me to carry everything I need to be mostly self-sufficient on the road.
Since then I've picked up an inflatable packraft that I can pack on the bike, and stow the bike on. The raft allows me to navigate lakes, rivers and, maybe even seas.
I have a video demonstrating the bike — raft conversion.


Airflow
Project
License
Quick Start
Installation
Tutorial
Configuration
UI / Screenshots
Concepts
Data Profiling
Command Line Interface
Scheduling & Triggers
Plugins
Security
Experimental Rest API
Integration
FAQ
API Reference
Airflow
Docs
»
Index
A
|
B
|
C
|
D
|
E
|
F
|
G
|
H
|
I
|
K
|
L
|
M
|
N
|
O
|
P
|
R
|
S
|
T
|
U
|
W
|
X
A
add_task() (airflow.models.DAG method)
add_tasks() (airflow.models.DAG method)
airflow.contrib.hooks (module)
airflow.contrib.operators (module)
airflow.executors (module)
airflow.hooks (module)
airflow.macros (module)
airflow.macros.hive (module)
airflow.models (module)
airflow.operators (module)
are_dependencies_met() (airflow.models.TaskInstance method)
are_dependents_done() (airflow.models.TaskInstance method)
B
bag_dag() (airflow.models.DagBag method)
BaseOperator (class in airflow.models)
,
[1]
BaseSensorOperator (class in airflow.operators.sensors)
BashOperator (class in airflow.operators)
BranchPythonOperator (class in airflow.operators)
bulk_dump() (airflow.hooks.DbApiHook method)
bulk_load() (airflow.hooks.DbApiHook method)
(airflow.hooks.MySqlHook method)
C
check_output() (airflow.contrib.hooks.SSHHook method)
clear() (airflow.models.BaseOperator method)
(airflow.models.DAG method)
clear_xcom_data() (airflow.models.TaskInstance method)
cli() (airflow.models.DAG method)
close_conn() (airflow.contrib.hooks.FTPHook method)
closest_ds_partition() (in module airflow.macros.hive)
collect_dags() (airflow.models.DagBag method)
command() (airflow.models.TaskInstance method)
command_as_list() (airflow.models.TaskInstance method)
concurrency_reached (airflow.models.DAG attribute)
Connection (class in airflow.models)
crawl_for_tasks() (airflow.models.DAG method)
create_dagrun() (airflow.models.DAG method)
create_directory() (airflow.contrib.hooks.FTPHook method)
current_state() (airflow.models.TaskInstance method)
D
dag (airflow.models.BaseOperator attribute)
DAG (class in airflow.models)
DagBag (class in airflow.models)
dagbag_report() (airflow.models.DagBag method)
DbApiHook (class in airflow.hooks)
deactivate_stale_dags() (airflow.models.DAG static method)
deactivate_unknown_dags() (airflow.models.DAG static method)
delete_directory() (airflow.contrib.hooks.FTPHook method)
delete_file() (airflow.contrib.hooks.FTPHook method)
deps (airflow.models.BaseOperator attribute)
describe_directory() (airflow.contrib.hooks.FTPHook method)
detect_downstream_cycle() (airflow.models.BaseOperator method)
downstream_list (airflow.models.BaseOperator attribute)
ds_add() (in module airflow.macros)
ds_format() (in module airflow.macros)
DummyOperator (class in airflow.operators)
E
EmailOperator (class in airflow.operators)
error() (airflow.models.TaskInstance method)
execute() (airflow.models.BaseOperator method)
(airflow.operators.BashOperator method)
ExternalTaskSensor (class in airflow.operators)
extra_dejson (airflow.models.Connection attribute)
F
filepath (airflow.models.DAG attribute)
filter_for_filesize() (airflow.operators.HdfsSensor static method)
filter_for_ignored_ext() (airflow.operators.HdfsSensor static method)
folder (airflow.models.DAG attribute)
FTPHook (class in airflow.contrib.hooks)
G
generate_command() (airflow.models.TaskInstance static method)
GenericTransfer (class in airflow.operators)
get_active_runs() (airflow.models.DAG method)
get_conn() (airflow.contrib.hooks.FTPHook method)
(airflow.hooks.DbApiHook method)
(airflow.hooks.HttpHook method)
(airflow.hooks.MySqlHook method)
(airflow.hooks.PrestoHook method)
(airflow.hooks.SqliteHook method)
get_cursor() (airflow.hooks.DbApiHook method)
get_dag() (airflow.models.DagBag method)
get_dagrun() (airflow.models.DAG method)
(airflow.models.TaskInstance method)
get_direct_relatives() (airflow.models.BaseOperator method)
get_first() (airflow.hooks.DbApiHook method)
(airflow.hooks.PrestoHook method)
get_flat_relatives() (airflow.models.BaseOperator method)
get_last_dagrun() (airflow.models.DAG method)
get_pandas_df() (airflow.hooks.DbApiHook method)
(airflow.hooks.PrestoHook method)
get_records() (airflow.hooks.DbApiHook method)
(airflow.hooks.PrestoHook method)
get_task_instances() (airflow.models.BaseOperator method)
get_template_env() (airflow.models.DAG method)
H
has_dag() (airflow.models.BaseOperator method)
HdfsSensor (class in airflow.operators)
HipChatAPIOperator (class in airflow.contrib.operators.hipchat_operator)
HipChatAPISendRoomNotificationOperator (class in airflow.contrib.operators.hipchat_operator)
HivePartitionSensor (class in airflow.operators)
HttpHook (class in airflow.hooks)
HttpSensor (class in airflow.operators)
I
init_on_load() (airflow.models.TaskInstance method)
insert_rows() (airflow.hooks.DbApiHook method)
is_paused (airflow.models.DAG attribute)
is_premature (airflow.models.TaskInstance attribute)
K
key (airflow.models.TaskInstance attribute)
kill_zombies() (airflow.models.DagBag method)
L
latest_execution_date (airflow.models.DAG attribute)
list_directory() (airflow.contrib.hooks.FTPHook method)
LocalExecutor (class in airflow.executors)
M
max_partition() (in module airflow.macros.hive)
MesosExecutor (class in airflow.contrib.executors.mesos_executor)
MetastorePartitionSensor (class in airflow.operators)
MySqlHook (class in airflow.hooks)
MySqlOperator (class in airflow.operators)
N
NamedHivePartitionSensor (class in airflow.operators)
next_retry_datetime() (airflow.models.TaskInstance method)
normalize_schedule() (airflow.models.DAG method)
O
on_kill() (airflow.models.BaseOperator method)
P
pool_full() (airflow.models.TaskInstance method)
Popen() (airflow.contrib.hooks.SSHHook method)
post_execute() (airflow.models.BaseOperator method)
pre_execute() (airflow.models.BaseOperator method)
prepare_template() (airflow.models.BaseOperator method)
PrestoCheckOperator (class in airflow.operators)
PrestoHook (class in airflow.hooks)
PrestoIntervalCheckOperator (class in airflow.operators)
PrestoValueCheckOperator (class in airflow.operators)
previous_ti (airflow.models.TaskInstance attribute)
process_file() (airflow.models.DagBag method)
PythonOperator (class in airflow.operators)
R
random() (in module airflow.macros)
ready_for_retry() (airflow.models.TaskInstance method)
refresh_from_db() (airflow.models.TaskInstance method)
rename() (airflow.contrib.hooks.FTPHook method)
render_template() (airflow.models.BaseOperator method)
render_template_from_field() (airflow.models.BaseOperator method)
retrieve_file() (airflow.contrib.hooks.FTPHook method)
run() (airflow.hooks.DbApiHook method)
(airflow.hooks.HttpHook method)
(airflow.hooks.PrestoHook method)
(airflow.models.BaseOperator method)
(airflow.models.DAG method)
(airflow.models.TaskInstance method)
run_and_check() (airflow.hooks.HttpHook method)
S
S3KeySensor (class in airflow.operators)
schedule_interval (airflow.models.BaseOperator attribute)
SequentialExecutor (class in airflow.executors)
set_dependency() (airflow.models.DAG method)
set_downstream() (airflow.models.BaseOperator method)
set_upstream() (airflow.models.BaseOperator method)
ShortCircuitOperator (class in airflow.operators)
SimpleHttpOperator (class in airflow.operators)
size() (airflow.models.DagBag method)
SqliteHook (class in airflow.hooks)
SqlSensor (class in airflow.operators)
SSHExecuteOperator (class in airflow.contrib.operators)
SSHHook (class in airflow.contrib.hooks)
store_file() (airflow.contrib.hooks.FTPHook method)
sub_dag() (airflow.models.DAG method)
subdags (airflow.models.DAG attribute)
sync_to_db() (airflow.models.DAG static method)
T
TaskInstance (class in airflow.models)
TimeSensor (class in airflow.operators)
tree_view() (airflow.models.DAG method)
TriggerDagRunOperator (class in airflow.operators)
tunnel() (airflow.contrib.hooks.SSHHook method)
U
upstream_list (airflow.models.BaseOperator attribute)
W
WebHdfsSensor (class in airflow.operators)
X
xcom_pull() (airflow.models.BaseOperator method)
(airflow.models.TaskInstance method)
xcom_push() (airflow.models.BaseOperator method)
(airflow.models.TaskInstance method)


We are both working a website for class and I am wondering how they are doing theirs.
Top ten best things about a program.
A cool infographic about HTML.
IT cartoon showing the problem with people and computers.
Chart on how people fix their computer.
---------------------------------------------------------------------
Instructions:
Infuse* all ingredients in a room full of programmers.
When finished, submit to boss or add to app store / web.
How to make a good program.
One free pass on syntax!


Opening a Tree Diagram
1 In the Results window, select an entity.
2 Do one of the following:
• Select View > Call Tree.
• Click .
A Tree Diagram window appears.
The selected entity appears as the root, at the left, without coloration. Dependent entities appear as branches, bordered with green.
Call Tree diagram color codes and graphic symbols


Before Change
conf.gcp_source_project_service_account_key),
target_storage_client=storage.Client.from_service_account_json(
conf.gcp_target_project_service_account_key),
target_logging_client=logging.Client.from_service_account_json(
conf.gcp_target_project_service_account_key),
source_project=conf.source_project,
target_project=conf.target_project,
bucket_name=conf.bucket_name,
After Change
target_project_credentials=target_credentials,
source_storage_client=storage.Client(
credentials=source_credentials, project=conf.source_project),
target_storage_client=storage.Client(
credentials=target_credentials, project=conf.target_project),
target_logging_client=logging.Client(
credentials=target_credentials, project=conf.target_project),
source_project=conf.source_project,


--- layout: post title: Read the docs tags: news author: Gertjan van Zwieten ---
Preparing for the first official nutils release we are putting some much needed effort into lowering the entry bar for new users. Today we added sphinx documentation under /docs and registered the project at readthedocs, which from this day on will host the official nutils user guide at docs.nutils.org. In the coming months we will populate the documentation tree with an installation guide, a quickstart tutorial, and build out docstrings to provide a meaningful API reference.


About Me
Time: I enjoy reading and listining to music, Playing video games, Hanging out with my friends, and having a good time.
Food: I ike to eat candy, pizza, sushi, Breakfast foods (as in bacon, cereal, eggs, toast, and waffles.) I love spicy foods, but need milk lots.
Life: I am in seventh grade, and am twelve. I skipped grade five, and am wanting to skip another grade. I am homeschooled for all grades exept preschool and grade two. I hated grade two. I am starting to write a book. I play baseball and want to play football, though it's four practices a week, and that leaves no room to do anything else.
Favourites: My favourite books are the Maze Runner sieries, the Wingfeather saga, the Mistborn sieries, the Hunger Games, the Eragon books, Ready Player One, and the Hobbit. My favourite movies are the Lord of the Rings, the Hobbit, the Hunger Games, Star Wars, and Spiderman Homecoming. My favourite video games are the Legend of Zelda, Mario, Halo, Star Wars Battlefront I and II, and Robo Recal for VR. My favourite songs are Say Something, Ice Age, No Excuses, Kinda Complicated, and Stay With Me.


WeiQi 围棋 / iGo 囲碁 / Baduk 바둑
Welcome to the Ohio Go Association Website (work in progress)
Active Statewide Clubs
Columbus
Cleveland
Dayton
Cincinnati
Mason
Toledo


BY EDWIN JAHIEL
KRIPPENDORF'S TRIBE (1998) ** 1/2 Directed by Todd Holland. Screenplay, Charlie Peters, based on the book by Frank Parkin.Photography, Dean Cundey. Editing, Jon Poll. Production design, Scott Chambliss. Art direction, Bill Rea.Costumes, Isis Mussend en. Music, Bruce Broughton. Produced by Larry Brezner. Cast: Richard Dreyfuss (James Krippendorf), Jenna Elfman (Veronica Micelli), Natasha Lyonne (Shelly), Gregory Smith (Mickey), Carl Michael Linder (Edmund), Lily Tomlin (Prof. Allen), Stephen Root (Gerald Adams),Doris Belack (President Porter), Julio Oscar Mechoso (Simon Alonso), Elaine Stritch (Grandma), Tom Poston (Grandpa), David Ogden Stiers (Henry Spivey), et al. A Buena Vista release of a Touchstone Picture. 93 min. PG-13.
"You who enter here, abandon all logic." Depending on a film's genre, lack of logic can range from disastrous (in serious dramas), to annoying (in action movies), to anodyne (in comedies), to fun (in farces). And "Krippendorf's Tribe" is a farce as broad as the Titanic was long -- the real ship, as the movie's is only 4/5ths to scale.
 Anthropologist Professor Krippendorf (Hoffman) had received a $100,000 Proxmire Foundation grant to find a "lost" tribe in New Guinea. He, his wife -- also an anthropologist -- and their three kids went on a field expedition, but it came a-cropper.
Things get cinematically murky from here on out. Upon their return, Mrs. K died (where, when, of what?). Apparently Prof.James Krippendorf claimed that the expedition was a success but kept stalling with making the results public. In reality, he fell apart professionally and personally, made a mess of being a single father, and in the past two years has gone through the rest of the grant money to raise his kids and buy stuff for the home. He is broke and way behind with his mortgage payments.
The above is a relatively coherent decryption of the movie's messy --but often funny -- exposition. It opens with a view of the K household in disarray, furniture that looks partly like the outcome of Goodwill (Industries) hunting, the Professor in a state of confusion and the kids not respecting Papa.
Old Hollywood college movies were populated by overage students who danced, sang, lit bonfires and apparently majored in ukulele. Nowadays, pictures on Academe, in keeping with the times may stress research. So,when Veronica Micelli (Jenna Elfman) persistently bangs on the Professor's door, she sets the plot in motion. Veronica, whose height dwarfs Krippendorf's, was an adoring student of his and is now a new Assistant Professor of Anthropology at the University. She wants to collaborate with her idol -- a good way to get fame, promotion and tenure. She also reminds him that he is giving a lecture on his findings. In a matter of hours.
Krippendorf's panic,chaotic school office and his bluffing throughout his lecture are as amusing as they are unlikely. Under pressure, the invent-as-you-go scholar baptizes the imaginary tribe Shelmikedmu -- concocted from the names of his children -- and describes it by using his own experiences as a single dad. His biggest "discovery" is that the Shelmikedmu fathers alone raise their progeny and are respected.
So far, so bad for Prof. K. The worst news is that visual proof of his success is expected of him. It's a nightmare. The professor must feel like Kafka's K. With necessity being the mother of invention, he gathers his children, builds a "New Guinea"" landscape in his yard (!), adds huts and stuff (!) and disguises the kids as "natives" (!) Then he films all this like a pro, on 16 mm. no less (!).In record time (something like a few hours) the film is shot, apparently developed at home, and edited with real anthropological footage spliced in (!)
What follows is chaotic madness, fluff as credible as Mel Brooks extravaganzas, the Three Stooges, The Marx Brothers or Monty Python. The tangled web we weave whenever we deceive grows non-stop and exponentially. At every step additional inventions are required, all unbelievable, of course. The tribe -- eventually including co-conspirator Veronica -- goes through lightning-quick masquerades, transformations, and complications which include a rival, suspicious and witchy colleague (Lily Tomlin, played as a caricature) suddenly taking off for New Guinea so as to discredit Krippendorf.
On the whole, the picture is entertaining, albeit uneven. It creates in the audience the gamut of reactions: big laughter, chuckles, smiles, smirks. Shudders too, since this "Widowed...with Children" farce can be just as tasteless as "Married... with children" and at times just as unfunny.
Alfred Hitchcock's famous remark "It's only a movie" applies here. Set aside your morals, as a precondition to having fun. Take "Krippendorf's Tribe" solemnly and its heavy load of bathroom and sexual "humor" is reprehensible, as is the spectacle of a dysfunctional family bonding through major cheating.
What certainly is politically incorrect is not the showing of white people in blackface, but the transparent and insensitive use of African-Americans (and a South African) to impersonate "real" New Guineans. Couldn't the film makers have gone the extra mile and somehow found natives of New Guinea?
Superfluously tacky too is a big banquet to honor donor Mrs. Proxmire on her 100th birthday.The sight of her and of several guests connected to intravenous machines is pure ageism -- not helped by an amazingly unfunny question to the centenarian: "Was it you who died or your sister?"
"KT" is to a great extent a burlesque send-off of Academe. The script, starting with the scandalous cheating on, or illegal use of grants, takes aspects of academic life and pushes them to most outrageously absurd levels. Cannily, it throws in the in-joke (wasted on most viewers) of the name Proxmire used for the grant and for a major campus building.
Wisconsin's great Senator William Proxmire served for 32 years, retiring in 1989. A devoted public servant, he created in 1975 his famous Golden Fleece Award which, each month, singled out a "wasteful, ridiculous or ironic use of the taxpayers' money." In 1985 he declared:"My own favorite was the study to find out whether sunfish that drink tequila are more aggressive than sunfish who drink gin." (See below for a sampling of other awards) *
Performances range from adequate to very good, the latter by the manic Dreyfuss and his brood. In a work of pure fantasy the youngsters are smart, imaginative, and deliver their lines more convincingly than in most child-roles.Jenna Elfman is overdone. Save for the smallish role of Lily Tomlin, the supporting cast have tiny parts
Photography (in Hawaii and California) is skillful. In another in-joke which only older or savvy viewers will appreciate, much of the musical score nicely consists of exotic tunes, including the once-famous "Taboo" by Margarita Lecuona ("Babalu"), a distant cousin of the admirable Ernesto Lecuona, the Cuban composer of, among many songs, "Malaguena," "Siboney," and"Jungle Drums." ====================================== * Some other Golden Fleece Awards.
To the Department of the Army for spending $6,000 in 1981 to prepare a 17-page document that told the federal government how to buy a bottle of Worcestershire sauce.
To the Environmental Protection Agency for spending an extra $1 million to $1.2 million in 1980 to preserve a Trenton, NJ sewer as an historical monument.
To the Commerce Department for spending $20,000 in 1981 to construct an 800-foot limestone replica of the Great Wall of China in Bedford, Indiana.
To the NEH for a $25,000 grant in 1977 to study why people cheat, lie and act rudely on local Virginia tennis courts.
To the Office of Education for spending $219,592 in 1978 to develop a curriculum to teach college students how to watch television.
" Le mauvais gout mene au crime" (Stendhal)
Edwin Jahiel's movie reviews are at http://www.prairienet.org/ejahiel
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Home
Trees
Indices
Help
[
frames
] |
no frames
]
[
Module Hierarchy
|
Class Hierarchy
]
Module Hierarchy
cnavg
:
The Glorious CN-AVG python library
cnavg.avg
:
All about sequence graphs
cnavg.avg.balanced
:
Definition of copy-number balancing across a sequence graph
cnavg.avg.gabp
cnavg.avg.gabp.gabp
:
Python wrapper for GaBP application in GraphLab By Daniel Zerbino, based on Matlab code by Danny Bickson
cnavg.avg.graph
:
Definition of sequence graphs
cnavg.avg.module
:
Definition of module around nets
cnavg.avg.node
:
Definition of the Node object
cnavg.avg.nodeFlow
:
Definition of NodeFlow, a static node's dynamic context within a graph
cnavg.basics
:
Basic mathematical objects
cnavg.basics.coords
:
Definition of geometric objects along chromosomes.
cnavg.basics.partialOrderSet
:
Definition of Partial Order Set
cnavg.cactus
:
All about cactus graphs
cnavg.cactus.balanced
:
Balancing of the flows in a Cactus graph
cnavg.cactus.block
:
Definition of Block, ie a segment edge in a cactus graph
cnavg.cactus.chain
:
Definition of Chain, a simple cycle of blocks within a cactus graph
cnavg.cactus.graph
:
Definition of Cactus graphs
cnavg.cactus.group
:
Definition of Group, a connected component of bonds
cnavg.cactus.net
:
Definition of Net, ie a set of 3-edge connected groups
cnavg.cactus.oriented
:
Definition of OrientedCactus, where nets and chains are organized into a bi-partite tree
cnavg.cactus.threeWay
cnavg.cactus.threeWay.components
:
Wrapper for the threeWay executable
cnavg.cactusSampling
cnavg.cactusSampling.sampling
:
Cactus graph normalization, ie ensuring the flow is constant across all blocks in a chain
cnavg.cactusTree
cnavg.cactusTree.cactusTree
:
Integrated jobTree pipeline.
cnavg.clock
:
Timing the SNVs wrt the CNVs
cnavg.clock.EM
:
Expectation Maximisation timing of the SNVs wrt CNVs
cnavg.clock.cnvTree
:
Representing the molecular tree underlying the clonal tree
cnavg.clock.timeEvents
:
Merging the SNV and CNV data
cnavg.flows
:
All about flows
cnavg.flows.cycle
:
Cycle traversal underlying an alternating flow
cnavg.flows.edge
:
Edge traversals
cnavg.flows.flows
:
Net flow change between two genomes
cnavg.flows.unitFlows
:
Near-simple flows
cnavg.history
:
All about simple flow histories
cnavg.history.constrained
:
Computing and detecting rearrangment costs plus any discrepancy in a history
cnavg.history.debug
cnavg.history.euclidian
:
Linear algebra representation of a history
cnavg.history.flattened
:
Flattening history so that they are no longer split by net
cnavg.history.history
:
Flow history
cnavg.history.ordered
:
History with arbitrary linear ordering, for display purposes
cnavg.history.overlap
:
History with look up table to speed up the search for overlapping flow changes
cnavg.history.scheduled
:
Keeping track of the tree of events in a history
cnavg.historySampling
:
All about sampling through histories
cnavg.historySampling.cycleCover
:
Producing an initial flow history underlying a metagenomic net flow change
cnavg.historySampling.sampleGraphCycles
:
Sampling through histories at the global level
cnavg.historySampling.sampleModuleCycles
:
Sampling histories at the local level
cnavg.preprocess
:
The gargage that goes into the pipeline
cnavg.preprocess.bambam
:
Parsing BamBam output
cnavg.preprocess.breakend
:
VCF style representation of breakend data
cnavg.preprocess.breakendGraph
:
Handling a collection of breakends
cnavg.preprocess.cbs
cnavg.preprocess.cbs.cbs
:
Wrapper around CBS
cnavg.preprocess.cnv
:
CNV data holder
cnavg.preprocess.discrepancies
cnavg.preprocess.segmentCNVs
:
Smooth out brute CNV calls
cnavg.preprocess.vcf
:
Read VCF files
cnavg.simulator
:
Testing the pipeline on simulated histories
cnavg.simulator.simulator
:
Produces random evolutionary histories
Home
Trees
Indices
Help
Generated by Epydoc 3.0.1 on Tue Mar 12 12:56:34 2013
http://epydoc.sourceforge.net


'What-if scenario' - Club chief gives update on plan for Aston Villa transfer target
Latest Aston Villa news includes Rangers' sporting director confirming Alfredo Morelos plan
by Shane Ireland, https://www.facebook.com/ShaneIrelandJournalistThere are ‘ongoing’ conversations to ensure that Rangers have a ready-made replacement for Alfredo Morelos when the Aston Villa-linked striker leaves the club.
Morelos, 23, has been touted for a move to the Premier League and Villa are said to be among his admirers.
Just four months after his first appearance of the season in the qualifying stages of the Europa League, Morelos has already scored 22 goals.
Rangers are keen to ensure the Colombian stays beyond the January window – as boss Steven Gerrard has already confirmed – but sporting director Ross Wilson revealed a plan is being drawn up for when the times comes to sell.
Aston Villa latest
This is your round up of all things Villa; the one-stop shop that will keep you updated on the latest goings on at the club and beyond.
Transfers, injuries, match-days and managers, we’ve got you covered.
We’ll be bringing the very latest on the Villains throughout the week and around the clock.
Make sure you keep yourself updated with our handy daily catch up...
Must reads...
- Villa fans make Chelsea transfer demand
- 'Worried' fans react to major announcement
- Former Villan reveals Newcastle bombshell
- Morelos saga takes new twist
For all your latest AVFC news, opinion, analysis and transfer gossip, click here
You can follow our Villa reporter Ashley Preece on Twitter, and his email address is<EMAIL_ADDRESS>“That’s a conversation that’s ongoing with the scouts all the time,” Wilson told the Scotsman.
“One of the aims of the scouting and recruitment department is to make sure that in every position we always have a strong list of where we might go in a ‘what-if’ scenario. That’s something we’ve got and it’s something that will build and evolve and develop all the time.
“The scouting network here has started to be developed strongly across the last couple of years and I’ve had a lot of chats with head of scouting Andy Scoulding as to how we continue to develop that.
“The task is to make that scouting structure bigger and more robust, tap into the networks we’ve all got inside the club, to find as many opportunities as we can, whether that’s from England, Scotland or into Europe.”
Morelos has also been linked with Leicester City and Crystal Palace, although talk of a move to the King Power Stadium was quashed by reports in Scotland.
Wilson added: "We want our best players to stay here as long as they possibly can.
"We understand that like every other club in world football that there comes a point when players have to move on to something else for a variety of reasons."


I have been trying to keep updated with the newest frameworks that are being added in JavaScript world.
Tracking new development and programming best practices is the activity that I enjoy during the initial hours of the day, spending most of the time checking issues and trying to answer on StackOverflow.
Being a subscriber of the open-source community and solving problems is what I am excited about.


Class: MailEngine::Sendgrid::RestApi
- Inherits:
-
Object
- Object
- MailEngine::Sendgrid::RestApi
- Includes:
- HTTParty
- Defined in:
- lib/mail_engine/sendgrid/rest_api.rb
Class Method Summary (collapse)
-
+ (Object) blocks(options = {})
<blocks>.
-
+ (Object) bounces(options = {})
<bounces>.
-
+ (Object) invalidemails(options = {})
<invalidemails>.
-
+ (Object) spamreports(options = {})
<spamreports>.
-
+ (Object) stats(options = {})
<stats>.
Class Method Details
+ (Object) blocks(options = {})
<blocks>
<block><EMAIL_ADDRESS><status></status> <reason>Some random block reason</reason> <created>2010-11-08 20:39:29</created> </block>
</blocks>
77 |
# File 'lib/mail_engine/sendgrid/rest_api.rb', line 77 def blocks = {} |
+ (Object) bounces(options = {})
<bounces>
<bounce><EMAIL_ADDRESS><status>5.1.1</status> <reason>host [<IP_ADDRESS>] said: 550 5.1.1 unknown or illegal user<EMAIL_ADDRESS><created>2009-06-10 12:40:30</created> </bounce>
</bounces>
41 |
# File 'lib/mail_engine/sendgrid/rest_api.rb', line 41 def bounces = {} |
+ (Object) invalidemails(options = {})
<invalidemails>
<invalidemail><EMAIL_ADDRESS><reason>Mail domain mentioned in email address is unknown</reason> <created>2009-06-10 12:40:30</created> </invalidemail>
</invalidemails>
64 |
# File 'lib/mail_engine/sendgrid/rest_api.rb', line 64 def invalidemails = {} |
+ (Object) spamreports(options = {})
<spamreports>
<spamreport><EMAIL_ADDRESS><created>2009-06-10 12:40:30</created> </spamreport>
</spamreports>
52 |
# File 'lib/mail_engine/sendgrid/rest_api.rb', line 52 def spamreports = {} |
+ (Object) stats(options = {})
<stats>
<day> <date>2009-06-20</date> <requests>12342</requests> <bounces>12</bounces> <clicks>10223</clicks> <opens>9992</opens> <spamreports>5</spamreports> <unique_clicks>3</unique_clicks> <unique_opens>6</unique_opens> <blocked>7</blocked> </day>
</stats>
28 |
# File 'lib/mail_engine/sendgrid/rest_api.rb', line 28 def stats = {} |


San Diego JS Meetup: Angular Directives
A directive that returns an object with a compile function.
Compile Directive


|
rapidjson
A fast JSON parser/generator for C++ with both SAX/DOM style API
|
JSON writer. More...
#include <writer.h>
Classes | |
| struct | Level |
| Information for each nested level. More... | |
Public Types | |
| typedef Encoding::Ch | Ch |
Public Member Functions | |
| Writer (Stream &stream, Allocator *allocator=0, size_t levelDepth=kDefaultLevelDepth) | |
| Writer & | String (const Ch *str) |
| Simpler but slower overload. | |
| Writer & | Null () |
| Writer & | Bool (bool b) |
| Writer & | Int (int i) |
| Writer & | Uint (unsigned u) |
| Writer & | Int64 (int64_t i64) |
| Writer & | Uint64 (uint64_t u64) |
| Writer & | Double (double d) |
| Writer & | String (const Ch *str, SizeType length, bool copy=false) |
| Writer & | StartObject () |
| Writer & | EndObject (SizeType memberCount=0) |
| Writer & | StartArray () |
| Writer & | EndArray (SizeType elementCount=0) |
Protected Member Functions | |
| void | WriteNull () |
| void | WriteBool (bool b) |
| void | WriteInt (int i) |
| void | WriteUint (unsigned u) |
| void | WriteInt64 (int64_t i64) |
| void | WriteUint64 (uint64_t u64) |
| void | WriteDouble (double d) |
| void | WriteString (const Ch *str, SizeType length) |
| void | WriteStartObject () |
| void | WriteEndObject () |
| void | WriteStartArray () |
| void | WriteEndArray () |
| void | Prefix (Type type) |
Protected Attributes | |
| Stream & | stream_ |
| internal::Stack< Allocator > | level_stack_ |
Static Protected Attributes | |
| static const size_t | kDefaultLevelDepth = 32 |
JSON writer.
Writer implements the concept Handler. It generates JSON text by events to an output stream.
User may programmatically calls the functions of a writer to generate JSON text.
On the other side, a writer can also be passed to objects that generates events,
for example Reader::Parse() and Document::Accept().
| void rapidjson::Writer< Stream, Encoding, Allocator >::WriteDouble | ( | double | d | ) | [inline, protected] |