Tensor Reloaded
COLLECTIVE
community
Machine learning research group @ Faculty of Computer Science of Iasi, working on advancing research in an open and transparent way
Contributors
Tensor Reloaded is all of us
Our contributors 1
Thank you for supporting Tensor Reloaded.
About
Machine learning student research group @ Faculty of Computer Science of Iasi
Proposed activities:
- Primary:
- Regular Hackathon’s on Kaggle like contests/tasks
- Forming groups to participate in ML workshops/contests
- Research activity in ML and connected fields
- Secondary:
- Paper reading and presentation activities
- Regularly form teams and encourage research on various topics
- Work on open source tools to be used by the ML/AI community
- Writing of tutorials, courses, articles to explain certain topics on our website/Medium blog (preferable English)
- Creation of YouTube videos for tutorials, presentations of topics related to the purpose of the group (preferably English)
Proposed membership requirements:
- Minimum 3 presentations of a novel/important paper per semester by group coordinators
- Grad/Master’s/Doc student at FII when joined. The IT industry can add value too (maybe later down the line). Maybe teachers.
- If group size allows, team coordinators are to present a monthly status update of their team’s work
- Be present for at least 50%+1 of group meetings per semester if that is not achieved they are to be downgraded to guest status
- Members are required to be enrolled in at least 1 work team, if they don’t want to or are unable to do so, they are to be downgraded to guest status
Proposed member benefits:
- Competitive and motivating environment to code and do research
- Opportunities to network and discuss new ML approaches
- Sharing of resources like datasets, trained models, computing power, and advice between members
- Eventual access to cloud instances to use for training (if any financing happens, by members or external)
Proposed goals:
- Drive interest into the field
- Provide a place where interested people can work and learn more engagingly and productively compared to what they can do individually
- Increase the academic level of students through practical and theoretical work in the field of ML
- Publishing of academic papers
- Developing of useful tools and resources to be used by the group as well as the ML/AI community in an open-source manner
Document Conventions:
- “Group” refers to the entire Tensor Reloaded group
- “Group coordinators” are responsible for executive and administrative decisions for the entire group
- “Team” refers to multiple members that have joined together to work on 1 or multiple projects, for workshops, competitions, research, article/tutorial writing, tool creation, or other such activities
- “Team coordinators” are responsible for leading and motivating a team towards the finalization of proposed projects and are expected to regularly propose future project ideas
- “Member” refers to individuals which are considered part of the group, all individuals in the group are considered members, they are the ones that propose projects, policy changes, form teams, work on projects
- “Guest” refers to individuals which attend group meetings, contribute to projects and engage with the group but do not choose or are unable to qualify to become a full member, they do not have voting power in the group and their issues and contributions come second in priority to that of members
Proposed regulation:
- Group coordinator votes are to be public
- Regular member votes are to be anonymous
- All funds obtained by the group, from competitions, contributions, or otherwise, are to be used solely for group-related activities and resources, such as Paperspace compute instances, GitHub fees, etc.
Proposed structural regulation:
- Group coordinators are responsible for organizing events, setting up teams, driving interest for the group, vetting people before joining
- A member can become a group coordinator if 50% + 1 of group coordinators vote so, absence or abstaining is to be counted as a “no”. The same process is to be used for the demotion of a group coordinator to member status
- The group coordinator can vote on the expulsion of a member. The motion is to be acted upon as the result of the majority vote.
- Regular members may vote the expulsion of another member by a unanimous vote
- Regular members can elect a group coordinator through a unanimous vote, the same process is to be used for demotion to member status
- The group should consist of several Teams
- Each member can be part of multiple teams as long as the Team Coordinator accepts them
- Teams are to be created in response to the beginning of work on a project or to have people collaborate for competitions/workshops, research or publishing.
- A team can work on multiple projects as long as this is accepted by the team that created the project, or if the team creates multiple projects itself
- A repository is to be created on the organization’s GitHub where all activity related to the project is to be accumulated
- A new project must be approved by a group coordinator which will also create the repository and instruct the team on the preferred guidelines when it comes to documentation, coding style, use of group resources
- This is done to assure the group doesn’t become bloated with projects people will not finish. The goal is not to limit the members but simply to assure a certain quality of work is maintained and that enough interest from the team is present to ensure enough dedication is present so that the project is not abandoned
- Any member or guest is invited to contribute to all projects if they so wish
- Guests may participate in all group activities but their vote in manners of administration or operational matters does not hold any value and any contributions or issues raised on projects are not to be treated with the same urgency as members of the group
- Guests may be asked to leave the group meetings if their presence is not wanted by members
Proposed operational regulation:
- At least 1 12/24h hackathon per semester
- At least 1 weekly/biweekly meeting with the whole group. The meetings will consist of:
- presentations prepared by the members on topics of interest for the group
- hackathon/coding sessions
- Debates regarding future activities such as deciding the participation of the group in contests/workshops
- Pitching of new project ideas by members wishing to form a group of interested members to work on the said project (this can be anything from research projects, competitions, working on open source projects, creation of tools/resources related to the interests of the group)
- Members are required to attend 50%+1 of these meetings unless a convincing explanation is given for why they are unable to do so
- Additional team meetings up to team coordinators
- team coordinators are responsible for coordinating the team towards the goal of finishing the project
- they are also responsible for mediation of eventual social/project related disputes between their members
- Team coordinators can ask for assistance from the group coordinators for finding additional members for the group, mediating conflicts, etc.
- All members are invited to provide ideas/suggestions for the direction of the group, new project ideas, change of policy,
- In the case of contests where financial prizes are offered, if any of the teams participating in such contests are to win such prizes, the entire sum is to be evenly split between members of the team. If all members of the team unanimously vote on a different distribution of said prize, that is to be respected. If even one member of the team does not agree on a proposed distribution, then the prize is to be split evenly as stated before. Any violation of the “good-faith” of the members is to be treated with a permanent ban from group activities. Guests are not to be included in the initial prize distribution, and only with the aforementioned unanimous vote of the team members are they to receive any financial gain
- Teams are encouraged to contribute the said prizes for the group fund but are not in any way, shape, or form expected to do so
- If any financial aid/support/funding/member contributions are made towards the group, these funds are to be used for improving the operational activities of the group, as well as acquiring resources that are to be made available to all members of the group. Examples of such expenditures consist of:
- Renting of improved spaces for the group to engage in activities
- Acquisitions of cloud resources/instances to be used by members
- Acquisitions of hardware to be shared with the members to be used in group activities
- Acquisition of cloud-based storage to store various resources used by the group such as datasets, trained models, etc.
- GitHub fees
- Members and guests alike may contribute to the group if they desire, either by offering useful information, access to personal hardware to be used by the group, sharing snacks/food/drinks for meetings and other activities, we encourage such mentalities but in no way are members required or expected to do so and neither are they to be treated preferentially if they engage in such an endeavor. Financial contributions are also possible but must be discussed with a group coordinator to see if there is a place for the contribution to be used effectively before it is to be accepted
Misc:
- Group regulations are to be respected even outside the teaching semesters
- Since the group is likely to consist mainly of students, the theoretical level of the contents presented and should be adjusted such that they can progressively reach a good understanding of the field
- Experienced members are encouraged to guide new members by including them in projects, recommending and reviewing dummy projects, etc.
- We strongly encourage any research paper to be made available on a preprint server such as Arxiv or Research Gate since we support transparent and readily available research
- Source code and documentation used for research projects/workshops/tools are also encouraged to be made publicly available on our organization’s GitHub page
- Competitions such as those found on Kaggle are to follow the regulation agreed upon entering the competition and are not necessarily expected to be made publicly available
- Tutorials/news/informative articles/courses are to be published on our own GitHub website or the group’s Medium blog
- Tutorials, presentations, etc. are encouraged to be published on the group’s Youtube channel, Medium profile, etc. All revenue coming from these sources is to go evenly towards the creators of said content, they are encouraged to contribute to the group fund but are not expected to
- Locations for the meetings (post-pandemic):
- Small groups: Members personal places/ C404
- Small-medium: Nexus Media conference room after-hours
- Medium-big: Negotiate with the faculty to facilitate classrooms
Current members:
- Group Coordinators:
- Cristian Simionescu
- Members:
- Cristian Simionescu
- Robert Herscovici
- Cosmin Pascaru - Remote
- Adrian Piriu
- Guests:
Current teams:
- TreiDaGrei:
- Robert Herscovici
- Cristian Simionescu
- Cosmin Pascaru
*Team coordinators are written in bold
Our team
Cristian Simi...
Admin