Synopsys® free and open-source licensing notices for:
Synopsys embARC Open Software Platform
CONTENTS
Contents
Creative Commons CC0 1.0 Universal
This document includes licensing information relating to free and open-source software (“FOSS”) included in source and binary distributions of the embARC Open Software Platform for Synopsys ARC® Processors (the “Software”). The terms of the applicable FOSS license(s) govern Synopsys’s® distribution and your use of the Software. Synopsys® and the other authors, licensors, and distributors of the FOSS have disclaimed all warranties relating to any liability arising from all use and distribution of the FOSS.
Synopsys® has reproduced below copyright and other licensing notices appearing within the FOSS packages. While Synopsys® seeks to provide complete and accurate copyright and licensing information for each FOSS package, Synopsys® does not represent or warrant that the licensing information provided is complete, correct, or error-free. Recipients of the Software are encouraged to (a) investigate the identified FOSS packages to confirm the accuracy of the licensing information provided herein and (b) notify Synopsys® of any inaccurate information or errors found in this document.
Certain FOSS Licenses, such as the GNU General Public License, GNU Lesser (or Library) General Public License, and Eclipse Public License, require that Synopsys® make the source code corresponding to those distributed FOSS binaries available under the terms of the same FOSS License. Recipients who would like to receive a copy of such corresponding source code should submit a request to Synopsys® by post at:
Synopsys
Attn: Open Source Requests
690 East Middlefield Road
Mountain View, CA 94043
Please provide the following information in all submitted FOSS requests:
· the FOSS packages for which you are requesting source code;
· the Synopsys® product (and any available version information) with which the requested FOSS packages are distributed;
· an email address at which Synopsys® may contact you regarding the request (if available); and
· the postal address for delivery of the requested source code.
|
Document Key |
||
|
Formatting |
Description |
Examples: |
|
filename: |
The name of the file in the FOSS source code repository that contains the text or excerpts that follow. |
COPYING; LICENSE, readme
|
|
[SPDX license identified] |
Placeholder for standard license text which has been reproduced in the appendix of this document |
[GPL-2.0], [LGPL-2.1], [EPL-1.0] |
Project homepage: http://www.embarc.org/
Project licensing:
Copyright (c) 2017, Synopsys, Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3) Neither the name of the Synopsys, Inc., nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

Project homepage: https://github.com/aws/aws-iot-device-sdk-embedded-C
Project licensing: https://github.com/aws/aws-iot-device-sdk-embedded-C/blob/master/LICENSE.txt
LICENSE:
[Apache License]
Project homepage: http://www.doxygen.org/
Project licensing: https://github.com/doxygen/doxygen/blob/master/LICENSE
LICENSE:
[GPL-2.0]
Project homepage: http://g.oswego.edu/dl/html/malloc.html
Project licensing: http://creativecommons.org/publicdomain/zero/1.0/
LICENSE:
[Creative Commons Zero v1.0 Universal]
Project homepage: http://elm-chan.org/fsw/ff/00index_e.html
Project licensing: http://elm-chan.org/fsw/ff/en/appnote.html#license
00readme:
AGREEMENTS
FatFs module is an open source software to implement FAT file system to small embedded systems. This is a free software and is opened for education, research and commercial developments under license policy of following trems.
Copyright (C) 2014, ChaN, all right reserved.
* The FatFs module is a free software and there is NO WARRANTY.
* No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial product UNDER YOUR RESPONSIBILITY.
* Redistributions of source code must retain the above copyright notice.
Project homepage: http://www.freertos.org/
Project licensing: http://www.freertos.org/a00114.html
The FreeRTOS.org source code is licensed by the modified GNU General Public License (GPL) text provided below. The FreeRTOS download also includes demo application source code, some of which is provided by third parties AND IS LICENSED SEPARATELY FROM FREERTOS.ORG.
For the avoidance of any doubt refer to the comment included at the top of each source and header file for license and copyright information.
This is a list of files for which Real Time Engineers Ltd are not the copyright owner and are NOT COVERED BY THE GPL.
1) Various header files provided by silicon manufacturers and tool vendors that define processor specific memory addresses and utility macros. Permission has been granted by the various copyright holders for these files to be included in the FreeRTOS download. Users must ensure license conditions are adhered to for any use other than compilation of the FreeRTOS demo applications.
2) The uIP TCP/IP stack the copyright of which is held by Adam Dunkels. Users must ensure the open source license conditions stated at the top of each uIP source file is understood and adhered to.
3) The lwIP TCP/IP stack the copyright of which is held by the Swedish Institute of Computer Science. Users must ensure the open source license conditions stated at the top of each lwIP source file is understood and adhered to.
4) Various peripheral driver source files and binaries provided by silicon manufacturers and tool vendors. Permission has been granted by the various copyright holders for these files to be included in the FreeRTOS download. Users must ensure license conditions are adhered to for any use other than compilation of the FreeRTOS demo applications.
5) The files contained within FreeRTOS\Demo\WizNET_DEMO_TERN_186\tern_code, which are slightly modified versions of code provided by and copyright to Tern Inc.
Errors and omissions should be reported to Richard Barry, contact details for whom can be obtained from http://www.FreeRTOS.org.
The GPL license text follows.
A special exception to the GPL is included to allow you to distribute a combined work that includes FreeRTOS without being obliged to provide the source code for any proprietary components. See the licensing section of http://www.FreeRTOS.org for full details. The exception text is also included at the bottom of this file.
[GPL-2.0]
The FreeRTOS GPL Exception Text:
Any FreeRTOS source code, whether modified or in it’s original release form, or whether in whole or in part, can only be distributed by you under the terms of the GNU General Public License plus this exception. An independent module is a module which is not derived from or based on FreeRTOS.
Clause 1:
Linking FreeRTOS statically or dynamically with other modules is making a combined work based on FreeRTOS. Thus, the terms and conditions of the GNU General Public License cover the whole combination.
As a special exception, the copyright holder of FreeRTOS gives you permission to link FreeRTOS with independent modules that communicate with FreeRTOS solely through the FreeRTOS API interface, regardless of the license terms of these independent modules, and to copy and distribute the resulting combined work under terms of your choice, provided that
+ Every copy of the combined work is accompanied by a written statement that details to the recipient the version of FreeRTOS used and an offer by yourself to provide the FreeRTOS source code (including any modifications you may have made) should the recipient request it.
+ The combined work is not itself an RTOS, scheduler, kernel or related product.
+ The independent modules add significant and primary functionality that is unrelated to multitasking, intertask communication or intertask signalling - and therefore do not merely extend the functionality already present in FreeRTOS.
Clause 2:
FreeRTOS may not be used for any competitive or comparative purpose, including the publication of any form of run time or compile time metric, without the express permission of Real Time Engineers Ltd. (this is the norm within the industry and is intended to ensure information accuracy).
Project homepage: http://gmsl.sourceforge.net/
Project licensing: BSD License
Copyright (c) 2005-2014 John Graham-Cumming
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the John Graham-Cumming nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

