Hello Purnawan Pontana Putra,
It looks that you’re off to a good start in that you have an idea how to get the information from the trajectories but from what you showed I am not sure yet how much would be needed to be done in MDA. For instance, do you need to write a new coordinate reader or can you use the existing XYZ reader. Do you want to read energies from a separate file and then associate it with the trajectory using the auxiliaries framework?
There should be enough work to justify at least a medium size (175h) GSoC project.
Ultimately, your proposal has to convince us that this is a worthwhile project, see
https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-FAQ#what-are-your-evaluation-criteria . I’d expect to see a discussion of how your proposed code fits into MDAnalysis’s standard trajectory API (and how you’ll read the topology information), how you’ll process energies (as auxiliaries or as part of the trajectory reading?), and possibly a discussion about API-level interoperability with xbt via xbt-python (or why you’d decide to NOT work on API interoperability). Do not forget to include to discuss (and allocate time!) for testing and documentation.
Given that the submission deadline is TOMORROW you should really start writing. Unfortunately, you’re quite late so there might not be a lot of opportunity to give detailed feedback on the proposal before the deadline.
Best,
OIiver