Project - EmulatedHardware

[Arunesh-Gour]

EmulatedHardware

Project 'EmulatedHardware' is created under 'Projects' section.
It contains 3 columns - To Do, In Progress and Done_.

To Do

Contains un-assigned, pending modules.
Those who wish to take up modules listed under this section and start working on it must assign it to themselves.

To self-assign, follow below steps.

1. Copy tab contents of module which you want to work on.
2. Under In Progress_ column, start out a new tab and paste the contents you copied from To Do_ tab.
3. Just after heading, give a line, and put assignee names as Assigned-to: @<assignee-github-username> in comma separated fashion.
4. After assignee names, put status of work in next line as Status: <status>. This must be updated regularly.
5. Save this tab.
6. Now, under To Do_ column, delete the tab you copied. At a time, a tab can only be in one column.

In Progress

Contains assigned, in-progress modules list.
Details include assignees' names and work status.

After completion of work, the work can be moved to Done_ column, if it is Done, not Partially done.

To complete, follow below steps.

1. Copy tab contents of module which is completed.
2. Under Done_ column, start out a new tab and paste the contents you copied from In Progress tab.
3. Change the status of the module to Done.
4. Save this tab.
5. Now, under In Progress_ column, delete the tab you copied. At a time, a tab can only be in one column.

Done

Contains completed modules.
These modules are stored to keep a track of what's done, who did it, and other details about the module.
This also serves a purpose in making individual project report.

Tabs under this are not supposed to be deleted. They can only be moved to other columns based on situations.

Extra information

• Instead of copy-pasting tabs, simply drag-n-drop and edit as given.
• Use examples/coding/ to get a sense of how to code certain category of files.
  For EmulatedHardware_, the sample file is examples/coding/SampleIoTStubDevice.py.
• Heading of the module is a reference to module listed in respective SRS file, here docs/software/IoTStubs_SRS.rst.
• Mount point refers to directory where the particular file needs to be placed / created.
• File name refers to the name with which the file has to be created under Mount point.
• Class name refers to the name of the class inside the file to be used.
• Readable refers to the only variables that can be read from the respective module.
• Writable refers to the only variables that can be written to the respective module.
• Names without an underscore _ in beginning denotes they are publicly available, i.e. listed in both tuples - ? and _?.
• Names with an underscore _ in beginning denotes they are hidden from public, i.e. listed only in _? tuple.
• Underscore is included in variable naming.

[Arunesh-Gour]

@Arunesh-Gour, @kartik-kumar71, @recker624, @Vikram-BM, @Prakhar-623, @gauravc6, @sanskar-singh-rajput.

Check this discussion and fill your preferences as per your free time and availability.
OPTIONAL!

[Arunesh-Gour]

@kartik-kumar71, @Vikram-BM, @Prakhar-623, @sanskar-singh-rajput.

Need someone someone who can help with hardware simulation.
Work is somewhere related to interdependence of various parameters like fish's discharge, soil nutrients, water cycle etc...

Call me or signal me directly anytime for discussion, only if you don't have exam.
Before calling, react to this comment if you're using a different number (other that your whatsapp or signal number).