Project homepage: https://github.com/nodejs/http-parser
Project licensing: https://github.com/nodejs/http-parser/blob/master/LICENSE-MIT
Project homepage: https://github.com/arkku/ihex
Project licensing: https://github.com/arkku/ihex/blob/master/LICENSE
Project homepage: http://libcoap.sourceforge.net/
Project licensing: https://github.com/obgm/libcoap#license-information
LICENSE:
libcoap is published as open-source software without any warranty of any kind. Use is permitted under the terms of the GNU General Public License (GPL), Version 2 or higher, OR the revised BSD license.
[GPL-2.0] – See Appendix A for full license text.
[BSD 2-Clause License]
Copyright (c) 2010--2011, Olaf Bergmann
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Project homepage: http://savannah.nongnu.org/projects/lwip/
Project licensing: http://lwip.wikia.com/wiki/License
lwIP is licenced under the BSD licence:
Copyright (c) 2001-2004 Swedish Institute of Computer Science. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.
 IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
Project homepage: https://tls.mbed.org/
https://github.com/armmbed/mbedtls
Project licensing: Apache 2.0
Project homepage: https://www.eclipse.org/paho/
Source code header:
Copyright (c) 2009, 2013 IBM Corp.
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 and Eclipse Distribution License v1.0 which accompany this distribution.
The Eclipse Public License is available at http://www.eclipse.org/legal/epl-v10.html and the Eclipse Distribution License is available at http://www.eclipse.org/org/documents/edl-v10.php.
epl-v10:
[EPL-1.0]
Project homepage:
http://store.digilentinc.com/pmodwifi-wifi-interface-802-11g/
Project licensing:
From source code headers (e.g., MRF24GAdaptor.c):
************************************************************************
Author: Keith Vogel
Copyright 2013, Digilent Inc.
************************************************************************
Copyright (c) 2013-2014, Digilent <www.digilentinc.com>
Contact Digilent for the latest version.
This program is free software; distributed under the terms of BSD 3-clause license ("Revised BSD License", "New BSD License", or "Modified BSD License")
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name(s) of the above-listed copyright holder(s) nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

Project homepage: http://cubeatsystems.com/ntshell/
Project licensing: http://cubeatsystems.com/ntshell/license.html
The license
• vtparse, vtparse_table are in the public domain.
• ntshell, ntopt, ntlibc, text_editor, text_history are in the MIT license.
• (or You can select TOPPERS license.)
===============================================================
The MIT license for Natural Tiny Shell (NT-Shell)
===============================================================
Copyright (c) 2010-2011 Shinichiro Nakamura
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
===============================================================
So you can use this software in non-commercial or commercial products. But there aren't any warranty.
Please do NOT remove copyright texts, if you redistribute this package.
Project homepage: https://github.com/openthread/openthread
Project licensing: https://github.com/openthread/openthread/blob/master/LICENSE
Project homepage: https://github.com/kgabis/parson
Project licensing: http://opensource.org/licenses/mit-license.php
Project homepage: https://github.com/olikraus/u8glib
Project licensing: https://github.com/olikraus/u8glib/blob/master/license.txt
Project homepage: https://projects.eclipse.org/projects/technology.wakaama
https://github.com/eclipse/wakaama
Project licensing: Eclipse Public License – v 1.0
[EPL-1.0]
Project homepage: http://elm-chan.org/fsw/strf/xprintf.html
Project licensing:
xprintf:
Universal string handler for user console interface
Copyright (C) 2011, ChaN, all right reserved.
This software is a free software and there is NO WARRANTY.
* No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial products UNDER YOUR RESPONSIBILITY.
* Redistributions of source code must retain the above copyright notice.
Project homepage: https://github.com/fredrikhederstierna/fymodem
Project licensing:
Free YModem implementation.
Fredrik Hederstierna 2014
This file is in the public domain.
You can do whatever you want with it.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Project homepage: https://github.com/kubo/ya_getopt
Project licensing: [2-clause BSD-style license]
Eclipse Public License - v 1.0
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
1. DEFINITIONS
"Contribution" means:
a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and
b) in the case of each subsequent Contributor:
i) changes to the Program, and
ii) additions to the Program;
where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.
"Contributor" means any person or entity that distributes the Program.
"Licensed Patents" mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.
"Program" means the Contributions distributed in accordance with this Agreement.
"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.
2. GRANT OF RIGHTS
a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.
b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.
c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.
d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.
3. REQUIREMENTS
A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
b) its license agreement:
i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;
ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;
iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and
iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.
When the Program is made available in source code form:
a) it must be made available under this Agreement; and
b) a copy of this Agreement must be included with each copy of the Program.
Contributors may not remove or alter any copyright notices contained within the Program.
Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.
4. COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.
For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.
5.  Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement , including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
6.
7. GENERAL
If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.
All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.
Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.
This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License.
Apache License
Version 2.0, January 2004
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
1. You must give any other recipients of the Work or Derivative Works a copy of this License; and
2. You must cause any modified files to carry prominent notices stating that You changed the files; and
3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
 DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED HEREUNDER.
