text:
Home > Courses > Course Search Results > Bond University > Bachelor of Journalism / Bachelor of Laws
Bachelor of Journalism / Bachelor of Laws
The Bachelor of Journalism is recognised internationally for its quality and innovation, incorporating foundations in journalistic traditions with emerging media trends. Students are trained in news writing, broadcast reporting, photography, media rounds and industries, digital publication and design, media ethics and law. Students can undertake specialised subjects such as Foreign Correspondence; Fashion, Travel and Sport Writing; Multimedia Production; Photojournalism; Creative Non-Fiction and Fiction Writing; Social Media and Citizen Journalism. Bond is committed to maintaining strong industry ties, with many assessment tasks linked to real world publication outcomes including internet publications. Students will have the opportunity to report for local, national and international media outlets throughout their degree and can undertake internships in Australia or internationally in places like New York, Washington and London. The Bachelor of Laws prepares students for a career as a legal professional, both within Australia and overseas. It provides students with a thorough grounding in essential areas of substantive law and access to a wide choice of law elective subjects, including the option of completing a specialisation. An integrated skills and professionalism program is embedded in the degree and focuses on core legal skills essential to the practice of law. The Bachelor of Laws provides an engaging learning experience that challenges students academically and prepares them practically for a legal career.
Australian: $205,920
International: $228,960
Bond University requires the successful completion of Year 12 or equivalent for entry to Bachelor level programs. Bond does not rely solely on the Overall Position (OP) or the Australian Tertiary Admission Rank (ATAR). Rather, a range of criteria are also considered such as extracurricular activities and personal attributes, including outstanding leadership qualities and community involvement.
3 core University subjects; 13 Foundation Journalism subjects; 6 Specialist Major subjects; 2 General Electives; 17 Compulsory Law subjects; 7 Law electives.
Advertising; Australian Studies; Business Context and Environment; Communication; Corporate Communication; Creative Writing; Criminology; Environmental Science and Management; Film and Television; International Relations; Media Studies; Multimedia Design; Philosophy; Public Relations; Social Media; Sport Industry; Sustainable Environment and Planning.
The Bachelor of Journalism / Bachelor of Laws enables you to graduate with two undergraduate degrees. The combined degree provides students with the professional outcomes and opportunities of both individual degrees. Please refer to the individual programs for professional outcomes. Completing this combined program will provide opportunities for a range of careers in private, government and not for profit sectors. Graduates may seek to practise law whilst utilising a foundational understanding of the production of content for a range of traditional and multimedia platforms, or employ their understanding of journalism to work in biomedical industries with a background in compliance, regulation and intellectual property.
Provider CRICOS: 00017B
Advertising Account Executive, Criminologist, Digital Marketing Specialist, eCommerce Business Owner, Journalist, Lawyer, Marketing Officer, Public Relations Officer, SEO Specialist, Writer,
information@bond.edu.au
Gold Coast No info No Full time 4 years
Gold Coast No info No Part time
A student experience powerfully focused on the individual.
If you're looking for a richly rewarding university experience which can bring your career goals to life much faster, Bond is for you.
The combination of smaller classes, highly individualised teaching and support and the wonderful bond of friendship that exists among the student community makes for an experience which many Bond students say is the most rewarding and empowering time of their lives.
Want independent proof that the student experience here is the best in the nation? You need only to look the independent research findings - which ask students nationwide for an unbiased, critical view of their university experience. The result: Bond has scored five stars for student satisfaction in The Good Universities Guide for 12 years running and ranks at the top of the Australian Government's 2017 national Student Experience Survey.
Our programs are geared towards inspiring students to achieve beyond their expectations - and to strive to pursue their dreams and aspirations. Our accelerated timetable and intensive programs can fast-track your studies to help you complete your degree much sooner, while world-class lecturers and the unrivalled facilities at our stunning, modern Gold Coast campus enhance your learning and social experience.
Bond offers undergraduate and postgraduate degrees in Law, Business, Communication and Creative Media, Architecture and Built Environment and Health Sciences & Medicine. All students have access to unparalleled academic and technological resources on Bond's world-class Gold Coast campus.
We've engineered all our programs to have a strong focus on entrepreneurial thinking and creative problem solving, with strategies to help graduates thrive in a disrupted, digital world. The Beyond Bond program, a key part of every degree, fosters and develops the skills demanded by employers, setting you up for career success.
Bond University's Scholarship Program encompasses a range of awards available to both Australian and international students at an undergraduate and postgraduate level. For more information, visit our scholarships page.
Study Mode Part-time internal Full-time internal
Bachelor of Business (Specialisation)
Bachelor of Biomedical Science / Bachelor of Business
Bachelor of Arts Therapy
IKON Institute of Australia
Bachelor of Communication - Media
Bachelor of Media and Communication
Bachelor of Arts / Bachelor of Science
Bachelor of Communication - Journalism
Bachelor of Digital Media - 3D Design and Animation
Billy Blue College of Design at Torrens University
Bachelor of Media and Communication (Professional)
Bachelor of Communication - Public Relations
Bachelor of Communication and Media / Bachelor of Science
Bachelor of Marketing and Public Relations / Bachelor of Communications and Media
The University of Notre Dame Australia
Bachelor of Journalism / Bachelor of Arts
Bachelor of Interactive Media
Academy of Information Technology Pty Ltd
Bachelor of Sports Media
Bachelor of Arts / Bachelor of Communication - Advertising
Bachelor of - Business, Humanities and Social Sciences - Flexible Vertical Double Degree
Bachelor of Arts (Film Production)
Bachelor of Arts - International Studies / Bachelor of Communication - Advertising
Bachelor of Communication & Media (Corporate & Public Communication)
Bachelor of Science / Bachelor of Arts
Bachelor of Education - Secondary
Bachelor of Laws / Bachelor of Arts
Bachelor of Arts / Bachelor of Commerce
Bachelor of Communications & Media
Bachelor of Arts - Politics and Journalism
Bachelor of Psychological Science
Bachelor of Media Design
Media Design School at Torrens
Bachelor of Arts (Advanced)
Bachelor of Arts / Bachelor of Economics
Bachelor of Liberal Arts and Sciences
Bachelor of International Studies / Bachelor of Arts
Bachelor of Visual Communication
Bachelor of Arts / Bachelor of Information Communication Technology
Bachelor of Media


