RHINELAB

RHINELAB Advanced Research Laboratory - Core Documentation

Properties2
descriptionThe main structural gatekeeper of the laboratory function. Don't worry, nothing happens here quite much.
tagsadministration, core

8 min read

Welcome to RHINELAB

This is the main page of the RHINELAB-RINALAB laboratory documentation, so customarily so, a welcome is said to be needed. Welcome to the main page. I am sure it would be very much helpful, planned of sort, to member of the laboratory itself in the future, as both a model of operation, and also a central piece of studies, information configuration, and bulletin of sort. The main page here works and function for this entire website, as the fundamental repository of which we will configure most of the expected contents, and functionalities of this site.

If you want quick information, you can see RL.2. Laboratory Structure as the particular inquiry section, UNIG - Named Laboratory for different laboratories in existence of RHINELAB, and PL.Intro. Introduction to the philosophy of RHINELAB for the most introduction to the content specified thereof for the philosophy section. For the surface contact information and so on, you can see them in the frontmatter website, or the more technical back-end or so website. For planned details and contact, see Contact.

Intended contents

The following are what we are intending this site to hold, in the future or so regardless.

  1. Foundational resources of the laboratory.
  2. Logistical denotation and summary of all logistics of the lab.
  3. Artefacts and working system.
  4. Updating on working systems.
  5. Assignments, directives and working/research/foundational documentation/buildup.
  6. Programme and intellectual/specific research events.
  7. Manifesto and subsequent core laboratory principles and designs, how the laboratory works, what is the organization.
  8. General stateful organization of the laboratory.
  9. Member pages.
  10. Works and publications, poster and showcases.
  11. Scheduling. Pending works, modification and preview.
  12. Collaborations and so on.
  13. Documentation of core functionalities and technologies of the lab, like git or quarto or even something as simple as markdown. Including how to work with latex or typst and other documenting system.

Those would be the content provided, alongside discussions and philosophical treatises that I would be giving RHINELAB and the larger body the virtue of exposing. It would also be a good prerequisite or rather something out of proposition for people to practice working on philosophies and system design, as to understand what there is of RHINELAB, and good practices for people in RHINE@PHIL Philosophical Research Group.

About this laboratory

In case you haven’t read from the front-facing website or so, RHINELAB is a theoretical research laboratory with the side prospect being a semi-experimental laboratory, under budget, and under constraint if there are any. In doing so, we are committed to the act that most of the time, would be abhorrently dismissed by the general academic society or so, during which times we are doing STEM research. Picking a philosophical commitment, but stand in between. That is, we want to perfect the art of tension1 to our best of ability. Our core belief stems from the reality of such, that there exists no fundamentally right model, and there exists no fundamentally wrong model in hindsight. Only there exists miscategorized, misused, misconfigured, and overall just the plain wrong usage there is. In doing so, that is the foundation and one of the core belief, that shaped RHINELAB to what it is, and the philosophies it carries with downstream effect.

In this website, you will find it as the central hub of operation of the entire lab, written down here, of organization, of whatever listed above in the functionalities, and of which is the living space, though detached from its many details, to coordinate different people together, and different worlds together at once. That means, basically, is that while it is a laboratory, our laboratory works and functions kind of, or rather particularly so, similar to how a fundamental institution operates, just without the money, and perhaps without the rhetoric often seen of institutional gravity thereof. We have, for example, RHINE@MAPR, the Mathematics and Physics Research Laboratory, and RHINE@MTAIL, the Modelling Theory and Theoretical Artificial Intelligence and Learning Theoretic Research Laboratory, which is perhaps very pointed of its intention and purpose.

Overtime, more information will be added, so please apologize if there are any missing packages, or so, of details inside this particular repository thereof. Because of the rate on operation, there will also be fairly lots of modification to be, as well as laboratory Member Introduction, for example, which will be shifted overtime. We then suggest you to take the main general link, should you wish instead, and move them instead of internal link inside this page. Contact information and so on will also be provided, and if you wish to inquire further, we are happy to present ample about of connections for you to dial in.