Statement of Purpose
The laws of most jurisdictions throughout the world automatically confer exclusive Copyright and Related Rights (defined below) upon the creator and subsequent owner(s) (each and all, an "owner") of an original work of authorship and/or a database (each, a "Work").
Certain owners wish to permanently relinquish those rights to a Work for the purpose of contributing to a commons of creative, cultural and scientific works ("Commons") that the public can reliably and without fear of later claims of infringement build upon, modify, incorporate in other works, reuse and redistribute as freely as possible in any form whatsoever and for any purposes, including without limitation commercial purposes. These owners may contribute to the Commons to promote the ideal of a free culture and the further production of creative, cultural and scientific works, or to gain reputation or greater distribution for their Work in part through the use and efforts of others.
For these and/or other purposes and motivations, and without any expectation of additional consideration or compensation, the person associating CC0 with a Work (the "Affirmer"), to the extent that he or she is an owner of Copyright and Related Rights in the Work, voluntarily elects to apply CC0 to the Work and publicly distribute the Work under its terms, with knowledge of his or her Copyright and Related Rights in the Work and the meaning and intended legal effect of CC0 on those rights.
1. Copyright and Related Rights. A Work made available under CC0 may be protected by copyright and related or neighboring rights ("Copyright and Related Rights"). Copyright and Related Rights include, but are not limited to, the following:
i. the right to reproduce, adapt, distribute, perform, display, communicate, and translate a Work;
ii. moral rights retained by the original author(s) and/or performer(s);
iii. publicity and privacy rights pertaining to a person's image or likeness depicted in a Work;
iv. rights protecting against unfair competition in regards to a Work, subject to the limitations in paragraph 4(a), below;
v. rights protecting the extraction, dissemination, use and reuse of data in a Work;
vi. database rights (such as those arising under Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, and under any national implementation thereof, including any amended or successor version of such directive); and
vii. other similar, equivalent or corresponding rights throughout the world based on applicable law or treaty, and any national implementations thereof.
2. Waiver. To the greatest extent permitted by, but not in contravention of, applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and unconditionally waives, abandons, and surrenders all of Affirmer's Copyright and Related Rights and associated claims and causes of action, whether now known or unknown (including existing as well as future claims and causes of action), in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each member of the public at large and to the detriment of Affirmer's heirs and successors, fully intending that such Waiver shall not be subject to revocation, rescission, cancellation, termination, or any other legal or equitable action to disrupt the quiet enjoyment of the Work by the public as contemplated by Affirmer's express Statement of Purpose.
3. Public License Fallback. Should any part of the Waiver for any reason be judged legally invalid or ineffective under applicable law, then the Waiver shall be preserved to the maximum extent permitted taking into account Affirmer's express Statement of Purpose. In addition, to the extent the Waiver is so judged Affirmer hereby grants to each affected person a royalty-free, non transferable, non sublicensable, non exclusive, irrevocable and unconditional license to exercise Affirmer's Copyright and Related Rights in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "License"). The License shall be deemed effective as of the date CC0 was applied by Affirmer to the Work. Should any part of the License for any reason be judged legally invalid or ineffective under applicable law, such partial invalidity or ineffectiveness shall not invalidate the remainder of the License, and in such case Affirmer hereby affirms that he or she will not (i) exercise any of his or her remaining Copyright and Related Rights in the Work or (ii) assert any associated claims and causes of action with respect to the Work, in either case contrary to Affirmer's express Statement of Purpose.
4. Limitations and Disclaimers.
a. No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.
b. Affirmer offers the Work as-is and makes no representations or warranties of any kind concerning the Work, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non infringement, or the absence of latent or other defects, accuracy, or the present or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law.
c. Affirmer disclaims responsibility for clearing rights of other persons that may apply to the Work or any use thereof, including without limitation any person's Copyright and Related Rights in the Work. Further, Affirmer disclaims responsibility for obtaining any necessary consents, permissions or other rights required for any use of the Work.
d. Affirmer understands and acknowledges that Creative Commons is not a party to this document and has no duty or obligation with respect to this CC0 or use of the Work.


Superstar Rajinikanth has joined the chorus against Home Minister Amit Shah's recent push for Hindi as a unifying language for the country. After Kamal Haasan, now Rajinikanth has said that Tamil Nadu and other southern Indian states would never accept Hindi imposition.Speaking to reporters outside Chennai airport, Rajinikanth said, "Hindi language should not be imposed. Not just Tamil Nadu, none of the southern states will accept Hindi imposition." He added, "Not just Hindi, no language should be imposed on the country." Speaking to the media on Wednesday, Rajinikanth said, "If there is a common language it is good for the unity and progress of the country. Unfortunately it can't be implemented in our country. However, forcing a language is not acceptable. Southern states will not accept Hindi imposition. Even some northern states will not accept Hindi Imposition".


