User:AkashSinghal

Akash Deep Singhal is a GSOC2015 student pursuing B.Tech + M.Tech from Department of Chemical Engineering, Indian Institute of Technology, Bombay (IN). He is working on the development of Chemical engineering specific models and integration of flash/thermodynamic libraries in ASCEND. To know more, visit his webpage

GSOC 2015

Proposed Plan

This section gives details of the ideal project timeline.

• During this semester (Before May 3)
  • Understand some basic concepts e.g. learning extensively about Mathematical modelling of a Chemical Process, design some basic process flowsheets to get familiar with the ascend modelling environment, recollect various relevant Chemical Engineering concept learnt in last four years
  • Try to get some experience in the relevant portions of the codebase, get familiarize with coding styles and version management in ASCEND
  • Develop a sample flow sheet for Steam reforming and provide complete documentation.
  • Collect (as many as possible) complete project material from various groups working separately on various processes, e.g. Group X is working on complete industrial level manufacture of some process P. This will give us around 25 complete working-process-flowsheets simulated on AspenPlus.

• May 3 – May 5: Discussion
  • Detailed discussion of project methodology and implementation with mentors, community members
  • Finalize the processes and flash algorithms to be worked on

• May 5 – May 12: Literature Survey
  • Identify different reaction paths
  • Find component and mixture properties, working temperatures and pressures
  • Design basic block diagrams

• May 12 – May 19: Conceptual Flow-Sheet Development
  • Writing and solving process equations
  • Check for kinetics, thermodynamics
  • Identify separation and reaction techniques required in different reaction paths
  • Select feasible route from the flow sheets developed. Selection of appropriate reactor, Heat exchanger, separator etc.

• May 19 – May 26: Paper Work
  • Perform manual Mass balance for each equipment
  • Steady state simulation on ASPEN. Get a converged file with recycle
  • Check for the heat duty
  • Equipment sizing for various equipments (manually or Aspen{preferable})
  • Heat Integration : Combine Heat Exchanger Network to minimize the energy consumption
  • Detailed discussion would be needed with mentors and Prof. Kannan, (I intend to do that while the above part goes on)
  • Reporting with extensive documentation

• May 26 – June 2: Begin Coding
  • Choose one process out of the selected ones | Finalize on the basis of ease
  • Code the model

• June 2 – June 9: First process ready
  • By this time, a basic ascend model should be ready and running. In this week, I intend to test it for various parameters and check whether the model is converging or not.
  • Grasp the crunch of this model and start working on the further models

• June 9 – June 20: Keep on writing processes (12 days)
  • Repeat the work done above for single process.
  • Validate models for reusability

• June 21 – June 24: Break
  • I wish to take some break. Go out trekking or for some adventure. Relax a bit.
  • Enjoy first showers of rain after hot and humid summers in Mumbai (One of my favorite time of the year)
  • Would help me for efficient working

• June 24 – July 1: Get back to work
  • Learn extensively about Flash Algorithms
  • DWSIM includes various equilibrium flash algorithms for VLE and even for more complicated SLE etc.
  • Getting info on how to import libraries from DWSIM since the major issue in the integration is that DWSIM core libraries are written in .NET while ASCEND libraries are written in C/C++
  • For the integration Inter-language unification need to be done. Check for its feasibility
  • Nested Loops(default), Gibbs Minimization, Inside-out (for 2-3 phases) are some of flash algorithms used in DWSIM

• July 1 – July 8: Writing Flash Algorithms
  • In case, direct integration of DWSIM package is not feasible or if new flash algorithms are needed to be developed, work on it
  • By the time, mentors guidance period starts on July 4 according to GSOC timeline
  • Get help in the issues I have been facing (though this will already be happening so does not make much sense)

• July 8 – July 15:
  • Come back to models which needed these flash algorithms
  • Make changes accordingly and validate the models
  • Fix any issue that occurs

• July 15 – July 22: Wrap up
  • Final Documentation to be made
  • Complete testing - Check for any bug and troubleshooting in that case
  • Merging my project branch with trunk

• July 22 – Aug 17:
  • Semester will start so will take this time as buffer for any leftovers due to glitches or some bugs
  • Extension for ARM devices: According to current scenario, tech-world is shifting from Laptops to Tablets and Phablets, in short ARM based devices. If time permits, I intend to get this whole package working on netbook, an ARM based laptop for on-the-go-development (an initiative by FOSSEE, IIT Bombay).

• Aug 21: Final Submission of the code to google