public:development_track
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
public:development_track [2022/05/10 10:16] – created htlin | public:development_track [2024/09/04 04:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Development Track of CLLab ====== | ====== Development Track of CLLab ====== | ||
+ | ==== Introduction ==== | ||
Hsuan-Tien Lin, 2022/05/10 | Hsuan-Tien Lin, 2022/05/10 | ||
In 2014, CLLab experimented with the // | In 2014, CLLab experimented with the // | ||
- | In 2022, I decided | + | In 2022, I decide |
* The research track is typically assumed to continue indefinitely as long as there is a sufficient match between the member and the lab; the development track would be designed on a project-based basis and will generally end in 3-6 months. Renewing is possible but there are absolutely no guarantees. | * The research track is typically assumed to continue indefinitely as long as there is a sufficient match between the member and the lab; the development track would be designed on a project-based basis and will generally end in 3-6 months. Renewing is possible but there are absolutely no guarantees. | ||
- | * The research track welcomes undergraduate, | + | * The research track welcomes undergraduate, |
* The research track is paid with a monthly salary; the development track is paid with an hourly or daily salary. | * The research track is paid with a monthly salary; the development track is paid with an hourly or daily salary. | ||
- | * The research track members usually have direct 1-1 meetings with me; the development track members usually have direct 1-1 meetings with the mentor (see below). | + | * The research track members usually have direct 1-1 meetings with me; the development track members usually have direct 1-1 meetings with designated |
* The research track members usually participate in weekly group meetings; the development track members can choose to (but are not obligated to) participate in the group meetings. | * The research track members usually participate in weekly group meetings; the development track members can choose to (but are not obligated to) participate in the group meetings. | ||
- | * | ||
- | There are several important things about the development track | ||
- | Undergraduate students who join the development track can get credits for their “special project” course if the student performs as expected. | ||
- | Strong performance in the development track can boost the chance of joining the research track if one chooses to apply to the research track afterward. | ||
- | Every development track member would be assigned a mentor (me or a mature student in the lab) that supervises how the project progresses. | ||
- | Generally, the number of hours that are spent on the development track is negotiable and depends on the project. But usually, 6 hours per week would be absolutely needed to make any progress on the project. | ||
- | Development track members will be provided with lab computing account and resources to facilitate their programming needs; they will not be assigned a fixed seat in the lab (though they are welcome to visit the lab and enjoy the sofa). | ||
- | Should the project call for software release or publication opportunities, | ||
- | For the research track members, here are some useful | + | ===information |
- | You can propose any project that could use the help of development track forces, and I will review the project before deciding whether to approve it. | + | |
- | You can choose to join any project on the development track. But generally, we will not pay you additionally—we will just balance your workloads between research and development. | + | |
- | If you are an M.S. student who was originally in the research track, it is possible to discuss with me if you want to graduate with your efforts on the development track. We can set up development plans that could lead to a decent M.S. thesis. We can discuss how the logistics (payment, workload, etc.) on a case-by-case basis. | + | |
+ | * An undergraduate student who joins the development track can get credits for her/his " | ||
+ | * Strong performance in the development track can boost the chance of joining the research track if one chooses to apply to the research track later. | ||
+ | * Every development track member would be assigned one or more mentors (me or a mature student in the lab) that supervise how the project progresses. | ||
+ | * Generally, the number of hours that are spent on the development track is negotiable and depends on the project. But usually, 6 hours per week would be absolutely needed to make any progress on the project. | ||
+ | * Development track members will be provided with lab computing accounts and resources to facilitate their programming needs; they will not be assigned a fixed seat in the lab (though they are welcome to visit the lab and enjoy the sofa and other resources). | ||
+ | * Should the project call for software release or publication opportunities, | ||
+ | |||
+ | ===information for current research track members=== | ||
+ | * If you believe that you are mature enough to serve as a mentor, you can propose any project that could use the help of development track forces. I will review the project before deciding whether to approve the proposal or not. | ||
+ | * If you want, you can choose to join any project on the development track. But generally, we will not pay you additionally---we will just balance your workloads between research and development. | ||
+ | * If you are an MS student in the research track, it is possible to discuss with me if you want to graduate with your efforts on the development track. We can set up development plans that could lead to a decent MS thesis. We can discuss how the logistics (payment, workload, etc.) on a case-by-case basis. | ||
+ | |||
+ | ==== Current Projects ==== | ||
+ | * [[public: | ||
+ | * [[public: |
public/development_track.1652177819.txt.gz · Last modified: 2024/09/04 04:00 (external edit)