This project is more numerically directed, with tests of algorithms for solving partial differential equations using finite difference schemes. Chapter 10 of the lecture notes provides the necessary theoretical background.
For this project you can collaborate with fellow students and you can hand in a common report. This project (together with projects 3 and 4) counts 1/3 of the final mark.
The project has a strong mathematical axis. However, for those interested, it should be straightforward to replace the dimensionless analysis in parts 5a-5f) with specific boundary and initial conditions. This is done in part 5g), with a focus on the heat equation and geophysical processes. That part is optional, but gives an additional 30 points to a score of 100.
The physical problem can be that of the temperature gradient in a rod of length \( L=1 \) or that of channel flow between two flat and infinite plates at \( x=0 \) and \( x=1 \), where the fluid is initially at rest and the plate \( x=1 \) is given a sudden initial movement. We are looking at a one-dimensional problem $$ \begin{equation*} \frac{\partial^2 u(x,t)}{\partial x^2} =\frac{\partial u(x,t)}{\partial t}, t> 0, x\in [0,L] \end{equation*} $$ or $$ \begin{equation*} u_{xx} = u_t, \end{equation*} $$ with initial conditions, i.e., the conditions at \( t=0 \), $$ \begin{equation*} u(x,0)= 0 \hspace{0.5cm} 0 < x < L \end{equation*} $$ with \( L=1 \) the length of the \( x \)-region of interest. The boundary conditions are $$ \begin{equation*} u(0,t)= 0 \hspace{0.5cm} t \ge 0, \end{equation*} $$ and $$ \begin{equation*} u(L,t)= 1 \hspace{0.5cm} t \ge 0. \end{equation*} $$ The function \( u(x,t) \) can be the temperature gradient of a rod or represent the fluid velocity in a direction parallel to the plates, that is normal to the \( x \)-axis. In the latter case, for small \( t \), only the part of the fluid close to the moving plate is set in significant motion, resulting in a thin boundary layer at \( x=1 \). As time increases, the velocity approaches a linear variation with \( x \). In this case, which can be derived from the incompressible Navier-Stokes, the above equations constitute a model for studying friction between moving surfaces separated by a thin fluid film.
In this project we want to study the numerical stability of three methods for partial differential equations (PDEs). These methods we will discuss are the explicit forward Euler algorithm with discretized versions of time given by a forward formula and a centered difference in space resulting in $$ \begin{equation*} u_t\approx \frac{u(x,t+\Delta t)-u(x,t)}{\Delta t}=\frac{u(x_i,t_j+\Delta t)-u(x_i,t_j)}{\Delta t} \end{equation*} $$ and $$ \begin{equation*} u_{xx}\approx \frac{u(x+\Delta x,t)-2u(x,t)+u(x-\Delta x,t)}{\Delta x^2}, \end{equation*} $$ or $$ \begin{equation*} u_{xx}\approx \frac{u(x_i+\Delta x,t_j)-2u(x_i,t_j)+u(x_i-\Delta x,t_j)}{\Delta x^2}. \end{equation*} $$ We will also discuss the implicit Backward Euler with $$ \begin{equation*} u_t\approx \frac{u(x,t)-u(x,t-\Delta t)}{\Delta t}=\frac{u(x_i,t_j)-u(x_i,t_j-\Delta t)}{\Delta t} \end{equation*} $$ and $$ \begin{equation*} u_{xx}\approx \frac{u(x+\Delta x,t)-2u(x,t)+u(x-\Delta x,t)}{\Delta x^2}, \end{equation*} $$ or $$ \begin{equation*} u_{xx}\approx \frac{u(x_i+\Delta x,t_j)-2u(x_i,t_j)+u(x_i-\Delta x,t_j)}{\Delta x^2}, \end{equation*} $$
Finally we use the implicit Crank-Nicolson scheme with a time-centered scheme at \( (x,t+\Delta t/2) \) $$ \begin{equation*} u_t\approx \frac{u(x,t+\Delta t)-u(x,t)}{\Delta t}=\frac{u(x_i,t_j+\Delta t)-u(x_i,t_j)}{\Delta t}. \end{equation*} $$ The corresponding spatial second-order derivative reads $$ \begin{align*} u_{xx}\approx &\frac{1}{2}\left(\frac{u(x_i+\Delta x,t_j)-2u(x_i,t_j)+u(x_i-\Delta x,t_j)}{\Delta x^2}\right. +\\ &\left. \frac{u(x_i+\Delta x,t_j+\Delta t)-2u(x_i,t_j+\Delta t)+u(x_i-\Delta x,t_j+\Delta t)}{\Delta x^2}\right). \end{align*} $$ Note well that we are using a time-centered scheme wih \( t+\Delta t/2 \) as center.
Here you can choose between an explicit or an implicit scheme. For the implicit scheme discussed in chapter 10 of the lecture notes, you need to use for example an iterative method like Jacobi's.
Outline the algorithm for solving the two-dimensional diffusion equation and implement the explicit or the implicit scheme as function of \( \Delta x \) (assuming \( \Delta x = \Delta y \)) and \( \Delta t \). Solve the equations numerically and give a critical discussion of your results. Compare your results with the closed-form answer. Discuss the stability of the solution as function of different values of \( \Delta x \) and \( \Delta t \).
You should, if you have time, try to parallelize the equations using MPI or OpenMP.
The Scientific background is based on geological evidence at the surface. Geologists have proposed that there was an active subduction zone on the western coast of Norway about 1Gy ago. When subducting, the oceanic lithosphere releases water and other chemical components that go mostly to the surface but may also be trapped in the mantle above the subducting slab. This process is called the refertilization of the mantle wedge (see Figure). These chemical components contain more radioactive elements than the normal mantle. We can therefore expect that ancient mantle wedges are enriched in radioactive elements and therefore warmer than normal mantle. The question is how much warmer they are and if we can find evidence for this enrichment in geophysical studies.
The purpose of this part is to calculate the thermal evolution of the lithosphere up to present following the emplacement of radioactive elements in the mantle wedge 1 Gy ago.
The equation to compute is the time evolution of the temperature distribution is the heat equation, which will be used only in 2D here, namely $$ \begin{equation} \vec \nabla(k \vec \nabla T) + Q = \rho c_p \frac{\partial T}{\partial t} \label{eq:heat2D} \end{equation} $$ where \( T \) is the temperature, \( \rho \) is the density, \( k \) is the thermal conductivity, \( c_p \) is the specific heat capacity and \( Q \) is the heat production.
With the boundary conditions and initial conditions, you should rescale your equations in order to use the results from parts 5a-5f). The paramaters of the model are described here.
The boundary conditions are \( 8^{\circ}\,C \) at the surface and \( 1300^{\circ}C \) at the bottom at a depth of 120 km.
In this study, we assume a constant density for the lithosphere of \( 3.5 10^3\,Kg/m^3 \), a constant thermal conductivity of \( 2.5\,W/m/^{\circ}C \) and a constant specific heat capacity of \( 1000\,J/Kg/^{\circ}C^{-1} \).
The heat production, caused by radioactive decay, cannot be taken as uniform in the whole lithosphere as radioactive elements are much more abundant in the crust than in the mantle. We need therefore to separate the lithosphere in 3 units: the upper crust from 0 to 20 km depth, the lower crust from 20 to 40 km depth and the mantle from 40 to 120 km depth, where the heat production is set respectively to \( 1.4\,\mu W/m^3 \), \( 0.35\,\mu W/m^3 \) and \( 0.05\,\mu W/m^3 \).
Before radioactive enrichment, the temperature is steady-state and depends only on depth. In order to test your results you should try to obtain analytical results for the temperature profile as function of depth neglecting the presence of radioactice sources and. Compare thereafter these results with your numerical results. Include then the radioactive sources and compare eventual analytical results with numerical calculations.
We assume that the lithosphere above the slab gets enriched in radioactive elements U, Th and K 1 Gy ago and that this results in an additional heat production of \( 0.5\mu W/m^3 \) over the whole depth of the mantle (not the crust) in a 150 km wide area above the slab. Neglecting all other thermal perturbations that this slab could produce, and assuming that the heat production will remain constant over geological time, compute the thermal evolution of the lithosphere from 1 Gy to present.
The radioactivity will decrease with time. Assuming that the additional heat is produced at 40% by U, 40% by Th and 20% by K, which have halflives of 4.47 Gy, 14.0 Gy and 1.25 Gy respectively, compute the thermal evolution of the lithosphere and compare with the result obtained above.
A very good reference is the textbook by Winther and Tveito on partial differential equations. It is available online from the University library.
Here follows a brief recipe and recommendation on how to write a report for each project.
The preferred format for the report is a PDF file. You can also use DOC or postscript formats or as an ipython notebook file. As programming language we prefer that you choose between C/C++, Fortran2008 or Python. The following prescription should be followed when preparing the report:


Package for constraints. ConBox is a special class, not a constraint, but has static methods for creation of frequently used constraints.