Structure

The following outlines the general shape and form of typical sitemap. Most of the content will be added later. Because of the fact that quartz works on Obsidian.md, the linking and backlinks are manually added, so if there are any things missing, please send a notification or issue on GitLab for such matter.

Important classification

As of now, under such inquiry thereof the organization and main functional groups under strain of institutional insufficiency of scholars, the organization thereby activated or concentrated, are RHINE@TAAI (Theoretical and Applied Artificial Intelligence), RHINE@MAPR (Mathematics and Physis Research), RHINE@LOGIT (Logistical Infrastructure and Architecture), and RHINE@MTAIL (Modelling Theory and Artificial Intelligence, Learning-theoretic) functionals.

RHINE@CAD - Organization Descriptions

The majority of them are in philosophy and conjectures there be of the laboratory. There is also organization of the laboratory for many of its operations and assignments. The section is maintained by CAD for much of its operation here and others. You can see the general encyclopaedia at Encyclopaedia Structure.

General information

  1. RL.1. Institutional Structure - The organizational structural and operational framework of RHINELAB. Roles and partitions thereof.
  2. RL.2. Laboratory Structure - The concurrent operational structure and functional organizational reality of RHINELAB (Currently, we are in phase I).
  3. RL.2.1. Domain, Field, and Foundation.
  4. RL.3. Members and Directorates.
  5. RL.3.1. Community Members and Directorates.
  6. RL.4. Document System.
  7. RL.5. Project Systems.
  8. RL.6. Logistical System.
  9. RL.7. Research System.
  10. RL.8. Research Activities.

Guideline

Guidelines are focused on capable contents. That is, contents that are of technical details or so bare minimum to present and operate inside the laboratory that is. For further details on such, please inquire the included specialization documentation of the matter, which would be deployed on separate websites.

  1. Guideline - Core Infrastructure - Guideline for core infrastructure of the laboratory functions.
  2. Guideline - How to use GitHub, GitLab, and Git - Guideline for technical version control system - git and the cloud platforms of GitHub and GitLab 2
  3. Guideline - How to Use OSF - OSF, Open Science Foundation, and many similar platforms of such function, guideline as stated of such.

Laboratory

Listing for internal laboratories of the lab.

  1. UNIG - Named Laboratory - Universal Academic Research Group administration and core laboratory functions.
  2. ONIG Operational Group - General (Academic) Research Group classification system.
  3. SNIG Operational Group - Special (Academic) Research Group classification system.
  4. ANIG Operational Group - Abstract (Academic) Research Group classification system.

RHINE@LOGIT Logistics

Logistic is the most contingent specification of the laboratory. That is why, for the majority of the time, the following up

  1. TBH

Philosophy and Institutional Baseline

  1. PL.Intro. Introduction to the philosophy of RHINELAB.

Donation and financial support

For donations and support, Funding and Donation outline somewhat the possible request and support scheme that would be available for receiving fundings and so on. Since we are a small group, we mainly work within the constraint of management minimality i.e. funds will be handled to specific founder’s financial account.

Footnotes

  1. Tension here refers briefly to, the incollapsibility of argument. Because most of our philosophies are to be effective theory philosophy, that is, there exists no universal theory of the current date, only many attempts and none should hold that ontology as being unquestioned. That is the stance we are putting, so is to also invest in unproven theory under clear enough justification thereof. ↩

  2. Because of the generality and sufficient universality on technical standard of version control system, it is wise to see for even Codeberg and Gitea, such would still use and utilize the foundational infrastructure on backend of git, even if to say it allows for many reconfigured and flavoured version of said terms. As such, one of the many ways to utilize this fundamental function, such is to reduce burden on logistical systems, is to provide a lessen achievement of content in such way of learning the core infrastructure of RHINELAB. And for reference, Gitea is self-hosted. ↩

Graph View