oofem-wiki

User Tools

Site Tools

Trace:
start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
start [2013/05/28 00:15] – [Developers] mikael.ohmanstart [2019/10/25 08:16] (current) – [How to get started with OOFEM] bp
Line 1: Line 1:
 ====== Main Page ====== ====== Main Page ======
-===== Important announcement: ===== 
-**:!: Due to the unauthorized edits caused by compromised user accounts, the user accounts have been deleted. \\ 
-If you need a new user account, please write to info (at) oofem.org. 
-** 
- 
----- 
-\\ 
-\\ 
-\\ 
-\\ 
  
  
Line 15: Line 5:
  
 **The contributions to oofem wiki are highly appreciated. If you want to contribute, just click on login button and follow the registration link. It's just a few clicks away!** **The contributions to oofem wiki are highly appreciated. If you want to contribute, just click on login button and follow the registration link. It's just a few clicks away!**
 +
 +
 +**:!: Due to the unauthorized edits caused by compromised user accounts, the user accounts have been deleted. \\
 +If you need a new user account, please write to info (at) oofem.org.
 +**
 +
 ---- ----
  
Line 26: Line 22:
   * The OOFEM [[http://www.oofem.org/en/documentation/manual.html|documentation]] includes input data manual, element and material library manuals, as well as other useful sources of information. OOFEM installation comes with many examples (located in tests directory), that can help you in making first steps.   * The OOFEM [[http://www.oofem.org/en/documentation/manual.html|documentation]] includes input data manual, element and material library manuals, as well as other useful sources of information. OOFEM installation comes with many examples (located in tests directory), that can help you in making first steps.
   * The link to [[postprocessing| postprocessing HOWTO]] describes the way how to visualize your results.   * The link to [[postprocessing| postprocessing HOWTO]] describes the way how to visualize your results.
 +  * Introduction to [[http://www.oofem.org/resources/doc/python/html/index.html|OOFEM Python interface]]
   * Useful oofem [[options_and_tips| options and tips]].   * Useful oofem [[options_and_tips| options and tips]].
   * Use OOFEM [[http://www.oofem.org/forum|forum]] to post your questions, get support, and much more.   * Use OOFEM [[http://www.oofem.org/forum|forum]] to post your questions, get support, and much more.
Line 38: Line 35:
   * [[gallery:damage|Investigating damage of buildings caused by tunneling]]   * [[gallery:damage|Investigating damage of buildings caused by tunneling]]
   * [[gallery:microstructureCracking|Simulation of three-point bending and splitting tests]]   * [[gallery:microstructureCracking|Simulation of three-point bending and splitting tests]]
 +  * [[gallery:CooksMembrane|Simulation of Cook's membrane using enhanced elements]]
 +  * [[gallery:SteelJoint|Simulation of Steel Joint with plasticity and contact]]
 +
 ===== OOFEM publications & users ===== ===== OOFEM publications & users =====
 Here, the publications containing result achieved using OOFEM by its users are listed. If you use OOFEM, and especially if you use it to accomplish real work, I would like very much to hear from you. Please add information about your publications and results in this section. Here, the publications containing result achieved using OOFEM by its users are listed. If you use OOFEM, and especially if you use it to accomplish real work, I would like very much to hear from you. Please add information about your publications and results in this section.
Line 54: Line 54:
 There are a number of ways that you can contribute to help make OOFEM a better system. Perhaps the most important way to contribute is to write high-quality code to extend or improve the functionality, and to make your code freely available for others to use. There are a number of ways that you can contribute to help make OOFEM a better system. Perhaps the most important way to contribute is to write high-quality code to extend or improve the functionality, and to make your code freely available for others to use.
  
-If you've already written a useful class or module for OOFEM that you would like to make available for others to use, please send it to the project e-mail info(at)oofem.org. Messages sent to this list will be seen by the maintainers, and will be considered for inclusion in future releases of OOFEM. Active developers may obtain commit access to the git repository.+If you've already written a useful class or module for OOFEM that you would like to make available for others to use, please use GitHub pull requests to contribute. The requests will be seen by the maintainers, and will be considered for inclusion in future releases of OOFEM. Active developers may obtain commit access to the git repository. 
 + 
 +  * [[git-tutorial|Git tutorial]] - in construction 
 +  * [[contributing-practical-workflow|Contributing to OOFEM - Practical workflow]] 
  
 If you are not a programmer and cannot provide funding or contribute code, you can still help make OOFEM better and more reliable by reporting any bugs you find in the latest version and/or by offering suggestions for ways to improve OOFEM. The OOFEM developers appreciate to hear from you! If you are not a programmer and cannot provide funding or contribute code, you can still help make OOFEM better and more reliable by reporting any bugs you find in the latest version and/or by offering suggestions for ways to improve OOFEM. The OOFEM developers appreciate to hear from you!
  
 **When you use OOFEM, and especially if you use it to accomplish real work, I would like very much to hear from you. An official letter from your company with short description of OOFEM application can help us significantly when asking for further support.** **When you use OOFEM, and especially if you use it to accomplish real work, I would like very much to hear from you. An official letter from your company with short description of OOFEM application can help us significantly when asking for further support.**
- 
- 
  
 Last but not least, updates and contribution to the web pages and OOFEM WIKI are highly appreciated.  Last but not least, updates and contribution to the web pages and OOFEM WIKI are highly appreciated. 
Line 67: Line 69:
 ===== Developers ===== ===== Developers =====
   * [[coding-conventions|Coding conventions]]    * [[coding-conventions|Coding conventions]] 
-  * <del>[[subversion-howto|Subversion HOWTO]]</del> - Subversion access is now obsolete, OOFEM migrated to Git revision system. 
   * [[git-tutorial|Git tutorial]] - in construction   * [[git-tutorial|Git tutorial]] - in construction
-  * [[git-transition| Git transition]] 
   * [[git-for-lieutenants|Git for lieutenants HOWTO]]   * [[git-for-lieutenants|Git for lieutenants HOWTO]]
   * [[cmake|CMake build system tutorial]]   * [[cmake|CMake build system tutorial]]
 +  * [[perf|Measuring performance bottlenecks with linux perf]]
  
   * [[parallelization-howto|Parallelization HOWTO]]   * [[parallelization-howto|Parallelization HOWTO]]
  
   * [[meeting-2013|Notes from meeting in Prague (April 2013)]]   * [[meeting-2013|Notes from meeting in Prague (April 2013)]]
-  * [[new-input-files|Planned changes for input files (i.e. things that would break backwards compatibility]]+  * [[new-input-files|Planned changes for input files (i.e. things that would break backwards compatibility)]]
  
 +Obsolete pages
 +  * <del>[[subversion-howto|Subversion HOWTO]]</del> - Subversion access is now obsolete, OOFEM migrated to Git revision system.
 +  * [[git-transition| Git transition]]
  
  
start.1369692945.txt.gz · Last modified: 2013/05/28 00:15 by mikael.ohman