text:
Manuscript Submission Requirements Checklist
Submit with Fast Format: ACS journals have simplified formatting requirements with a streamlined and standardized review-ready format for an initial manuscript submission. Include article titles in references.
Cover Letter: must include a paragraph explaining why your manuscript is appropriate for ACS Organic & Inorganic Au, clearly indicating what key advance(s) are described in the work relative to the state-of-the-art, and a statement confirming the manuscript has not been previously published by any of the authors and/or is not under consideration for publication in another journal at the time of submission.
Suggested Reviewers: Submit names and email addresses of at least six scientists from at least three different countries who could evaluate the work. These suggested reviewers must not be former mentors or mentees nor collaborators or co-authors from the past five years.
Disclosure of previous submissions: If the manuscript was previously rejected by ACS Organic & Inorganic Au, provide the manuscript number and a detailed response to each reviewer's comments. If the manuscript was previously declined by any other journal, even without external peer review, this must be disclosed; however, providing the journal name and additional information is optional.
Disclosure of prior publication & ACS Organic & Inorganic Au preprint policy: Submitted work must not be published elsewhere or concurrently submitted to another journal. Posting submitted manuscripts on a pre-print server is permitted in accordance with ACS Organic & Inorganic Au policy and must be disclosed upon submission to the journal.
Author list with affiliations: List of authors, order of authors, author affiliations, and manuscript title must be the same on all pieces of the submission and match the electronic entry at submission.
Manuscript Type: Article, Letter, Review, Perspective, Correspondence/Rebuttal, or Addition and Correction
Title and Abstract: Be clear and concise, reflect the emphasis and content of the manuscript. Titles and abstracts of manuscripts may not contain the words "New", "Novel", or "First"; "Superb", "Excellent", "Exceptional", "Outstanding" or other similar descriptive words discouraged unless rigorously supported by a thorough comparison with the state-of-the-art in the manuscript. Acronyms and abbreviations are not permitted in manuscript titles, unless they are broadly familiar to readers in all disciplines of chemistry.
Graphics (Figures/Tables/Schemes): Text should be clear and legible, ideally with Arial or Helvetica fonts, with fonts no smaller than 8 pt. Chemical structures should be presented in ACS format. Authors should use drawing packages with journal-based templates, if possible. These contain the appropriate bond widths, bond lengths, fonts, and other settings recommended by ACS Organic & Inorganic Au. Figures must be mentioned in the text in consecutive order and number with Arabic numerals. Avoid inset figures.
References: Include article titles in references.
Safety: Authors must emphasize any unexpected, new, and/or significant hazards associated with the work.
Table of Contents graphic:
required, dimensions of 3.25 inches by 1.75 inches (approx. 8.25 cm by 4.45 cm)
Cover Art (optional): Authors may submit images to be considered for the cover (TIF, JPG, PNG or EPS files with a resolution of at least 300 dpi for pixel-based images). The image size is 8.19 inches (20.8 cm) wide × 10 inches (25.4 cm) high at 300 ppi.
Supporting Information (if any): must be included at the time of electronic submission. Include the heading "Supporting Information" followed by the manuscript title, author list, and affiliations. Tables, Schemes, and Figures should be written as Table S1, Figure S1, Scheme S1, etc. All pages of the PDF Supporting Information should be numbered consecutively. Copies of all related works that are "in press", "accepted", or "submitted" for publication or in the late stages of preparation must be uploaded as Supporting Information for Review Only at the time of submission. References that are only available online should be cited by the Digital Object Identifier (DOI).
Administrative considerations: All manuscripts must not be under consideration or published elsewhere; manuscripts will be screened with plagiarism software; information on whether the manuscript has been previously considered elsewhere must be provided; do not forget to list funding sources and utilize ORCID.
ACS Organic & Inorganic Au is an open access journal that publishes original experimental and theoretical/computational studies on organic, organometallic, inorganic, crystal growth and engineering, and organic process chemistry. Short letters, comprehensive articles, reviews, and perspectives are welcome on topics that include:
Organic chemistry:
Physical and theoretical organic chemistry, including mechanistic studies
Natural products isolation, identification, and synthesis
New synthetic methodology, including single or multistep reactions and total synthesis
Bioorganic and medicinal chemistry
Materials science: Polymer chemistry and studies on functional molecules and systems
Organometallic chemistry:
Synthesis, structure, bonding, chemical reactivity, and reaction mechanisms for a variety of applications, including catalyst design and catalytic processes
All aspects of main-group, transition-metal, and lanthanide and actinide metal chemistry
Synthetic aspects of polymer science and materials science
Bioorganometallic chemistry
Inorganic Chemistry:
Coordination chemistry involving transition metals, lanthanides, and actinides
Main-group and organometallic chemistry
Catalyst design and catalytic processes
Solid-state/materials/nanoscale chemistry
Organic Process Chemistry:
Practical applications of organic chemistry that enable the safe, environmentally benign, and ultimately economical manufacturing of organic compounds at large-scale
Crystal Growth and Engineering:
Organic, inorganic, hybrid solids, biological substances (e.g., biomineralization)
Articles should report a significant advance in a subfield of chemistry, being characterized by the editor and referees as an advance representing the top 10% of articles published annually in that field. Articles must be of high scientific quality, originality, significance, and conceptual novelty. Articles that mainly expand findings that were previously published as Letters in ACS Organic & Inorganic Au or elsewhere and that only incorporate experimental data, without greatly expanded scope and without providing new insights or conceptual breakthroughs, will be declined or recommended for Manuscript Transfer to specialized journals. Similarly, articles that are mainly routine extensions of previously published related work will be declined or recommended for Manuscript Transfer to specialized journals.
Use of the template for Articles is strongly encouraged but is not required. If an author chooses not to use a template to prepare an Article, only Times and Symbol fonts and 1.5 or double line spacing should be used. Other fonts may cause problems when the PDF files used for review are created. Also, if the template is not used, the document mode or its equivalent in the word-processing program should be used; i.e., files should not be saved in "Text Only" (ASCII) mode. If a non-Western version of word- processing software is used to prepare the manuscript, the file should be saved in rich-text format (RTF).
Articles should cover their subjects with thoroughness, clarity, and completeness but should be as concise as possible. Abstracts to Articles are typically limited to 300 words and should summarize the significant results and conclusions.
Letters are short publications that report results whose immediate availability to the science and engineering community is deemed important. A Letter must convey the scientific findings concisely in a brief abstract, main text, and graphical elements as determined by word count not exceeding 2,200 words, including titles/footnotes/captions of approximately five graphics (typically 2 inches long in a single column). References are not included in word count to allow article titles to be included at submission. To calculate word count within the word processing application, select all text from abstract through end of main text (excluding title, authors, affiliations, and content after main text) and view the word processor's word count data. Letters exceeding the word count limit must be shortened before acceptance. Note: ACS Organic & Inorganic Au encourages submission of Letters ranging from approximately 1,200-2,200 words (equivalent to 2-4 formatted journal pages), with more concise submissions appropriate for the most urgent new findings of exceptional significance.
All graphics and tables must be placed near the point of first mention in the text of the manuscript (not grouped at the end of the document) and must be sized according to current guidance. Long notes are not permitted in the References section; information not directly germane to the Letter can be included as Supporting Information. Letters can be complete publications, but follow-up publication may be justified when the research is continued and a more complete account of the work is deemed necessary, especially for the most urgent concise Letters noted above. Special efforts will be made to expedite the reviewing and the publication of Letters. The time for proofreading the galley proofs is relatively short. For this reason, authors of Letters should ensure that manuscripts are in final, error-free form when submitted. A template for Letters is available.
Reviews are topical, forward looking, and of general interest to the readership. Length is flexible (6–20 or more pages). A good review critically evaluates existing work of multiple groups in a field or across disciplines, provides a logical organization, and makes the material more easily available to those not expert in the area through clear text and figures. Reviews should lay out the challenges and opportunities that lie ahead. Reviews should contain an abstract and appropriate references. The use of graphics to illustrate key concepts is strongly encouraged. Reviews include a graphical Table of Contents entry. Reviews also include ~8–10 keywords and a vocabulary section in which 5–7 terms extracted from the text are defined in one or two sentences.
Perspectives are personal reviews of a field or area by one or a small team of authors, and they are focused rather than comprehensive. Perspective authors are asked to assess the current status of the field with an emphasis toward identifying key advances being made or those advances that are needed, and with an eye to the future. The ACS Organic & Inorganic Au Perspective should touch base with the current literature, including key contributors and references, but will primarily serve to inspire and help direct future research efforts. Authors may be invited by the Editor to submit Perspectives. Authors interested in submitting a Perspective are strongly encouraged to contact the Editor prior to manuscript preparation and submission, to seek conditional approval of the proposed topic. One-page proposals should be sent to the Editor, Geraldine Masson (masson-office@orginorgau.acs.org), for consideration. Perspectives may not exceed 10,000 words in abstract, main text, and graphical elements.
Correspondence/Rebuttal. Correspondence is a technical contribution providing, with supporting material, a respectful but alternative point of view to a publication that has appeared in ACS Organic & Inorganic Au. The author of the original publication may be invited to write a Rebuttal. The Correspondence and Rebuttal will appear in the same issue of the journal, when possible.
ACS Organic & Inorganic Au does not require the use of any document templates. General information on the preparation of manuscripts may be found in the ACS Guide to Scholarly Communication.
The letter must provide the corresponding author's name, title, affiliation, and e-mail address. All Editorial correspondence concerning receipt, status, review, revision, and publication of a manuscript will be sent only to one person who has been designated as the corresponding author during the evaluation period. The corresponding author is responsible for communicating the manuscript status to all co-authors of the manuscript and for obtaining the co-authors' assent to any substantial changes of content or interpretation made during revision. While a cover letter with designate a single corresponding author who serves as the primary contact during the submission and review process, additional corresponding authors may be designated with asterisks in collaborative manuscripts, with the number of corresponding authors not to exceed three.
The cover letter must include a paragraph explaining why your manuscript is appropriate for ACS Organic & Inorganic Au. This paragraph should clearly indicate what key advance(s) is/are described in the work. The letter may suggest the name of an appropriate ACS Organic & Inorganic Au Associate Editor. However, manuscript assignment to an Associate Editor is ultimately at the discretion of the Editor-in-Chief. Non-preferred Associate Editors and reviewers may be denoted in the cover letter, along with a reason for their designation.
The cover letter should provide explicit assurance that the manuscript is not under consideration for publication and has not been published elsewhere. Please note any submission to a preprint server such as ChemRxiv, bioRxiv, or arXiv in the cover letter and include a link to the preprint, and as appropriate, state how the manuscript has been adjusted/updated between deposition and submission.
Title. Titles should clearly and concisely reflect the emphasis and content of the manuscript. Titles are of great importance for current awareness and information retrieval and should be carefully constructed for these purposes. Titles of manuscripts may not contain the words "New" or "Novel" nor any part number or series number without permission from the Editor. Claims of precedence should not be made in a title, so use of "First" in titles for this purpose is prohibited. Additionally, "Superb", "Excellent", "Exceptional", "Outstanding" or other similar descriptive words, are strongly discouraged. Acronyms and abbreviations are not permitted in manuscript titles, unless they are broadly familiar to readers in all disciplines of chemistry. Titles should not be phrased as a question.
Author List. Bylines should include all those who have made substantial contributions to the work. To facilitate indexing and retrieval and for unique identification of an author, use first names, initials, and surnames or first initials (e.g., Jody R. Smith), second names, and last names (e.g., J. Riley Smith). Do not use only initials with surnames (e.g., J. R. Smith). Deceased persons who meet the criteria for inclusion as coauthors should be included, with an Author Information note indicating the date of death. Do not include professional or official titles or academic degrees. At least one, or optionally more than one but fewer than four authors must be designated with an asterisk as the author(s) to whom reader correspondence regarding the published manuscript may be addressed.
The full names and e-mail addresses of all co-authors must be provided on the Authors & Institutes page upon submission of the manuscript in ACS Paragon Plus. Use of ORCID identifiers is encouraged.
Addition or deletion of an author or authors after submission of the manuscript requires justification from the corresponding author and is subject to approval by the Editor.
Institution Address. The author affiliation(s) listed should be the institution(s) where the work was conducted. If the present address of an author differs from that at which the work was done, that address should be given in an Author Information note.
Many Funders and Institutions require that institutional affiliations are identified for all authors listed in the work being submitted. ACS facilitates this requirement by collecting institution information during manuscript submission under Step 2: Authors and Affiliations in ACS Paragon Plus.
Abstract. All Articles, Letters, and Perspectives) must be accompanied by an abstract, including an Abstract (TOC) graphic, which should state briefly the purpose of the research, the principal results, and major conclusions. Abstracts of manuscripts may not contain the words "superb", "excellent", "exceptional", "outstanding", or other similar descriptive words unless rigorously supported by a thorough comparison with the state-of-the-art in the manuscript. Like manuscript titles, the words "New", "First", or "Novel" are also generally disallowed in the abstract. The abstract should not generally exceed 200/300 (Letter/Article) words. Pasting the abstract in the text box on the Web submission page does not replace the need for including an abstract in the manuscript document.
Keywords. All Articles, Letters, and Perspectives must be accompanied by 5–8 keywords. These keywords will appear in the PDF version of the article and will also be used as a search term in the HTML version of the article.
Text (Articles). The first paragraphs of an Article should explain the motivation for and import of the work, where it fits in the development of the field and of chemistry, and perhaps why it should be of interest to chemists in other areas. It should be possible to do this without excessively increasing the length of the Article. Extensive reviews of the literature cannot be accepted. Thoughtful use of schemes and figures (with well-composed captions) is recommended, so that even casual browsers can discern the nature of the work. Well-known procedures should be designated by name, or literature references to them should be given. Experimental results are of lasting value and should be clearly and logically presented in a separate section. Standard Article format must be used for preparing a manuscript for submission as an Article, including section headings and a proper Introduction, a complete Experimental Section (unless placed in the Supporting Information), Results, and Discussion. The addition of a Conclusion section at the end of the manuscript, which briefly summarizes the principal conclusions of the work, is recommended. If desired for clarification, section headings may be given Arabic numbers and subsections numbered in decimals (e.g., subsection 2.1 and subsection 2.2).
Text (Letters). Section headings (Introduction, Experimental Section, Conclusion, etc.) should not be used in a Letter.
Safety. Authors must emphasize any unexpected, new, and/or significant hazards or risks associated with the reported work. For each manuscript that reports experimental procedures, authors must include an affirmative statement about safety in the Experimental Section of the full article or the main text of a Letter. Further information may be included or re-introduced in the Supporting Information.
Appendices. Appendix sections must be placed in the Supporting Information.
Dedications. All dedications must appear in the Acknowledgment section and are subject to approval by the Editor.
Abbreviations. Acronyms and abbreviations that are not broadly familiar to readers in all disciplines of chemistry should be introduced in parentheses following the full term on its first appearance in the text. Do not include a separate Abbreviations list.
Acknowledgment. Dedications and notes acknowledging financial or professional assistance to the conduct of research or indicating presentation at a meeting should be brief and placed in the Acknowledgment section.
Author Information Notes. The e-mail address(es) of the corresponding author or authors must be provided as a Corresponding Author note. Present addresses for individual authors that differ from the address(es) at which the work was done should be given in a Present Address(es) note.
Statements about author contributions to the work or equal contributions of work should be included as a separate statement.
References and Footnotes. All the references and footnotes must be placed together in a list at the end of the manuscript text. In the Web edition, many of them will have links to other Web resources, such as the corresponding abstracts in Chemical Abstracts and the full text from other American Chemical Society journals. Because of this electronic linking, and to aid scientific research, it is crucial that authors verify the accuracy of all references.
Unnecessarily long lists of references should be avoided, and excessive self-citation is not permitted. However, authors must reference all previous publications in which portions of the present work have appeared. Each literature reference should be assigned one number and placed in the text as a superscript Arabic numeral. Footnotes to the text should be combined with references and numbered in ordinal sequence. Long footnotes should be avoided in Articles and are not permitted in Communications; additional data and peripheral discussion should be placed in the Supporting Information rather than in footnotes.
Bibliographic references to classified documents and reports or references to unpublished materials that are not generally available to the scientific public should not be used. Authors must obtain written permission from any person whose work is cited as a personal communication, unpublished work, or work in press. Copies of letters of permission and documentation should be appended to the cover letter file. If the manuscript is accepted but the necessary permissions have not been received, the Editor will ask the author to remove the reference(s) and dependent text.
List submitted articles as "in press" only if they have been formally accepted for publication. Otherwise, use "unpublished work" with the name of the place where the work was done and the date. For work published online (ASAP, in press), the DOI should be furnished in addition to the author name(s), article title, journal name, and year. DOI is an accepted form of citation before and after the article appears in an issue.
Example of a journal reference:
Yue, Q.; Liu, W.; Zhu, X. n-Type Molecular Photovoltaic Materials: Design Strategies and Device Applications. J. Am. Chem. Soc. 2020, 142, 11613–11628.
Example of an in-press journal reference:
Ham, J. S.; Park, B.; Son, M.; Roque, J. B.; Jurczyk, J.; Yeung, C. S.; Baik, M.-H. ; Sarpong, R. C–H/C–C Functionalization Approach to N-Fused Heterocycles from Saturated Azacycles. J. Am. Chem. Soc. 2020, DOI: 10.1021/jacs.0c04278.
Example of a reference to a book with no editors:
Desiraju, G. R.; Vittal, J. J.; Ramanan, A. Crystal Engineering: A Textbook. World Scientific Publishing Co Pte Ltd: Singapore, 2011.
Example of a reference to a book with editors:
Byrn, S. R.; Stowell, J. G. Impurities in Drug Substances and Drug Products. In Validation of Active Pharmaceutical Ingredients; Berry, I.R., Harpaz, D., Eds.; CRC Press: Boca Raton, 2001; pp 271–292.
Authors should consult the ACS Guide to Scholarly Communication for the appropriate style to use in citations of journal articles, books, and other publications. In literature references, article titles must be included and journal abbreviations should be those used in the Chemical Abstracts Service Source Index (CASSI).
Compound Characterization, Experimental and Computational Data
Authors are required to provide sufficient information (as described in more detail below) to establish the identity of a new compound, its purity, and its yield. Sufficient experimental details must also be included to allow another researcher to reproduce the synthesis. Safety: Authors must emphasize any unexpected, new, and/or significant hazards or risks associated with the reported work. This information should be in the experimental details section of the full article or communication. Characterization data and experimental details must be included in either the paper or the Supporting Information. Guidelines for reporting NMR data are available online. Note that, when possible, unambiguous peak assignments should be given for all NMR spectra.
Characterization of New Substances. Adequate evidence to firmly establish both identity and purity should be provided. Recommended criteria vary according to substance categories. A summary of the detailed criteria may be found below.
Guidelines for Characterization of Organometallic and Inorganic Compounds
Authors are required to provide sufficient information (as described in more detail below) to establish the identity of a new compound, its purity, and its yield. Sufficient experimental details must also be included to allow another researcher to reproduce the synthesis. Characterization data and experimental details must be included in either the manuscript or the Supporting Information. It must be emphasized that the following is only a general guideline and authors are encouraged to present as much data as possible to support their structure assignments. In some cases, a reviewer or Editor may require authors to submit additional data to satisfy themselves of the validity of a proposed formulation.
Characterization Data
(a) Routine Compounds
Compounds in this category are those that have either literature precedents or are obtained by a logical synthesis in close to quantitative yield. Because of potential misidentification of atoms, an X-ray diffraction structure alone will not typically be considered to provide sufficient characterization for these molecules. Diamagnetic compounds must also be characterized by NMR spectroscopy, preferably for at least two different nuclei. In addition, at least one other characterization technique must be used to support the proposed formulation. Preferably, this would be a technique that provides definitive identification of a key functional group or chromophore. For example, IR spectroscopy may be used to support the presence of carbonyl, acyl, dinitrogen, carbonyl, and hydride moieties.
Paramagnetic compounds of this category present a further complication if NMR spectroscopy does not furnish clear evidence for the proposed formulation (note that NMR spectroscopy of paramagnetic complexes can be useful if sufficiently large sweep widths are used). In many cases, X-ray diffraction may provide the most unambiguous characterization of such complexes, but this will not suffice as the only means of characterization. In the absence of an X-ray structure determination, evidence for elemental constitution must be provided by elemental analysis (e.g., combustion analysis, microprobe analysis), or mass spectrometry. Magnetic moment and/or ESR spectroscopic data should also be given for paramagnetic compounds if it is considered that the spin state of the molecule is of special interest.
(b) Novel or Unexpected Compounds
Compounds in this category are those that either (i) exhibit an unprecedented type of structure, or (ii) are obtained by unexpected reaction. Such compounds require more detailed characterization to ensure their validity. In select instances, a variety of definitive spectroscopic techniques may provide sufficient characterization (for example, if many of the nuclei are NMR active), but in the majority of cases evidence for elemental constitution must be provided by either elemental analysis (e.g. combustion analysis, microprobe analysis), or mass spectrometry. While an X-ray diffraction structure is not considered definitive proof of elemental composition, it is acceptable evidence for composition providing that the results of other physical methods concerning the characterization are conclusive.
(c) Solid State Materials
Compounds in this category are those that have no existence in solution. These materials must be characterized in such a way as to sufficiently describe their structure and composition. Atomic ratios and elemental compositions must be provided for solid state materials. X-ray diffraction data should be provided for crystalline materials.
(d) Compounds that have not been isolated
Compounds that have not been isolated in pure form (e.g. reaction intermediates or intractable mixtures, or unstable species) may be published. However, in these circumstances, an explicit statement must be given indicating that the compounds have not been isolated. Only in exceptional circumstances will an article be published in which none of the new compounds reported has been isolated and fully characterized.
Purity and Yield
The yield and purity of all compounds must be reported, including the methods used to determine them. The yield of a compound obtained in an NMR tube reaction should be determined using an internal standard.
Guidelines for Characterization of Organic Compounds
Sample Quality
For new substances, evidence of the homogeneity the purified sample should be included. Elemental analysis is sufficient. If no analysis was performed, then other evidence (for example, 1H NMR, 13C NMR, HPLC, gel electrophoresis, etc.) should be included as figures in the Supporting Information.
Evidence of molecular weight should be provided, especially if elemental analysis was not performed. Low resolution MS data under conditions that minimize fragmentation are acceptable. If there is a specific need to distinguish alternative formulas with the same molecular mass (within one amu), then HRMS data are necessary.
Numerical listings of characteristic spectroscopic data should be included to support assigned structures, changes in functionality, unusual chromophores, properties, etc. Methods of purification used to prepare samples for characterization should be described. For crystalline samples, information about the method of crystallization should be included (solvents; mp; etc.). For non-racemic, chiral substances, data to allow correlation of absolute configuration should be given, preferably including [α]D values. If correlation data are provided based on HPLC or related methods, then retention times for both enantiomers must be provided, together with solvent and flow rate information, and identification of the chiral support.
Intermediates on Solid Phase; Combinatorial Chemistry
Validation of methods and characterization of new substances in a statistically significant sampling should be provided. Resin-bound intermediates need not be characterized if acceptable end product quality (as defined in three section above) is demonstrated.
Kinetic and Equilibrium Data. For publication in the ACS Organic & Inorganic Au, the reporting of kinetic data and equilibrium binding data for proteins, nucleic acids, and other species should preferably include a description of the identity of the catalyst or binding molecule, its origin, purity of composition, and any modifications such as mutations, post-translational modifications, or other modifications made to facilitate expression and purification. The method of assay and the exact experimental conditions of the assay should be provided as a reference to previous work, with or without modifications, or fully described if a new assay. Conditions essential to reproduce the results such as the temperature, pH, and pressure (if other than atmospheric) of the assay should be included. Terms such as "not detectable" (ND) should be avoided. Instead, an estimate of the limit of detection based on the sensitivity and error analysis of the assay should be provided. Authors are referred to the STRENDA (Standards for Reporting Enzymology Data) Commission of the Beilstein Institut (http://www.beilstein-institut.de/en/projects/strenda/guidelines) for an example of detailed guidelines.
Reporting and Stewardship of NMR Data. The NMR Guidelines recommend a standard baseline for the submission of NMR data to ACS journals. They are intended to promote accuracy and consistency. The guidelines are divided into three sections: NMR text, which outlines the preferred format for NMR data included in the Experimental Section; NMR spectra, which outlines the preferred format for inclusion of hard copies of spectra in the Supporting Information; and primary NMR data files, which outlines the procedure for submitting FID files, acquisition data, and processing parameters to include in the Supporting Information. Authors are strongly encouraged to provide all three sets of data for all new and/or key compounds described in a manuscript submission.
In the Experimental Section, the compound must be clearly identified, for example in a header at the beginning of the synthetic procedure or the summary of spectroscopic data. List the nucleus being measured, any nucleus being broad-band decoupled, the solvent used (formula preferred, e.g. C6D6 over benzene-d6), the standard used, and the field strength. Field strength should be noted for each spectrum, not as a comment in the general Experimental Section. The standard(s) may be specified in the general Experimental Section; as an example, 1H NMR data recorded in C6D6 listed as "residual internal C6D5H (δ 7.15)". Indicate solvent or peak suppression protocols used in collecting data. List the probe temperature when it is accurately known; ambient probe temperature is otherwise understood. Give 1H NMR chemical shifts to two digits after the decimal point. Include the number of protons represented by the signal, peak multiplicity, and coupling constants as needed (J italicized, reported with up to one digit after the decimal). The number of bonds through which the coupling is operative, xJ, may be specified by the author if known with a high degree of certainty. Accepted abbreviations for multiplicities and descriptors are s = singlet, d = doublet, t = triplet, q = quartet, quint = quintet, m = multiplet (denotes complex pattern), dd = doublet of doublets, dt = doublet of triplets, td = triplet of doublets, and br = broad signal.
Chemical shifts should be listed consistently in a single article, starting either from downfield to upfield or vice-versa. Assign peak identities under the following circumstances: non-decoupled or equivalent spectra have been collected (13C, 31P, etc.); 2-D experiments have been performed; or unambiguous assignment is possible without additional experiments, such as in the case of an organometallic metal-hydride 1H signal, PF6 vs MPPh3 31P signal, etc. Give 13C chemical shifts to one digit after the decimal point, unless an additional digit will help distinguish overlapping peaks. Include peak multiplicities for 1H-coupled 13C NMR spectra or for signals in 1H-decoupled spectra that are coupled to other magnetically active nuclei. A 13C NMR signal will be considered a singlet if the multiplicity is not assigned. Only rarely is a true multiplet observed in a 13C{1H} NMR spectrum. However, a certain region may contain a group of unresolved peaks or signals. Mention of unobserved resonances is encouraged.
Submission of spectra (.doc, .docx, .txt, .pdf, .tif) is strongly recommended for all new and/or key compounds, following these guidelines:
A caption should be included on the spectrum, noting the nucleus being measured, the solvent (formula preferred, e.g. C6D6 over benzene-d6) and the field strength.
A representation of the compound should be included on the spectrum—please use ChemDraw or a related program. The compound identifier used in the manuscript should be included.
The largest peak in the 1H NMR spectrum should normally arise from the compound, not the solvent.
All peaks in the 1H NMR spectrum should be integrated. Chemical shift values should be included.
The solvent peak should be clearly labeled on the spectrum.
All peaks should be visible on the spectrum. Insets are encouraged to show expanded regions. At minimum, the spectral window should be ‒1 ppm to 9 ppm for 1H NMR and ‒10 ppm to 180 ppm for 13C NMR.
Font should be clear and large enough to read (minimum of 10 point). Horizontal orientation is preferred for spectra.
Submission of primary NMR data files (FID files, acquisition data, processing parameters) is encouraged for all new and/or key compounds. When submitting these files, please consider the following guidelines:
One folder should be created for each compound. The folder should be named clearly, using the compound name (if available) and compound identifier, as referenced in the Experimental Section or Supporting Information. Include the FID files, acquisition data, and processing parameters for each experiment.
Name each spectrum according to the type of nucleus measured. 1H, 13C, DEPT, COSY, etc. NMR files should be compressed into zip files—please use multiple zip files if necessary. Files must be submitted in their native format. In a text document, include the name of the manufacturer of the spectrometer used to collect the data, the acquisition software and processing programs used to analyze the data, and the field strength used to measure each nucleus (i.e., 300 MHz 1H or 50 MHz 13C). Include a structure file that shows the structure and compound identifier for each provided dataset. MolFile is the recommended format and is strongly preferred.
Nuclear Magnetic Resonance Pulse Sequences. For manuscripts that present new NMR pulse sequences, authors are requested to supply as "Supporting Information for Publication" a file that includes the original working pulse sequence information required to record data. This will typically include the pulse sequence code, parameter set, and other associated files, such as tables of gradient or pulse shapes.
Structural and Chemical Shift Data for Proteins and Nucleic Acids. Any set of atomic coordinates referred to in the manuscript, including atomic coordinates and structure factors for proteins determined by X-ray crystallography and coordinates determined by NMR, should be deposited with the Protein Data Bank, Research Collaboratory for Structural Bioinformatics at Rutgers University whenever appropriate. (Theoretical model depositions are no longer accepted for inclusion in the PDB archive.) If the coordinate files are not deposited in the PDB, or if the PDB files are on hold until publication, then the coordinate files must be included in the Supporting Information submitted concurrently with the manuscript. Requirements are similar for structures of nucleic acids, which should be deposited with the Nucleic Acid Database. A manuscript that does not provide coordinates at the time of submission will not be sent out for review. It is the responsibility of the author to obtain a file name (PDB ID or NDB ID) for the molecule; the file name must appear in the published manuscript. If a file name has not yet been obtained upon acceptance of a manuscript, it must be added in proof. Atomic coordinates and structure factors for all structures mentioned must be available immediately upon publication of the article, either directly in the Supporting Information or as a data bank deposition. Similar requirements also apply to any chemical shifts referred to in the manuscript, whether they are only for assignment of resonances or used for any form of structure calculation. Those chemical shifts must be available to the reviewer at time of submission, either as an available entry in the Biological Magnetic Resonance Data Bank or included directly as Supporting Information.
Single Crystal Diffraction Data. Manuscripts reporting the determination of one or more structures by X-ray diffraction must adhere to the following requirements:
Abstract. The abstract may summarize geometric features of unusual interest but should not contain unit cell parameters.
Main Body of Manuscript. Tables of essential interatomic distances and angles are not required but may be submitted (metric information for standard structural components should not be included).
For structures with anisotropically refined atoms, a figure displaying the thermal ellipsoids should ordinarily be presented; a spherical-atom representation may be substituted if necessary for clarity. If a spherical atom view is chosen for the manuscript, a thermal ellipsoid figure should be included in the Supporting Information. In cases where intermolecular interactions are relevant to the discussion, a view of the unit cell may be included.
An Article should list for each structure the formula, formula weight, crystal system, space group, color of crystal, unit cell parameters, temperature of data collection, and values of Z, R, and GOF; a brief description of data collection and solution and refinement of the structure should be placed in the Experimental Section. Tables of atom coordinates and thermal parameters will not be printed.
Supporting Information. Complete detailed data for each structure must be submitted in the electronic Crystallographic Information File (CIF) format. Deposition of CIF files in the Cambridge Crystallographic Data Centre (CCDC) does not eliminate the ACS Organic & Inorganic Au requirement to submit the CIF file(s) as Supporting Information. See Requirements for Depositing X-Ray Crystallographic Data [PDF] for complete details on submission of CIFs and a list of file types accommodated by CCDC.
Authors are requested to combine multiple CIFs for a given manuscript into a single file. The individual structures in the combined file are to be separated from each other by the sequence #===END at the beginning of a new line. ACS Organic & Inorganic Au requires authors to run the CheckCIF program for each crystallographic structure and to correct any syntax errors in the CIF file prior to submission. Authors should consult the CIF Submission Instructions listed below during manuscript preparation.
Structure factors (except for proteins and nucleic acids) should not be submitted as Supporting Information. However, one printed table of structure factors should be retained in case it is requested by the Editor for review purposes only.
CIF Submission Instructions:
Authors are encouraged to submit X-ray crystallographic data to be published as Supporting Information. The information required for each structure should be submitted in the electronic CIF format. Such files should be submitted electronically as described below.
CIFs must be uploaded at the same time the manuscript is submitted via the Web, with the file designation Supporting Information for Publication. The CIF for each structure should be uploaded as a separate Supporting Information file. CIFs should be saved in the text-only (plain ASCII) format, with a .cif extension before being submitted. No information other than the CIF itself should be included inside the file. CIFs may NOT be furnished as Microsoft Word, Corel WordPerfect, or PDF files.
Before submission, CIFs must be checked using the CheckCIF utility on the Web at http://checkcif.iucr.org/. A copy of the output should be retained in case it is requested by an Editor. Authors with appropriate software may alternatively use IUCRVAL or the CHECK validation tool in PLATON.
If CIFs are not available, the required data should be furnished in neatly formatted tables with informative titles that identify the name or the structure number of the compound.
Powder Diffraction Data. The presentation of X-ray powder diffraction data for new materials or for materials previously uncharacterized by this technique is encouraged. Data from X-ray powder measurements should be accompanied by details of the experimental technique: source of X-rays, the radiation, its wavelength, filters or monochromators, camera diameter, the type of X-ray recording, and the technique for measuring intensities. In cases of unindexed listing of the data, the d spacings of all observed lines should be listed in sequence, together with their relative intensities. In cases where filtered radiation is used, every effort should be made to identify residual β lines. Where resolution into α1-α2 doublets occurs, the identification of the d spacing for each line as dα1, dα2 gives a measure of the quality of the diffraction pattern. When an indexing of the data is offered, the observed and calculated 1/d2 values should be listed along with the observed relative intensities (it is superfluous to give d spacings in this instance). All calculated 1/d2 values should be listed (exclusive of systematic absences), to the limit of the data quoted. If possible, the crystal system should be specified. Possible space groups may also be listed if the data warrant it. Relevant information about the specimen used should be included.
Magnetic Measurements. Fits of magnetic data [χ(T), χ-1(T), χT(T), μ(T), M(H), etc.] to an analytical expression must include both the Hamiltonian from which the analytical expression is derived and the final analytical expression and fitting parameters. When the value of an exchange coupling constant, J, is given in the abstract, the form of the Hamiltonian must also be included. The expressions may be included in the manuscript or, if long and complex, as Supporting Information; if the latter method is used, it should be noted in the Supporting Information paragraph at the end of the manuscript. In addition, how the sample was measured (in a gelatin capsule, Teflon capsule, etc.) and the diamagnetic correction for the sample holder, as well as the diamagnetic correction for the material, must be provided and the manner in which it was calculated (Pascal's constants) or measured must be stated.
Computations. When computational results are an essential part of a manuscript, sufficient detail must be given, either within the paper or in the Supporting Information, to enable readers to reproduce the calculations. This includes data such as force field parameters and equations defining the model (or references to where such material is available in the open literature). If the software used for calculations is generally available, it must be properly cited in the References and Footnotes. References to the methods upon which the software is based must also be provided. Results obtained from methods or parameters that are not adequately described in the manuscript or in the literature are not acceptable for publication. Authors who report the results of electronic structure calculations are requested to provide as Supporting Information the geometries (either as Cartesian coordinates or Z matrices) of all the stationary points whose relative energies are given in the manuscript. The absolute energies in hartrees that are computed at these geometries should not be given in the manuscript but should be included in the Supporting Information. Where applicable, the number of imaginary frequencies should be reported to identify stable structures and transition states.
Submission of a manuscript to ACS Organic & Inorganic Au is contingent upon the agreement by all the authors that the reported work has not received prior publication and that no portion of this or any other closely related work is under consideration for publication.
ACS Organic & Inorganic Au authors may deposit an initial draft of their manuscript in a preprint service such as ChemRxiv, bioRxiv, arXiv, or the applicable repository for their discipline before the manuscript is accepted for publication in ACS Organic & Inorganic Au. Authors may revise the preprint version of their manuscript up until a final acceptance decision has been issued. Please note any use of a preprint server in the cover letter and include a link to the preprint, and as appropriate, state how the manuscript has been adjusted/updated between deposition and submission. All other prior/redundant publication is forbidden. Upon publication in ACS Organic & Inorganic Au, authors should add a link from the preprint to the published article via the Digital Object Identifier (DOI). Some preprint servers, including ChemRxiv and bioRxiv, add this link for authors automatically after publication. For further details, contact the Editorial Office. For the ACS Publications policy on theses and dissertations, click here.
Open Access and Article Publishing Charges at ACS Organic & Inorganic Au:
ACS Organic & Inorganic Au is a fully open access journal, with all content published under an open access license. There is therefore no subscription charges and no charge to access, read, and download articles published in the journal. Authors of accepted manuscripts will need to pay an Article Publishing Charge (APC) to publish their research in ACS Organic & Inorganic Au. The default license for authors will be CC-BY-NC-ND, with the option to upgrade to CC-BY. Discounts are available for ACS Members and further country discounts apply for authors based in countries with lower-income economies, detailed here. Authors from institutions with ACS Read + Publish Agreements are eligible to have their APC covered through these agreements. Information can be found here.
Pricing details can be found here. For assistance with open access, please contact support@services.acs.org.
Anonymity of Peer Review
All manuscripts are subject to critical, single-anonymized peer review. It is to be understood that the final decision relating to a manuscript's suitability rests solely with the Editor. The journal disapproves of attempts by authors to determine the identity of reviewers. This journal's policy is to neither confirm nor deny speculation about the identities of reviewers.
Authors are required to provide the names of at least four reviewers, working in at least three different countries, competent to referee their manuscripts. They may also suggest in their cover letter that certain individuals not be used as referees along with justification for the request. Such requests will generally be honored by the Editors, unless it is believed that the specific individual's opinion is vital in the consideration of the manuscript. Authors are encouraged to avoid suggesting reviewers from the authors' institutions. Do not suggest reviewers who may have a real or perceived conflict of interest. Whenever possible, suggest academic email addresses rather than personal email addresses.
Authors publishing in ACS Organic & Inorganic Au retain copyright of their published research and may publish via a choice of CC-BY-NC-ND or CC-BY license. ACS offers options by which authors can fulfill the requirements for open access and deposition into repositories for funded research. Visit our Open Science site to see how to fulfill requirements for specific funders and to find out if you are eligible to publish under a Read + Publish agreement between ACS and your institution. You can also find out more about Open Access Compliance and ACS Open Science initiatives.
ACS Organic & Inorganic Au authors are encouraged to submit images to be considered for use on the journal's front cover or Supplementary Covers at the time of the submission of their revised manuscript. If your article is accepted for publication, your suggestion may also be selected for use on one of the journal's covers. If your art is selected for front cover, ACS will send you information about how to request one complimentary 18" by 24" printed poster featuring your work.
Cover image submissions should be colorful and visually engaging, with minimal text. The cover image should not resemble a graphical abstract or data figure, but rather should be an artistic and scientifically accurate representation of the manuscript.
Image files should be submitted as TIF, JPG, PNG or EPS files (not PDF or PPT) with a resolution of at least 300 dpi for pixel-based images. Cover art should be 8.19 inches (20.80 cm) wide × 10 inches (25.4 cm) high at 300 ppi, and submission of "layered" artwork is encouraged. The journal's logo will obscure the top 2.5 inches (6.35 cm) of the image. Authors should submit the cover image, along with a short (< 50-word), clear legend explaining the image, as supplementary files to ACS Paragon Plus with their revised manuscript.
If you wish to be considered only for the front cover, and not a paid supplementary cover, please respond NO accordingly to the Supplementary Cover Art question in ACS Paragon Plus. For more information on the Supplementary Covers program, please see this webpage. All art submitted for consideration for a supplementary cover will also be considered for a front cover.

redpajama_set_name: RedPajamaCommonCrawl


text:
Shape Shape
Explore Shape
The Keto Meal Plan for Beginners
Everything you need to know to get started with this high-fat, low-carb diet. Read More
10 Things I Learned During My Body Transformation
Twenty months and 17 pounds later, I came away with 10 big lessons. Read More
Your Guide to Strength Training for Beginners
This total-body beginner weight lifting routine is the easiest way to ease into strength training as a newbie. Read More
Exercise Recovery
Exercise Tips
See All Celebrities
Celebrity Workouts
Healthy IRL
See All Video
Weight Loss Videos
Workout Shoes
Shape.com
Sharon Stone Proves 50s Are Fabulous on the March Cover of Shape
By Ashley Ross February 17, 2014
sharon700x700_0.jpg
It's not easy to look sexy at 56, but Sharon Stone, who became a sex symbol 22 years ago in Basic Instinct, makes it look as much on the March cover of Shape. Stone is currently juggling motherhood (she has three boys), a role in the upcoming romantic comedy Fading Gigolo, and the new TNT series Agent X.
The star doesn't look this good by faking it either. She decided to focus on aging gracefully rather than fading into the youth-obsessed standards of beauty. "This idea that being youthful is the only thing that's beautiful or attractive simply isn't true. I don't want to be an 'ageless beauty.' I want to be a woman who is the best I can be at my age." In her new cover story, she touches on the fact that many surgeons have tried to get her to go under the knife for a face-lift. Her biggest concern with plastic surgery is that everyone is starting to look the same. "We've got 400,000 girls with beachy blonde hair, the same nose, gigantic lips, implants in their cheeks, and little Chicklets for teeth. Are they really prettier?" she says.
But she hasn't always been this confident. "There was a point in my 40s when I went into the bathroom with a bottle of wine, locked the door, and said, 'I'm not coming out until I can totally accept the way that I look right now.' She eventually decided to move forward with a healthy mindset, keeping herself fit through exercise and plenty of stretching. Unlike some celebrities with private gyms, she swings by 24-Hour Fitness for her workouts. And her routine is anything but. "Every time I exercise, I do something different based on which areas need to get in motion," she says. She credits her physique to total-body stretches, strength straining, yoga, and dance. She proves you can fit in a workout anywhere, and we mean anywhere. "Sometimes I do a series of standing leg lifts and circles in the tub, using the water as resistance."
Her diet has changed a lot since growing up in 1970s Pennsylvania when every meal included mashed potatoes and gravy. Stone prefers eating steak, porterhouse, rib eyes, and New York strip, and can do so because of her low cholesterol and low blood pressure. She also steers clear of alcohol completely. After battling weight gain in her twenties, she learned how to discipline herself by following in the footsteps of Jane Fonda, and she's gracefully accepting her body's changes. "I'm not trying to make myself look like a girl because I'm not a girl anymore. I'm very happy about being a grown woman. I think there's a lot of sexuality, and glamour, and allure, and mystery to being a woman that you just don't have when you're young."
For more from Stone, plus her exclusive total-body workout, pick up the new issue of Shape, on stands and iPads nationwide February 24.
By Ashley Ross
Shop | Shape
Plus Size Cothing
Shape may receive compensation when you click through and purchase from links contained on this website.
MeredithShape is part of the Instyle Beauty Group. © Copyright 2022 Meredith Corporation. All Rights Reserved. Privacy Policythis link opens in a new tab Terms of Servicethis link opens in a new tab Ad Choicesthis link opens in a new tab California Do Not Sellthis link opens a modal window Web Accessibilitythis link opens in a new tab
© Copyright Shape. All rights reserved. Printed from https://www.shape.com


text:
Tikuna is een geslacht van haften (Ephemeroptera) uit de familie Leptophlebiidae.

Soorten
Het geslacht Tikuna omvat de volgende soorten:
Tikuna atramentum
Tikuna bilineata
Tikuna fusconotum
Tikuna nigrobulla

Leptophlebiidae

redpajama_set_name: RedPajamaWikipedia


What Is a Dolphin's Hearing Range?
How Would You Describe a Dolphin?
What Is Some Dolphin Information for Kids?
What Is a High Pitch Noise That Adults Can't Hear?
What Is a Flatworm's Habitat?
What Is the Temperate Grasslands Food Chain?
What Animals Live in Arica, Chile?


text:
package de.tum.in.www1.artemis.programmingexercise;

import java.io.IOException;
import java.net.MalformedURLException;
import java.net.URISyntaxException;
import java.util.List;
import java.util.Set;

import org.gitlab4j.api.GitLabApiException;
import org.springframework.http.HttpStatus;

import com.fasterxml.jackson.core.JsonProcessingException;

import de.tum.in.www1.artemis.domain.*;
import de.tum.in.www1.artemis.domain.participation.AbstractBaseProgrammingExerciseParticipation;
import de.tum.in.www1.artemis.domain.participation.ProgrammingExerciseStudentParticipation;
import de.tum.in.www1.artemis.service.connectors.bamboo.dto.BambooBuildResultDTO;

public interface MockDelegate {

    void mockConnectorRequestsForSetup(ProgrammingExercise exercise, boolean failToCreateCiProject) throws Exception;

    void mockConnectorRequestsForImport(ProgrammingExercise sourceExercise, ProgrammingExercise exerciseToBeImported, boolean recreateBuildPlans) throws Exception;

    void mockImportProgrammingExerciseWithFailingEnablePlan(ProgrammingExercise sourceExercise, ProgrammingExercise exerciseToBeImported, boolean planExistsInCi,
            boolean shouldPlanEnableFail) throws Exception;

    void mockConnectorRequestsForStartParticipation(ProgrammingExercise exercise, String username, Set<User> users, boolean ltiUserExists, HttpStatus status) throws Exception;

    void mockConnectorRequestsForResumeParticipation(ProgrammingExercise exercise, String username, Set<User> users, boolean ltiUserExists) throws Exception;

    void mockUpdatePlanRepositoryForParticipation(ProgrammingExercise exercise, String username) throws IOException, URISyntaxException;

    void mockUpdatePlanRepository(ProgrammingExercise exercise, String planName, String repoNameInCI, String repoNameInVcs, List<String> triggeredBy)
            throws IOException, URISyntaxException;

    void mockRemoveRepositoryAccess(ProgrammingExercise exercise, Team team, User firstStudent) throws Exception;

    void mockCopyRepositoryForParticipation(ProgrammingExercise exercise, String username) throws URISyntaxException, IOException, GitLabApiException;

    void mockRepositoryWritePermissionsForTeam(Team team, User newStudent, ProgrammingExercise exercise, HttpStatus status) throws Exception;

    void mockRepositoryWritePermissionsForStudent(User student, ProgrammingExercise exercise, HttpStatus status) throws Exception;

    void mockRetrieveArtifacts(ProgrammingExerciseStudentParticipation participation) throws MalformedURLException, URISyntaxException, JsonProcessingException;

    void mockGetBuildLogs(ProgrammingExerciseStudentParticipation participation, List<BambooBuildResultDTO.BambooBuildLogEntryDTO> logs)
            throws URISyntaxException, JsonProcessingException;

    void mockGetRepositorySlugFromRepositoryUrl(String repositorySlug, VcsRepositoryUrl repositoryUrl);

    void mockGetProjectKeyFromRepositoryUrl(String projectKey, VcsRepositoryUrl repositoryUrl);

    void mockGetRepositoryPathFromRepositoryUrl(String projectPath, VcsRepositoryUrl repositoryUrl);

    void mockGetProjectKeyFromAnyUrl(String projectKey);

    void mockFetchCommitInfo(String projectKey, String repositorySlug, String hash) throws URISyntaxException, JsonProcessingException;

    void mockCopyBuildPlan(ProgrammingExerciseStudentParticipation participation) throws Exception;

    void mockConfigureBuildPlan(ProgrammingExerciseStudentParticipation participation) throws Exception;

    void mockTriggerFailedBuild(ProgrammingExerciseStudentParticipation participation) throws Exception;

    void mockNotifyPush(ProgrammingExerciseStudentParticipation participation) throws Exception;

    void mockTriggerParticipationBuild(ProgrammingExerciseStudentParticipation participation) throws Exception;

    void mockTriggerInstructorBuildAll(ProgrammingExerciseStudentParticipation participation) throws Exception;

    void resetMockProvider();

    void mockUpdateUserInUserManagement(String oldLogin, User user, String password, Set<String> oldGroups) throws Exception;

    void mockUpdateCoursePermissions(Course updatedCourse, String oldInstructorGroup, String oldEditorGroup, String oldTeachingAssistantGroup) throws Exception;

    void mockFailUpdateCoursePermissionsInCi(Course updatedCourse, String oldInstructorGroup, String oldEditorGroup, String oldTeachingAssistantGroup, boolean failToAddUsers,
            boolean failToRemoveUsers) throws Exception;

    void mockCreateUserInUserManagement(User user, boolean userExistsInCi) throws Exception;

    void mockFailToCreateUserInExernalUserManagement(User user, boolean failInVcs, boolean failInCi, boolean failToGetCiUser) throws Exception;

    void mockDeleteUserInUserManagement(User user, boolean userExistsInUserManagement, boolean failInVcs, boolean failInCi) throws Exception;

    void mockCreateGroupInUserManagement(String groupName) throws Exception;

    void mockDeleteGroupInUserManagement(String groupName) throws Exception;

    void mockAddUserToGroupInUserManagement(User user, String group, boolean failInCi) throws Exception;

    void mockRemoveUserFromGroup(User user, String group, boolean failInCi) throws Exception;

    void mockDeleteRepository(String projectKey, String repostoryName, boolean shouldFail) throws Exception;

    void mockDeleteProjectInVcs(String projectKey, boolean shouldFail) throws Exception;

    void mockDeleteBuildPlan(String projectKey, String planName, boolean shouldFail) throws Exception;

    void mockDeleteBuildPlanProject(String projectKey, boolean shouldFail) throws Exception;

    void mockGetBuildPlan(String projectKey, String planName, boolean planExistsInCi, boolean planIsActive, boolean planIsBuilding, boolean failToGetBuild) throws Exception;

    void mockHealthInCiService(boolean isRunning, HttpStatus httpStatus) throws Exception;

    void mockCheckIfProjectExistsInVcs(ProgrammingExercise exercise, boolean existsInVcs) throws Exception;

    void mockCheckIfProjectExistsInCi(ProgrammingExercise exercise, boolean existsInCi, boolean shouldFail) throws Exception;

    void mockCheckIfBuildPlanExists(String projectKey, String templateBuildPlanId, boolean buildPlanExists, boolean shouldFail) throws Exception;

    void mockRepositoryUrlIsValid(VcsRepositoryUrl vcsTemplateRepositoryUrl, String projectKey, boolean b) throws Exception;

    void mockTriggerBuild(AbstractBaseProgrammingExerciseParticipation solutionParticipation) throws Exception;

    void mockTriggerBuildFailed(AbstractBaseProgrammingExerciseParticipation solutionParticipation) throws Exception;

    void mockSetRepositoryPermissionsToReadOnly(VcsRepositoryUrl repositoryUrl, String projectKey, Set<User> users) throws Exception;

    void mockConfigureRepository(ProgrammingExercise exercise, String participantIdentifier, Set<User> students, boolean userExists) throws Exception;

    void mockDefaultBranch(ProgrammingExercise programmingExercise) throws IOException, GitLabApiException;
}

redpajama_set_name: RedPajamaGithub


MATS Bootcamp was really fun this session. I missed a couple of assignments but I was able to create some really great pieces. This month's assignment was creating an editorial illustration for an article about digital nomads. The gallery was once again filled with wonderful work. I chose four of my favorite pieces to feature. You can view the whole gallery here.
Katie Vernon - I really like how open and spacious Katie's piece is. I love her use of watercolors. I love seeing traditional media used. I wish I could paint more but in the mean time I'll enjoy the work of those that do! Please check out more work on her website.
Anna Hokerberg - Anna's piece is also very airy and it has a great story going on in her piece. I feel her work makes me think: "Where is the girl working?" "What kind of work does she do up in the mountains?" It's great when the work provokes you to create your own story. Please check out more work on her website.
Liz Alpass - I love how bright and cute Liz's piece is! All her little details are super cute and fun! Love the pineapple cocktail and the tiki head! Please check out more work on her website.
Kelly Angelovic - I love Kelly's piece! What a unique take, and her use of colors is so pretty. This would definitely be an eye catching piece if I saw it in a magazine. Please check out more work on her website.
And last but not least, here is my finished piece. I do like it but I always second guess my decisions when I see the beautiful illustrations and wonderful ideas of the other bootcampers!


Episode 3 of the first season of TC Productions presents Underground Sound. Underground Sound is a web series designed for the indie artist to help gain them exposure while giving the audience an appreciation of what they do.
Episode 3 of Underground Sound is centered around reggae artist Dad Cee. With a sound of his own this Jamaican born artist has been working the underground circuit for several years with no mercy. He has spent most of his time on the West Coast (California) networking and has now landed in Atlanta where he is already creating a buzz. His two tracks he are performing "Sweet" and "Fiyah" off of his new solo album produced by Reggie Rock.


text:
#region Usings

using System;
using System.Linq;
using System.Collections;
using System.Collections.Generic;

using org.GraphDefined.Vanaheimr.Illias.Collections;

#endregion

namespace org.GraphDefined.Vanaheimr.Styx
{

    /// <summary>
    /// Extensions methods for the IEndPipe interface.
    /// </summary>
    public static partial class IEndPipeExtensions
    {

        // Anything which maps from IEndPipe to something unlike IEndPipe...

        #region Aggregate<T>(this SourcePipe, AggreationDelegate, DefaultValue = default(T))

        /// <summary>
        /// Safely aggregates the items emitted by the given pipe. If the pipe is null
        /// or has no elements the default value will be returned.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <param name="AggreationDelegate">The delegate to aggregate the items emitted by the pipe.</param>
        /// <param name="DefaultValue">The default value to return for an empty pipe.</param>
        public static T Aggregate<T>(this IEndPipe<T> SourcePipe,
                                     Func<T, T, T>    AggreationDelegate,
                                     T                DefaultValue = default(T))
        {

            #region Initial checks

            if (SourcePipe == null)
                return DefaultValue;

            if (AggreationDelegate == null)
                throw new ArgumentNullException("AggreationDelegate");

            #endregion

            using (var Enumerator = SourcePipe.GetEnumerator())
            {

                if (!Enumerator.MoveNext())
                    return DefaultValue;

                T Aggregated = Enumerator.Current;

                while (Enumerator.MoveNext())
                    Aggregated = AggreationDelegate(Aggregated, Enumerator.Current);

                return Aggregated;

            }

        }

        #endregion

        #region Aggregate<T>(this SourcePipe, Prefix, Map, Reduce, Suffix, DefaultT = default(T))

        /// <summary>
        /// Safely aggregates the items emitted by the given pipe. If the pipe is null
        /// or has no elements the default value will be returned.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <param name="DefaultValue">The default value to return for an empty pipe.</param>
        public static T Aggregate<T>(this IEndPipe<T>  SourcePipe,
                                     T                 Prefix,
                                     Func<T, T>        Map,
                                     Func<T, T, T>     Reduce,
                                     T                 Suffix,
                                     T                 DefaultValue = default(T))
        {

            if (SourcePipe == null)
                return DefaultValue;

            try
            {
                return Reduce(Reduce(Prefix, SourcePipe.Select(Item => Map(Item)).Aggregate(Reduce)), Suffix);
            }
            catch (Exception e)
            {
                return DefaultValue;
            }

        }

        #endregion

        #region All<T>(this SourcePipe, IncludeFilter)

        /// <summary>
        /// Determines whether all items of a pipe satisfy a condition.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <param name="IncludeFilter">A delegate to test each item emitted by the pipe for a condition.</param>
        /// <returns>True if every item of the pipe passes the specified filter, or if the pipe is empty; otherwise, false.</returns>
        public static Boolean All<T>(this IEndPipe<T> SourcePipe, Func<T, Boolean> IncludeFilter)
        {

            if (SourcePipe == null)
                return true;

            foreach (var Item in SourcePipe)
                if (!IncludeFilter(Item))
                    return false;

            return true;

        }

        #endregion

        #region Any<T>(this SourcePipe)

        /// <summary>
        /// Determines whether a pipe emits any items.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <returns>True if the pipe emits any items; otherwise, false.</returns>
        public static Boolean Any<T>(this IEndPipe<T> SourcePipe)
        {

            if (SourcePipe == null)
                return false;

            using (var Enumerator = SourcePipe)
                return Enumerator.MoveNext();

        }

        #endregion

        #region Any<T>(this SourcePipe, IncludeFilter)

        /// <summary>
        /// Determines whether any item emitted by a pipe satisfies a condition.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <param name="IncludeFilter">A delegate to test each item emitted by the pipe for a condition.</param>
        /// <returns>True if the pipe emits any matching items; otherwise, false.</returns>
        public static Boolean Any<T>(this IEndPipe<T> SourcePipe, Func<T, Boolean> IncludeFilter)
        {

            if (SourcePipe == null)
                return false;

            foreach (var Item in SourcePipe)
                if (IncludeFilter(Item))
                    return true;

            return false;

        }

        #endregion

        #region Contains<T>(this SourcePipe, Value, ValueComparer = null)

        /// <summary>
        /// Determines whether a pipe emits the specified element by
        /// using the default equality comparer.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <param name="Value">The value to locate in the pipe.</param>
        /// <param name="ValueComparer">An equality comparer to compare values.</param>
        /// <returns>True if the pipe contains an item that has the specified value; otherwise, false.</returns>
        public static Boolean Contains<T>(this IEndPipe<T>      SourcePipe,
                                          T                     Value,
                                          IEqualityComparer<T>  ValueComparer = null)
        {

            if (SourcePipe == null)
                return false;

            if (ValueComparer == null)
                ValueComparer = EqualityComparer<T>.Default;

            foreach (var Item in SourcePipe)
                if (ValueComparer.Equals(Item, Value))
                    return true;

            return false;

        }

        #endregion

        #region Count<T>(this SourcePipe, IncludeFilter = null)

        /// <summary>
        /// Returns the number of items in the given pipe satisfying an optional condition.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <param name="IncludeFilter">A delegate to test each item emitted by the pipe for a condition.</param>
        public static UInt64 Count<T>(this IEndPipe<T>  SourcePipe,
                                      Func<T, Boolean>  IncludeFilter = null)
        {

            if (SourcePipe == null)
                return 0UL;

            var Counter = 0UL;

            if (IncludeFilter == null)
                foreach (var Item in SourcePipe)
                    Counter++;

            else
                foreach (var Item in SourcePipe)
                    if (IncludeFilter(Item))
                        Counter++;

            return Counter;

        }

        #endregion

        #region FirstOrDefault<T>(this SourcePipe, IncludeFilter = null, DefaultValue = default(T))

        /// <summary>
        /// Returns the first item of the given pipe that satisfies a condition
        /// or the given default value if no such item was found.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <param name="IncludeFilter">A delegate to test each item emitted by the pipe for a condition.</param>
        /// <param name="DefaultValue">A default value.</param>
        public static T FirstOrDefault<T>(this IEndPipe<T>  SourcePipe,
                                          Func<T, Boolean>  IncludeFilter  = null,
                                          T                 DefaultValue   = default(T))
        {

            if (SourcePipe == null)
                return DefaultValue;

            if (IncludeFilter == null)
                foreach (var Item in SourcePipe)
                    return Item;

            foreach (var Item in SourcePipe)
                if (IncludeFilter(Item))
                    return Item;

            return DefaultValue;

        }

        #endregion

        #region LastOrDefault<T>(this SourcePipe, IncludeFilter = null, DefaultValue = default(T))

        /// <summary>
        /// Returns the last item of the given pipe that satisfies a condition
        /// or the given default value if no such item was found.
        /// </summary>
        /// <typeparam name="T">The type of the items emitted by the pipe.</typeparam>
        /// <param name="SourcePipe">A pipe.</param>
        /// <param name="IncludeFilter">A delegate to test each item emitted by the pipe for a condition.</param>
        /// <param name="DefaultValue">A default value.</param>
        public static T LastOrDefault<T>(this IEndPipe<T>  SourcePipe,
                                         Func<T, Boolean>  IncludeFilter  = null,
                                         T                 DefaultValue   = default(T))
        {

            if (SourcePipe == null)
                return DefaultValue;

            T Value = DefaultValue;

            foreach (var Item in SourcePipe)
                if (IncludeFilter(Item))
                    Value = Item;

            return Value;

        }

        #endregion

        #region SequenceEqual

        public static Boolean SequenceEqual<T>(this IEndPipe<T>      first,
                                               IEndPipe<T>           second,
                                               IEqualityComparer<T>  comparer = null)
        {

            if (comparer == null)
                comparer = EqualityComparer<T>.Default;

            using (IEnumerator<T> first_enumerator = first.GetEnumerator(),
                    second_enumerator = second.GetEnumerator())
            {

                while (first_enumerator.MoveNext())
                {
                    if (!second_enumerator.MoveNext())
                        return false;

                    if (!comparer.Equals(first_enumerator.Current, second_enumerator.Current))
                        return false;
                }

                return !second_enumerator.MoveNext();

            }

        }

        #endregion

        #region ToArray(this SourcePipe, ResetPipeBefore = false, ResetPipeAfter = false)

        /// <summary>
        /// Copies the elements of the given pipe into a new array.
        /// </summary>
        /// <typeparam name="T">The type of the emitting objects.</typeparam>
        /// <param name="SourcePipe">A pipe as element source.</param>
        /// <param name="ResetPipe">Reset the pipe after operation.</param>
        public static T[] ToArray<T>(this IEndPipe<T>  SourcePipe,
                                     Boolean           ResetPipeBefore  = false,
                                     Boolean           ResetPipeAfter   = false)
        {

            new List<String>().ToArray();
            var Values = new T[8];
            var Size   = 0;

            if (ResetPipeBefore)
                SourcePipe.Reset();

            foreach (var Item in SourcePipe)
            {

                if (Size == Values.Length)
                    Array.Resize(ref Values, Size * 2);

                Values[Size++] = Item;

            }

            if (Size != Values.Length)
                Array.Resize(ref Values, Size);

            if (ResetPipeAfter)
                SourcePipe.Reset();

            return Values;

        }

        #endregion

        #region ToDictionary(this SourcePipe, KeySelector, ValueSelector, Comparer = null, ResetPipeBefore = false, ResetPipeAfter = false)

        public static Dictionary<TKey, TValue> ToDictionary<T, TKey, TValue>(this IEndPipe<T>         SourcePipe,
                                                                             Func<T, TKey>            KeySelector,
                                                                             Func<T, TValue>          ValueSelector,
                                                                             IEqualityComparer<TKey>  Comparer         = null,
                                                                             Boolean                  ResetPipeBefore  = false,
                                                                             Boolean                  ResetPipeAfter   = false)
        {

            if (Comparer == null)
                Comparer = EqualityComparer<TKey>.Default;

            var Dictionary = new Dictionary<TKey, TValue>(Comparer);

            if (ResetPipeBefore)
                SourcePipe.Reset();

            foreach (var Item in SourcePipe)
                Dictionary.Add(KeySelector  (Item),
                               ValueSelector(Item));

            if (ResetPipeAfter)
                SourcePipe.Reset();

            return Dictionary;

        }

        #endregion

        #region ToList(this SourcePipe, ResetPipeBefore = false, ResetPipeAfter = false)

        public static List<T> ToList<T>(this IEndPipe<T>  SourcePipe,
                                        Boolean           ResetPipeBefore  = false,
                                        Boolean           ResetPipeAfter   = false)
        {

            var List = new List<T>();

            if (ResetPipeBefore)
                SourcePipe.Reset();

            foreach (var Item in SourcePipe)
                List.Add(Item);

            if (ResetPipeAfter)
                SourcePipe.Reset();

            return List;

        }

        #endregion

    }

}


text:
Looking Back for a Way Forward: Jeff Scott's Passion for Bach and Coltrane
By Tysen Dauer ,
Chamber Music Silicon Valley
If you went looking for Jeff Scott's 2014 Passion for Bach and Coltrane in a record store you might find it resting accurately but uncomfortably in the Third Stream section, the theoretical halfway point between Western classical music and jazz. Scott's piece does offer up excerpts and techniques from these two genres, but it is so much more. It also weaves in A. B. Spellman's mesmerizing poetry, connects with John Coltrane's spiritual journey, and fuses theater and film music styles with poetic descriptions to create a fascinating, visual experience.
Saturday's pleasant performance by Chamber Music Silicon Valley at Santa Clara University was the West Coast premiere of the work, given in a small black-box theater with small, circular tables set up near the performers and four rows of tiered seating behind this jazz club arrangement. The prevailing mood was hipness, with performers dressed in a variety of business casual.
Scott's ear-opening composition, the only piece on the program, is made up of eight movements, two named after selections from works by J. S. Bach, three referring to tracks from Coltrane's album A Love Supreme, and three with titles from Spellman's 2008 poetry collection, Things I Must Have Known. Each movement started off firmly planted in either a jazz or classical idiom and eventually incorporated elements of the other, often with orator Malinda Haslett speaking Spellman's poetry.
Scott uses a wind quintet, string quartet, piano, and double bass without cornering instruments into expected, traditional roles: The bassoon gets a jazz solo and the drummer accompanies Bach's tunes on the piano.
Chamber Music Silicon Valley stepped up to the job. Bursts of quasi-improvisatory virtuosity intermittently drew attention to Douglas Brown's bassoon playing and to flutist and Artistic Director Ray Furuta. Pianist Miles Massicotte kept on top of the many style transitions between classical and jazz, and Haslett was nearly flawless in her delivery. Rare moments of questionable instrument intonation or gaps in ensemble synchronicity were the only performance blemishes.
The fourth and longest movement, "Out of Nazareth," is the heart of the piece. While the scriptural title might suggest a devout mood, Spellman's language is religious yet unorthodox, at one point portraying Christ's supposed crucifiers, "dar[ing] him to miracle his broke ass out of this one." Here, and throughout Scott's work, Spellman's poetry is the engine driving the music forward. Scott's masterful text selection and placement is paired with dramatic musical techniques from musical theater and film, creating a sort of ear film where visuals are induced by the spoken word and poetry rather than provided by a screen or actors.
Scott's musical and literary references are beautifully and meaningfully interwoven throughout. His Passion not only references Bach's canonical works and the story of Jesus of Nazareth, it delves into every human's final days. The references to Coltrane's legacy also transcend their status as homage to a masterful jazz musician. The album Scott draws on came after the iconic saxophonist's "spiritual awakening" and Scott places Coltrane's pieces in reverse order, starting with "Psalm," then "Resolution," and finally drawing on "Acknowledgement" as the conclusion of the Passion. This sets the composition's trajectory toward beginnings, with Coltrane's powerful declamation of the text "a love supreme" in his opening track coming at the conclusion of Scott's work and aligning with Spellman's musing over the great question of life, its basis in love, and a description of the pure love given to newborns.
Scott's riveting and hopeful work looks back in time into the histories of Western art music, jazz, poetry, and religious figures, even reading Coltrane's album from end to beginning. But the work is powerfully forward looking: it draws on these past events with an eye on what is still to come, with a heart-full path for how to be in our new world.
Tysen Dauer studies musicology at Stanford University. His current research focuses on the reception history of early American minimalism.
Coltrane's Love Crosses Boundaries


There are always two sides to a story. Anyone who has ever tried to mediate a disagreement between two children, especially if they are siblings, knows that there are two sides to every story. Typically, as the two sides compete, there is a sliver of truth that emerges in the middle that becomes the real narrative.
Many times in life there are two sides of the story. Blessings can also bring tragedies. Pain, after time and healing, can shape and lead individuals into great moments and futures. That doesn't mean that the blessing is in reality pain, or that the pain one is experiencing should be disregarded because it will lead to blessing. It's just a reminder that there are always two sides of the story.
Psalms 105 and 106 are two sides of the same story. They are Psalms that are often quoted together because they begin and end with words of thanksgiving.
They are reminders of where our focus should remain. They are reminders of all that God has done for us. They are encouragements to lead lives of thanksgiving. Yet the remainder of the Psalms seem so different.
Psalm 105 is a reminder of God's goodness in being faithful to the promises, and bringing Israel safely into the land. It's focus is on what God has done. God is holy, and has remembered the covenant to Abraham. When the nation was small in number God kept them safe. When there was a famine in the land, God sent Joseph ahead to prepare a safe place to live in Egypt. When Israel was in slavery, God sent Moses and Aaron to lead them to freedom through the plagues and the crossing of the Sea. When the Egyptians pursued them, God protected them with the cloud and saved them, eventually placing them in the promised land. The Lord is Good!
While Psalm 105 is a reminder of God's faithfulness to the promise, Psalm 106 is a reminder that Israel has failed. Psalm 105 tells of all the good things God has done, while Psalm 106 declares Israel's sinfulness, sharing reminders of their, and our, mistakes. Both we and our fathers have sinned and acted wickedly. We rebelled against God's love. We saw God's good works, and yet ignored them to follow our own passions. We searched after, and created our own gods. We participated in the rebellion of Dathan and Abiram. We made a calf in the wilderness, and bowed down. We complained about the food and the water. We worshiped the Baal of Peor. We mixed with the nations, doing the very thing God asked us not to do. The anger of the Lord was kindled against us, and we deserved it. Nevertheless, God looked upon us, heard our cry, and saved us.
Psalms 105 and 106 are two sides of the same story. Give thanks to God because God has been faithful. Give thanks to God because even when we were unfaithful, God was still faithful.
Honestly, I would rather read Psalm 105 than 106. Psalm 105 is exciting as I can declare with others, look at all the great things God has done. God has been faithful in the past. God will be faithful in the future.
Psalm 106 is discouraging because it reminds me of my own mistakes. I have sinned right along with my fathers. I may not have built a calf to worship, but I've held up my own idols, and worshiped them believing they could bring me life. I may not have grumbled because I didn't have meat to eat, but I've grumbled about how others sometimes have more than I do, forgetting that all that I have comes from God. I may not have worshiped the Baal of Peor, prostituting myself to a foreign God, but I have been unfaithful time and time again, and I probably deserve death.
I don't like reading Psalm 106 because it reminds me of my mistakes. Psalm 105 is a fun story, an exciting book to read. Psalm 106 is depressing, being reminded of sin after sin. Yet even in my mistakes, when I deserve punishment, I'm reminded that God does not leave me. Instead, God's steadfast love is always faithful.
Thus, no matter where I am today, I can praise the Lord at all times. I praise the Lord, because the Lord has been faithful to the promises and conquered the enemies. But even more so, because the Lord has taken me, one who deserves nothing but death, and has given me life.


text:
namespace MassTransit.ActiveMqTransport.Topology
{
    using System.Collections.Generic;
    using System.Linq;

    public class QueueEntity :
        Queue,
        QueueHandle
    {
        public QueueEntity(long id, string name, bool autoDelete, bool lazy = false)
        {
            Id = id;
            EntityName = name;
            AutoDelete = autoDelete;
            Lazy = lazy;
        }

        public static IEqualityComparer<QueueEntity> NameComparer { get; } = new NameEqualityComparer();

        public static IEqualityComparer<QueueEntity> QueueComparer { get; } = new QueueEntityEqualityComparer();
        public bool Lazy { get; }

        public string EntityName { get; }
        public bool AutoDelete { get; }
        public long Id { get; }
        public Queue Queue => this;

        public override string ToString()
        {
            return string.Join(", ",
                new[] { $"name: {EntityName}", AutoDelete ? "auto-delete" : "" }.Where(x => !string.IsNullOrWhiteSpace(x)));
        }

        sealed class QueueEntityEqualityComparer : IEqualityComparer<QueueEntity>
        {
            public bool Equals(QueueEntity x, QueueEntity y)
            {
                if (ReferenceEquals(x, y))
                    return true;
                if (ReferenceEquals(x, null))
                    return false;
                if (ReferenceEquals(y, null))
                    return false;
                if (x.GetType() != y.GetType())
                    return false;
                return string.Equals(x.EntityName, y.EntityName) && x.AutoDelete == y.AutoDelete;
            }

            public int GetHashCode(QueueEntity obj)
            {
                unchecked
                {
                    var hashCode = obj.EntityName.GetHashCode();
                    hashCode = (hashCode * 397) ^ obj.AutoDelete.GetHashCode();
                    return hashCode;
                }
            }
        }

        sealed class NameEqualityComparer : IEqualityComparer<QueueEntity>
        {
            public bool Equals(QueueEntity x, QueueEntity y)
            {
                if (ReferenceEquals(x, y))
                    return true;
                if (ReferenceEquals(x, null))
                    return false;
                if (ReferenceEquals(y, null))
                    return false;
                if (x.GetType() != y.GetType())
                    return false;
                return string.Equals(x.EntityName, y.EntityName);
            }

            public int GetHashCode(QueueEntity obj)
            {
                return obj.EntityName.GetHashCode();
            }
        }
    }
}