Skip to main content

Softwares


    Figures, Plotting, Graph
    • Origin, Windows, GUI
    • Inkscape
    • Matlab
    • Paraview
    • Gnuplot, unix OS, TUI
    • Mathematica
    • xfig 
    • LibreOffice Draw


    (1) Origin
    Pro: professional level, full-ledged, with statistics function
    Con: not free, not sure if there is free evaluation version

    (2) Origin-like software, QtiPlot derived
    QtiPlot is not free; Labplot is Linux only!
    SciDavis  is cross-platform, a fork from QtiPlot, python scriptable
    Pro: SciDavis  is free under GPLv2, without any restriction
    Con: SciDavis and  Labplot stop at the early development stage; less functions than origin.

    (3) script byMatlab, pyLab(matplotlib), gnuplot
    Pro: good for bath processing, tight integration with data generation codes in matlab or python
    Con: need programming experience

    (4) Office Excel or LibreOffice
    Pro:  widely available, good for report generation,
    Con: Mouse drag edit is not supported, not for high quality plot

    (5) Paraview or other FEA and CFD post-processing visualization
    Pro:  very impressived 2D drawing in 3D view
    Con: complicated, only domain user will use such software

     
    Graph Visualization
    Graphviz, free, multi-system
    visio, GUI,
    processon,online tool


    File converter
      Pandoc

    Presentation
    Beamer (a LaTeX document class for creating slides for presentations)

    Editor
    Vim
    Emacs

    Typesetter
    LaTex
    Latex vs InDesign
    • LATEX is not a program, InDesign is one
    • They are meant for completely different tasks
    InDesign is a program that helps you in layout: one can make newspapers, journals, magazines, books and so on. It produces a text which looks very nicely and compact. Moreover, InDesign provides its user with almost insurmountable ability to make their book/magazine/newspaper/… look prettier: one can add additional layers with images or with small pictures which will serve as a background and so on.

    LATEX
    on the other hand is meant for processing a text with complex structure and hence incorporating different text-like objects (like math formulas) and figure-like objects. It lacks, however, the ability to make texts look fancy and pretty (they instead look really awesome), although one can (if one really wants) embed a picture almost like one works with InDesign. This is mostly because LATEX is used for editing scientific or near-scientific texts.



    LATEX vs FrameMaker

    References:


    Latex vs MS word
    LaTeX is better at:
    • Dealing with mathematical notation.
    • Consistent handling of intra-document references and bibliography.
    • Separation of content and style. In principle this means that you can write your document without caring how it is formatted, and at the end of the day wrap it in the style-file provided by the journal publisher before submission to conform to the house style. In practice some of the journal publishers demand special formatting commands that partially moots this process. Furthermore recent versions of Word and LibreOffice Writer, when properly used, should be able to keep track of various levels of section heading separate from the body text, and apply uniform styling to each level. The gap is somewhat closing.
    • Tables and illustrations. With PSTricks or TikZ, one can produce high quality illustrations within the document (though the learning curve is a bit steep there). And I've found LaTeX to be better at preparing complex tables.
    WYSIWYG (especially Word and Writer) is better at:
    • Collaborative editing. Without using an online site for collaborative LaTeX editing (such as ShareLaTeX), working collaboratively on a LaTeX file ideally requires some sort of separate revision control software. Word and Writer have very good comments/annotations and edit-tracking features. When a large number of authors are commenting on the writing of one file, this can be very useful.
    • Spell check. Admittedly most text editors one uses to edit TeX files also do spell check. But this is generally conveniently built into WYSIWYG editors.
    • Compatibility. Unless you work in mathematics, computer science, or physics (and sometimes even if you work in those fields), it is more likely that your collaborators will know what to do with a Word or Writer file than a LaTeX file.
    • Minimum barrier to entry. If you just care about getting the ideas down on paper, you can use a WYSIWYG editor just like a typewriter. Sure, it may be tedious to fix the formatting later on, compared to LaTeX where one need to first figure out how to setup a bare-minimum file before using, it may be an attractive point.
    A wash:
    • Most journals provide templates for both Word and LaTeX, so there's no real winner there.

    Suggestion: if you want to convince someone to start using LaTeX, start them out first in one of the WYSIWYG environments designed for LaTeX first (for example LyX). This will help somewhat to ameliorate the scary entry barrier.


    personal wiki software for Windows
    cloud-based knowledge management software







Comments

Popular posts from this blog

TUI Fluent

‎ Table of Contents 1. TUI 1.1. Examples 1.1.1. Steady 1.1.2. Unsteady 1.2. discretization schemes 1.3. Turbulence model 1.4. Reference 1.5. Save residual 1.6. Journal 1.6.1. record journal GUI 1.6.2. The interactive TUI inside Fluent helps: 1.7. define 1.7.1. boundary-conditions 1.8. change rotational velocity of moving reference frame 1.8.1. batch model 1.8.2. interactive console TUI 1.9. set background color 1.9.1. invalid command [background] 1.10. syntax 1.11. Batch model 1.12. Boundary condition 1.12.1. Inlet BC 1.13. Animation/residual/monitor on cluster 1.14. Solver 1.15. Change pressure-velocity-coupling model in batch mode 1.16. time step size 1.17. Modifying the View 1.18. initialization 1.19. discretization schemes 1.20. Set under relaxation 1.21. log of execute makefile 1 TUI keywords: Background Execution on Linux Systems, journal file Programming language : Scheme , as a Lisp dial

Fluent Error FAQ

  Process 1928: Received signal SIGSEGV. Running on windows Mesh size, 12M serial     Error:  received a fatal signal (Segmentation fault).     Error Object: #f parallel     select 4 processors         error information     Node 0: Process 1928: Received signal SIGSEGV.         Node 5: Process 2824: Received signal SIGSEGV.     MPI Application rank 0 exited before MPI_Finalize() with status 2      The fl process could not be started.         Reason         This is primarily a Windows issue.                 If running Fluent with -t1 or higher number of processes and leave the session for an extended period of time (2-20 hours), it receives the following message in the console:                 The fl process could not be started.                 No other information about what timed out is provided, and only the cortex process is left running. This issue becomes more significant in light of the switch from serial to -t1.         IP interfaces on the machine

Turbulent viscosity limited to viscosity ratio of 1e+05

** Turbulent viscosity limited to viscosity ratio of 1e+05 *** reason The possible *causes* for large turbulent viscosity ratio include: - Bad initial conditions for the turbulence quantities (k and e) - Improper turbulent boundary conditions - Skewed cells *** solution If the problem is not caused by *bad mesh*, then *the beginning of the phenomena* can usually be avoided by: -Turn off solving *turbulence equations* for the first 100-200 iterations -Turn on turbulence and continue iterations If the problem occurs *in the middle of the iteration process*, then use the following procedure: - Stop the iteration - Turn *off* all equations except the *turbulence equations* - Increase turbulence under relaxation factors (URFs) (k and e) to 1 and iterate for 20-50 iterations - *Turn back all equations* and reduce the turbulence URFs to 0.5-0.8 and then continue iterations - Repeat the above steps for several times For *faster convergence*, it might be useful to obtain an initial solution wit