How a request is being processed
or how you can follow a request to debug it .e.g. http://localhost:8080/yanel/yanel-website/en/documentation/how-a-request-is-being-processed.html
- Figure out the Realm.
http://localhost:8080 is the root context of the servlet engine
/yanel is the Yanel servlet context as configured in build.properties resp. local.build.properties
/yanel-website is the realm prefix as configured in conf/realms.xml resp. conf/local/local.realms.xml resp. WEB-INF/classes/realms.xml
You will find out where the realm is configured e.g. ../src/realms/yanel-website/realm.xml - Figure out RTI/RC Repo
Have a look ../src/realms/yanel-website/realm.xml where the rti-repository is configured. e.g ../src/realms/yanel-website/config/res-config-repository.xml
- Get RTI/RC
Follow the path and get the .yanel-rti
or .yanel-rc
in the content and you will get the Resource Type (e.g. <{http://www.wyona.org/yanel/resource/1.0}xml/>). Also take a look at ../src/realms/yanel-website/res-configs-repo/data/map.rc-map
(Also see org.wyona.yanel.core.util.PathUtil#getRCPath(String)
)
- Get the Resource Type
Have a look at conf/resource-types.xml resp. conf/local/local.resource-types.xml resp. WEB-INF/classes/resource-types.xml to find out where the Resource Type is located. (e.g. /home/simon/src/yanel/src/resources/xml/resource.xml) - Get the Resource Type Class (where the view is being generated)
have a look at /home/simon/src/yanel/src/resources/xml/resource.xml to see where the class is located. (e.g. /home/simon/src/yanel/src/resources/xml/src/java/org/wyona/yanel/impl/resources/XMLResource.java)


Select a city:
The city is: {{city}}
The country is: {{getCountry(city) || "Unknown"}}
Billing Zip Code
Save Billing
Shipping Zip Code
Use Billing
Save Shipping


Country Database
{{item.display}}
No states matching {{ac.searchText}}" were found
{{ac.selectedItem.value.name }}
{{ n | capitalize}}
{{ ac.selectedItem.value[n] }}


Reaching the Infamous Star in CLOP
In CLOP, you play a perambulatory challenged unicorn attempting to reach a virgin on the far side of a hill. Sound simple? What if I told you that CLOP was made by the same person who made GIRP and QWOP. Yeah, that QWOP.
Well, although CLOP may seem easier at first, the learning curve only gets steeper as the game progresses.
However, just like QWOP, it is possible. Furthermore there seems to be this spinning star near the start just above the viewport. If you get the jump just right in the right spot you can just about see it.
It doesn’t take many tries to realise how utterly impossible it is to reach it. The internet doesn’t seem to know what it is and it doesn’t look like anybody has ever reached it (prove me wrong). I must find out what it does.
Judging by the few YouTube play-throughs that there are, towards the end of the actual game it becomes a matter of luck no matter how good you are at timing the patterns (the ones I find work for me are HJ-KL, H-JK-H-KL, and HJ*-K/L by the way). Even though I already know how the game ends, I figure one day I’ll play it through since I know it’s possible.
Difficult games like these have a certain quality to them; they can easily turn into obsessions for certain players, like the “Nintendo-hard” games of old. When a goal is virtually impossible though, like the reaching the star, some people chose to give up. Others chose to hack the game. Guess which category I fall into.
A quick “Inspect Element” will reveal that the SWF file is located at http://www.foddy.net/CLOP.swf, so download and decompile that (I use JPEXS) and we have our source code.
Sure enough, everything we need is plain as day and not obfuscated. You can even read the entire list of Sherrod’s taunts in “PlayState” (one giant switch statement).
The next step is to find the code responsible for the infamous star. I can immediately see a class called “Star” that loads the star sprite and plays the spinning animation and since the rest of the code is not obfuscated, all you need to do is search for where a “Star” is initialised.
Instead of cheating and bringing the star down rendering the goal far too easy, why not do something else that will step the goal down from impossible to “Nintendo-hard”? Hmm, let’s see…
private var _gravity:Number = 270;
Muahahaha! Let’s crank that down to 10 aaand yup, CLOP should now be able to fly.  But wait, what’s this?
A quick search for “permission” yielded only one result in “FlxPreloader” (probably a feature of Flixel) and the if statement was quickly put out of commission.
And presto, moon gravity mode! It’s a little hard to move now but it’s also hard to die since you complete a flip before you can hit the ground.
If you want to play around with low gravity CLOP, drop me a line. I’d host it here but Bennett Foddy might not be too pleased about that.
After flying around a bit it’s finally time to reach for the star. Does touching it grant us supernatural powers of dexterity beyond the wildest dreams of a unicorn? Does it teleport us to a world of rainbows and magic?  Well, we’re about to find out. Then we’ll finally know if it is truly an easter egg that requires skills that transcend gaming and enter the realm of hacking to reach, or simply an artifact; an echo of an orphaned game feature that never quite made the cut. Here it is, the moment we’ve all been waiting for:
Well that was anti-climactic…


Reports "marker" interfaces which have no methods or fields.
Such interfaces may be confusing, and normally indicate a design failure.
Interfaces which extend two or more other interfaces or interfaces
which specialize the generic type of their superinterface will not be reported by
this inspection.
Powered by InspectionGadgets


Your Profile
{{ doctor.user.get_full_name.title }}
About
{{ doctor.about }}
Educational Qualifications
{{ doctor.education }}
Availability
{{ doctor.available_description }}
{{ doctor.available_description }}


--- layout: page title: Donate subtitle: Help Us Spread Knowledge permalink: /donate/ ---
We keep our costs pretty low but our domain costs $25 a year, and all the time I spend on the church is time that I am not working. Obviously the more that we get the better we can serve our community and provide better outreach. All your donations are tax deductable, if you need a letter from us please email<EMAIL_ADDRESS>with your name and address and we will give you a tax receipt.
Please type in a donation amount (in US dollars), $15 is appreciated. For every dollar we get we can buy 10 days of server time, or 200 leaflets we can use to spread the message of kopimism.
The Kopimist Church (of Idaho Inc.) is a US non-profit 501(c)3 organization, the Kopimist Church of Canada our Canadian arm is also a Federally registered non-profit but does not yet have charity status. Donations will be made in US dollars and distributed between churches as needed.
Donate


Sylvanian Families Persis Persian Cat Family
UK Biography Information
Father Septimus Persis is a master craftsman, making the most beautiful, colourful rugs that Sylvania has ever seen! Sitting at his loom, surrounded by wonderful, complicated designs, Septimus creates his masterpieces in delicate coloured silks and cottons on sturdy jute strands. 'Why have the floor covered in a single coloured carpet, when I can give you the moon and stars in a rug?" he asks his customers.
Mother Salome Persis is an artist and draws her inspiration from nature, she creates a lot of the intricate designs that her husband Septimus uses in his rugs. Sitting at her easel in the woods drawing and painting for hours, Salome feels at peace with the natural world that is all around her.
Brother Nolly Persis' idea of the 'purrfect' day is to play in the garden, only returning to the house at mealtimes. His favourite pastime is to climb up all the different trees but predictably, he always seems to gets stuck up the biggest tree! As soon as his father, Septimus, hears his son's cries for help, he mutters: "Not again!" as he heads out into the garden. Nolly just shrugs his shoulders and smiles each time.
Sister Sadie Persis likes nothing better than to curl up with a good book in the sunniest part of the house. She can spend hours reading romantic novels in the sun's warm rays, oblivious to the world around her.


--- layout: foundation_layout --- {% include include_navigation.html %} {% include include_heading.html %} {% include include_title_bar.html %} {{ content }} {% include include_footer.html %}


--- layout: base title: Junk Land ---
It's been nearly half a century since the Garbage Wars. Junk Land is the only home you know, and collecting scrap is the only way you know how to live.
...actually, it's a great way to live! Let's get to work. Where's my duct tape?
In this resource-driven card game for 1-4 players, you're an optimistic, scrappy adventurer set in a paradoxically lush wasteland of junk. You need to be the first to build one of the many super cool things you can make with the scrap you collect.
But you can only carry so much at a time.
This card game plays in a series of about 7-10 turns for each player, resulting in quick 20-30 minute games. I consider Junk Land to currently be in the Alpha stage, as the artwork has a long way to go. The game, however, is quite well-tested and mature. I am attempting some artwork myself, but I could use any volunteers who are good with silly illustrations.
I have room for this, right?
Items are cards that let you collect resources and get interesting bonuses. Items can be stacked into piles, but only the top card on the pile provides a bonus. Increase your Capacity to get more piles.
Down to the essentials: string, wood, metal, and glass.
Simplify your inventory by scrapping Items at any time down to their essential components. The tough part is knowing when to keep that neat item for its bonus, or to scrap it for something better. Scrapping means you get to make more stuff, but is also harder to carry because each element type counts as a pile!
Duct Tape is scarce and critical resource. It's lost when scrapping, so it cannot be found in items. You must use other, more clever means of acquiring duct tape.
I need that!
 Bonuses include things like Initiative (starting player), Capacity (the ability to carry more stuff), Conversion (convert some stuff to other stuff!), and Collection (get more stuff each turn!). Blueprints are powerful, but they leave the rotation every few turns so you'd better make your move. Most blueprints require Duct Tape.
The first person to build an Awesome Blueprint wins the game immediately. Awesome Blueprints are always available, but tough to build. They all require six duct tape, for example.
Friends are useful, permanent bonuses that you can collect throughout the game.
Friends can do things like convert resources, give permanent initiative boosts, increase your capacity, or just give you more stuff each turn. They don't require capacity to carry, so you can collect as many as you like. They come and go very quickly, however, so grab them when you can.
Maximize your bonuses. Keep a Friend.
The rules include a three-game solo campaign where you have a limited time to build an Awesome Blueprint. The gameplay becomes more about maximizing the bonuses than thwarting your opponent. Friends get to be kept from one game to the next
The bonuses are also part of a rich iconographic language that are easy to track and straightforward to interpret.
Want to try it out yourself? It's free! On Github
Not quite ready to buy? That's fine, you can play the game for free. You just need to be willing to print out the PDFs, and cut the cards yourself. It usually takes me about 20 minutes to cut them and put them into sleeves.
Be sure to check out the attached PnP notes on the download for tips.
The rules are also available on the GitHub.
{%include cc-junkland.html %}
Unfortunately, I'm not an illustrator.
Many people have expressed interest in this game. I'm just a hobbyist, but I'm hoping for someone out there who would also like to draw over fifty junk-filled illustrations for just the love of the game and the hobby. I know it's a lot and I am not holding my breath. Until then, the game will be just words, icons, a blank spot in the middle, with the occasional doodle.


lround
, lroundf
, llround
, llroundf
—round to integer, to nearest#include <math.h> long int lround(double x); long int lroundf(float x); long long int llround(double x); long long int llroundf(float x);
Description
The lround
and llround
functions round their argument to the
nearest integer value, rounding halfway cases away from zero, regardless
of the current rounding direction. If the rounded value is outside the
range of the return type, the numeric result is unspecified (depending
upon the floating-point implementation, not the library). A range
error may occur if the magnitude of x is too large.
Returns
See Also
round
functions for the return being the same floating-point type
as the argument. lrint
, llrint
.
Portability


{% if not user.is_activated %}
You should verify your account otherwise it may be deleted. Please check your email to verify. Send the verification email again.


|
|
CIFXTaskManager Class ReferenceInheritance diagram for CIFXTaskManager:
List of all members.
Constructor & Destructor Documentation
| CIFXTaskManager::CIFXTaskManager |
( |
|
) |
[private] |
|
| CIFXTaskManager::~CIFXTaskManager |
( |
|
) |
[private, virtual] |
|
Member Function Documentation
| U32 CIFXTaskManager::AddRef |
( |
void |
|
) |
[virtual] |
|
|
|
This method increments the reference count for an interface on a component.
- Note:
- It should be called for every new copy of a pointer to an interface on a given component.
- Returns:
- It returns a U32 that contains a value from 1 to 2^32 - 1 that defines the new reference count. The return value should only be used for debugging purposes.
Implements IFXUnknown. |
|
|
This method adds a new task to the task manager.
Internally this creates an IFXTaskManagerNode to hold the registration data. A task handle is returned which identifies the registration, and can be used to remove the task from the TaskManager.
The Task Data is a template of the event this task is to handle. Fields which are filled with default values (zero, null, etc) are treated as wild fields and match any event; fields with a specific value must match the task data associated with a particular event in order for the IFXTask to be invoked. The registered IFXTaskData is not actually passed to the IFXTask::Execute method; rather, the IFXTaskData that is associated with the event is passed to the Execute method.
- Parameters:
-
| pTask | The IFXTask pointer.
|
| pData | The IFXTaskData pointer.
|
| priority | The priority for this task. Priority is used to resolve the order of execution when multiple tasks are registered to handle the same event.
|
| pTaskHandle | Returns the task handle.
|
- Returns:
- Returns an IFXRESULT code.
- IFX_OK upon success.
- IFX_E_NOT_INITIALIZED if the component has not been initialized.
- IFX_E_INVALID_POINTER is returned if pTask, pData, or pTaskHandle is NULL.
Implements IFXTaskManager. |
|
|
This method creates an IFXTaskManagerView for a given event.
An event is defined by an IFXTaskData object. This method matches the event to the IFXTaskData "pattern" contained in each registered IFXTaskManagerNode. Each match results in the node pointer being added to the IFXTaskManagerView. Thus, the View contains all matching task handlers for a given event. Since tasks can be added, removed, and modified at virtually any time, a given view is highly time sensitive and should generally not be held.
It is possible for a View to contain no data (i.e., no task nodes). This simply indicates that there were no matching tasks.
See IFXTaskManagerView for more information.
- Parameters:
-
| pPattern | The IFXTaskData which defines the event.
|
| ppView | Returns an IFXTaskManagerView. ppView must not be NULL -- the caller must supply a valid pointer - but the pointer should not actually contain a IFXTaskManagerView. Rather, an IFXTaskManagerView will be created and returned when this method is called, and the contents of ppView will be overwritten.
|
- Note:
- For efficiency, the Task Manager recycles TaskManagerViews. It will not recycle a view object as long as anyone else has a pointer to it, and uses the reference count to verify this. For this reason it is very important not to keep a non-reference-counted pointer to a returned IFXTaskManagerView, as the contents could change without notice.
- Returns:
- Returns an IFXRESULT code. This may also return errors from IFXCreateComponent if it is necessary to create a new IFXTaskManagerView. It may also return errors from IFXTaskManagerNode::MatchPattern
- IFX_OK upon success.
- IFX_E_NOT_INITIALIZED if the component has not been initialized.
- IFX_E_INVALID_POINTER is returned if pPattern is NULL.
- IFX_E_INVALID_HANDLE is returned if ppView is NULL.
Implements IFXTaskManager. |
| IFXRESULT CIFXTaskManager::GetOrigin |
( |
IFXUnknown ** |
ppOrigin |
) |
[virtual] |
|
|
|
This method retrieves the IFXTaskManagerNode for a registered task.
This allows modification of registration data.
- Parameters:
-
| taskHandle | The task handle returned by AddTask.
|
| ppNode | Receives the IFXTaskManagerNode pointer.
|
- Returns:
- Returns an IFXRESULT code.
- IFX_OK upon success.
- IFX_E_NOT_INITIALIZED if the component has not been initialized.
- IFX_E_INVALID_POINTER is returned if ppNode is NULL.
- IFX_E_INVALID_HANDLE is returned if taskHandle is IFXTASK_HANDLE_INVALID.
- IFX_E_NOT_FOUND if the specified task is not found. Since multiple components contain an IFXTaskManager, this error may indicate an attempt to retrieve a task from the wrong component.
Implements IFXTaskManager. |
|
|
This method initializes the IFXTaskManager.
- Parameters:
-
| pCoreServices | A pointer to the CoreServices object.
|
- Returns:
- Returns an IFXRESULT code.
- IFX_OK upon success.
- IFX_E_ALREADY_INITIALIZED if the IFXTaskManager object has already been initialized.
- IFX_E_INVALID_POINTER is returned if pCoreServices is invalid.
Implements IFXTaskManager. |
| IFXRESULT CIFXTaskManager::QueryInterface |
( |
IFXREFIID |
riid, |
|
|
void ** |
ppv |
|
) |
[virtual] |
|
|
|
This method provides access to the various interfaces supported by a component.
Upon success, it increments the component's reference count and hands back a pointer to the specified interface.
- Note:
- A number of rules must be adhered to by all implementations of IFXAPI QueryInterface . For a list of such rules, refer to the IFXCOM usage guidelines.
- Returns:
- Upon success, IFX_OK is returned. Otherwise, either IFX_E_INVALID_POINTER or IFX_E_UNSUPPORTED are returned.
Implements IFXUnknown. |
| U32 CIFXTaskManager::Release |
( |
void |
|
) |
[virtual] |
|
|
|
This method decrements the reference count for the calling interface on a component.
- Note:
- If the reference count on a component falls to zero, the component is destroyed.
- Returns:
- It returns a U32 that contains a value from 1 to 2^32 - 1 that defines the new reference count. The return value should only be used for debugging purposes.
Implements IFXUnknown. |
| IFXRESULT CIFXTaskManager::RemoveTask |
( |
U32 |
taskHandle |
) |
[virtual] |
|
|
|
This method removes a task from the Task Manager.
- Parameters:
-
| taskHandle | The task handle returned by AddTask.
|
- Returns:
- Returns an IFXRESULT code.
- IFX_OK upon success.
- IFX_E_NOT_INITIALIZED if the component has not been initialized.
- IFX_E_INVALID_HANDLE is returned if taskHandle is IFXTASK_HANDLE_INVALID.
- IFX_E_NOT_FOUND if the specified task is not found. Since multiple components contain an IFXTaskManager, this error may indicate an attempt to remove a task from the wrong component.
Implements IFXTaskManager. |
| IFXRESULT CIFXTaskManager::Reset |
( |
|
) |
[virtual] |
|
|
|
This method resets the IFXTaskManager, resetting it to a just-initialized state.
All registered tasks are removed.
- Returns:
- Returns an IFXRESULT code.
- IFX_OK upon success.
- IFX_E_NOT_INITIALIZED if the IFXTaskManager object has not been initialized.
Implements IFXTaskManager. |
| IFXRESULT CIFXTaskManager::SetOrigin |
( |
IFXUnknown * |
pOrigin |
) |
[virtual] |
|
Friends And Related Function Documentation
| IFXRESULT IFXAPI_CALLTYPE CIFXTaskManager_Factory |
( |
IFXREFIID |
riid, |
|
|
void ** |
ppv |
|
) |
[friend] |
|
Member Data Documentation
© 1999 - 2006 Intel Corporation. All rights reserved.
* Other names and brands may be claimed as the property of others.
|
|


To use the module, you need to modify your application’s web.xml
files. Configuration is slightly different depending on the topology you are setting up.
Refer to Common Topologies for HTTP Session Management for more information. Modifying the war file can be done manually or with the modify_war
script. To see the command line options for the modify_war
script, invoke:
$ modify_war -h
Manual Configuration
To modify your war or ear file manually, make the following updates:
web.xml needs a filter added as follows. If you have your own filters, the Geode Module filter must be the first one.
<filter> <filter-name>gemfire-session-filter</filter-name> <filter-class> org.apache.geode.modules.session.filter.SessionCachingFilter </filter-class> <init-param> <param-name>cache-type</param-name> <param-value>peer-to-peer</param-value> </init-param> <init-param> <param-name>gemfire.property.locators</param-name> <param-value>localhost[10334]</param-value> </init-param> </filter> <filter-mapping> <filter-name>gemfire-session-filter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
Add the following jar files from the AppServer.zip to the
WEB-INF/lib
directory of the war:- geode-modules jar
- geode-modules-session-internal jar
- geode-modules-session jar
- slf4j-api jar
- slf4j-jdk14 jar
Add the following jar files from the
$GEODE/lib
directory to theWEB-INF/lib
directory of the war, where$GEODE
is set to the Geode product installation:- antlr jar
- fastutil jar
- geode-core jar
- geode-json jar
- javax.transaction-api jar
- jgroups jar
- log4j-api jar
- log4j-core jar
- log4j-jul jar
If you are deploying an ear file:
- Copy all the dependent files, given above, to the
lib
directory of the ear. Modify each embedded war file’s manifest by adding a Class-Path entry which references the shared jars added in the previous step. For example:
Manifest-Version: 1.0 Built-By: joe Build-Jdk: 1.8.0_77 Created-By: Apache Maven Archiver-Version: Plexus Archiver Class-Path: lib/geode-modules-1.0.0.jar lib/geode-modules-session-internal-1.0.0.jar lib/geode-modules-session-1.0.0.jar lib/slf4j-api-1.7.7.jar lib/slf4j-jdk14-1.7.7.jar lib/antlr-2.7.7.jar lib/fastutil-7.0.2.jar lib/geode-core-1.0.0.jar lib/geode-json-1.0.0.jar lib/javax.transaction-api-1.2.jar lib/jgroups-3.6.8.Final.jar lib/log4j-api-2.5.jar lib/log4j-core-2.5.jar lib/log4j-jul-2.5.jar
Peer-to-Peer Setup
To run Geode in a peer-to-peer configuration, use the modify_war
script with options
-t peer-to-peer
, -p gemfire.property.locators=localhost[10334]
, and -p gemfire.propery.cache-xml-file=<moduleDir>/conf/cache-peer.xml
to result in the following web.xml
content:
<filter>
<filter-name>gemfire-session-filter</filter-name>
<filter-class>
org.apache.geode.modules.session.filter.SessionCachingFilter
</filter-class>
<init-param>
<param-name>cache-type</param-name>
<param-value>peer-to-peer</param-value>
</init-param>
<init-param>
<param-name>gemfire.property.locators</param-name>
<param-value>localhost[10334]</param-value>
</init-param>
</filter>
Client/Server Setup
To run Geode in a client/server configuration, you make the application server operate as a Geode client. Use the -t client-server
option to the modify_war
script. This adds the following filter to application server’s web.xml
file:
To run Geode in a client/server configuration, you make the application server operate as a Geode client. Use the modify_war
script with options
-t client-server
and -p gemfire.property.cache-xml-file=<module dir>/conf/cache-client.xml
to result in the following web.xml
content:
<filter>
<filter-name>gemfire-session-filter</filter-name>
<filter-class>
org.apache.geode.modules.session.filter.SessionCachingFileter
</filter-class>
<init-param>
<param-name>cache-type</param-name>
<param-value>client-server</param-value>
</init-param>
<init-param>
<param-name>gemfire.property.cache-xml-file</param-name>
<param-value>module dir/conf/cache-client.xml</param-value>
</init-param>
</filter>
The cache-client.xml
file contains a <pool> element pointing at the locator. Its default value is localhost[10334].
Starting the Application Server
After you update the configuration, you are now ready to start your application server instance. Instantiate the locator first:
$ gfsh start locator --name=locator1
Then start the server:
$ gfsh start server \
--name=server1 \
--server-port=0 \
--locators=localhost[10334] \
--classpath=<moduleDir>/lib/geode-modules-1.0.0.jar:\
<moduleDir>/lib/geode-modules-session-internal-1.0.0.jar
Once the application server is started, the Geode client will automatically launch within the application server process.
Verifying that Geode Started
You can verify that Geode has successfully started by inspecting the application server log file. For example:
info 2016/04/18 10:04:18.685 PDT <localhost-startStop-2> tid=0x1a]
Initializing Geode Modules
Java version: 1.0.0 user1<PHONE_NUMBER>-11-18 08:46:17 -0700
javac 1.8.0_121
Native version: native code unavailable
Source revision: 19dd8eb1907e0beb2aa3e0a17d5f12c6cbec6968
Source repository: develop
Running on: /<IP_ADDRESS>, 8 cpu(s), x86_64 Mac OS X 10.11.4
Information is also logged within the Geode log file, which by default is named gemfire_modules.<date>.log
.
Configuring Non-Sticky Session Replication
Some situations require sessions to be ‘non-sticky’, which means that client requests can be directed to any server in a cluster of application servers instead of the same server each time. To achieve this, you must configure your deployment as described for the following topologies.
Peer-to-Peer
No additional configuration is required.
Client-Server
For client-server topologies, the local client cache must be empty. Ensure that the filter property gemfire.cache.enable_local_cache=false
is set. This effectively sets the local client cache to be a PROXY cache.
Note: Non-sticky sessions affect performance because sessions need to be re-created every time a request hits a different server. This may not be noticeable when the session attributes are small, but may become more evident as the session attributes increase in size and/or number.


Open Yourself
Search
Select Category
Love
Life
Friendship
Philosophy
Traval
Poetry
Shayari
Humour
Inspiration


At a high level the Verification SDK supports email verification functionality.
Verification of an email address
Updating user with verified email address


TOC
Prerequisites
- Install Apache Web Server
www
group:apache
- restorecon -R
www
- Install MariaDB Relational Database Server
- Install PHP
Installation
Install PHP Extensions
# Laravel required PHP extensions.
$ sudo dnf install php php-common php-cli php-pdo php-mbstring php-zip php-xml
# Restart Apache
$ sudo systemctl restart httpd
Install Composer
We will need composer to install laravel and it’s dependencies
$ curl -sS https://getcomposer.org/installer | php
$ sudo mv composer.phar /usr/local/bin/composer
$ chmod +x /usr/local/bin/composer
$ composer -V
Install laravel installer
$ composer global require "laravel/installer"
# Place the ~/.config/composer/vendor/bin directory in your PATH so the laravel
# executable can be located by your system.
$ echo 'export PATH="$PATH:$HOME/.config/composer/vendor/bin"' >> ~/.bashrc
Restart Terminal. Now you can create a laravel project with the commands
$ laravel new ProjectName
Setup
$ cd ProjectName
$ cp .env.example .env
$ nano .env
Edit the .env file with DB_* lines with the correct info
DB_HOST=localhost
DB_DATABASE=laravel_equals_winning
DB_USERNAME=Chur
DB_PASSWORD=Chur1
Serve
$ php artisan serve
# Laravel development server started on http://localhost:PORT/
More Problems
1.storage
permissions:775
group:apache
2.application key