[{"_1":2,"_187":-5,"_188":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_162":163},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":85,"_106":107,"_155":-5,"_156":11,"_157":17,"_158":11,"_159":-5,"_160":161},"canonicalUrl","https://hub.docker.com/r/teambitflow/bitflow4j-build/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","teambitflow","reponame","bitflow4j-build","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-03-21T15:49:00.385024Z","description","","is_private","last_updated","2019-05-10T16:28:05.302841Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",489,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","[![Build Status](https://ci.bitflow.team/jenkins/buildStatus/icon?job=Bitflow%2Fbitflow4j%2Fmaster&build=lastBuild)](http://wally144.cit.tu-berlin.de/jenkins/blue/organizations/jenkins/Bitflow%2Fbitflow4j/activity)\n[![Code Coverage](https://ci.bitflow.team/sonarqube/api/project_badges/measure?project=bitflow4j&metric=coverage)](http://wally144.cit.tu-berlin.de/sonarqube/dashboard?id=bitflow4j)\n[![Maintainability](https://ci.bitflow.team/sonarqube/api/project_badges/measure?project=bitflow4j&metric=sqale_rating)](http://wally144.cit.tu-berlin.de/sonarqube/dashboard?id=bitflow4j)\n[![Reliability](https://ci.bitflow.team/sonarqube/api/project_badges/measure?project=bitflow4j&metric=reliability_rating)](http://wally144.cit.tu-berlin.de/sonarqube/dashboard?id=bitflow4j)\n\n# bitflow4j\nbitflow4j is a lightweight framework for performing data analysis on streamed timeseries data.\nThis library implements sending and receiving of a data over various transport channels.\n\n## Installation\n\nAt first, you can \n\n```\n$ git clone https://github.com/bitflow-stream/bitflow4j \n$ cd bitflow4j\n$ mvn install\n```\nWithin the `/target` directory, the file `bitflow4j-0.0.1-jar-with-dependencies.jar` is created. This file should be used for further usages.\n\n## Bitflow script usage and examples\n\nIt is convenient, to invoke the Bitflow4j functionality through a domain specific language called `Bitflow Script`.\nThis lightweight scripting language is implemented in the `bitflow-stream` sub-directory of the [antlr-grammars repository](https://github.com/bitflow-stream/antlr-grammars).\nSee the [README of the Bitflow Script](https://github.com/bitflow-stream/antlr-grammars/tree/master/bitflow-script) for details regarding the script syntax.\n\nThe main entrypoint for a Bitflow Script is the class `bitflow4j.script.Main`.\nIt can be started with the `--help` parameter to list all command line options.\nThe script can be passed directly on the command line, or in a file, using the `-f` option:\n\n```\njava -cp bitflow4j.jar bitflow4j.script.Main -f bitflow-script.bf\n```\n```\njava -cp bitflow4j.jar bitflow4j.script.Main \"input.csv -> Standardize() -> output.csv\"\n```\n\nWhen starting, the Java implementation of the Bitflow Script scans a list of packages for pipeline steps that will be made available in the script. The list of packages to scan defaults to `bitflow4j`, but can be modified by passing a comma-separated list of packages to the `-P` parameter.\n\nTo see which pipeline steps and forks are available, start `bitflow4j.script.Main` with the `--capabilities` parameter.\nSpecify the `-v` parameter for verbose logging, which will show which classes have been scanned, but not registered for usage in the script, because they do not fullfill the requirements listed below.\n\n\n### Registering new Pipeline Steps\n\nInstallation via maven (add this to your pom.xml):\n\n```\n\n\tbitflow4j\n\tbitflow4j\n\t0.0.1\n\n```\n\nTo provide functionality inside a Bitflow Script, a class must implement one of 3 interfaces and 1 abstract class.\nAll implementations of these interfaces are scanned in a list of packages, as describe above.\n\nThe general conditions for successfully registering a class as a pipeline step are:\n\n* The class must not be abstract\n* The class must have at least one constructor with only the following types: `String`, `int`, `long`, `double`, `float`, `boolean`, and the respective boxed types.\n* Alternatively, a constructor with a single `java.lang.Map` constructor is supported. In this case the parameters are not parsed or validated, but simply passed to the constructor inside the Map.\n\nRegistered classes are available in the script under their **simple names**.\nCurrently, if multiple implementations share a name, only one of them will be available in the script. Such collisions will be logged as a warning.\n\nThe parameter names provided in the script must satisfy one of the constructors in the class that implements the pipeline step.\nThe provided parameter values will be parsed to the expected types (`double`, `boolean`, etc), except if the `Map` constructor is used.\nAn error will be shown if parsing a parameter fails or if no fitting constructor can be found.\n\nThe following interfaces can be implemented. See the documentation of the Bitflow Script for more information.\n\n - `bitflow4j.PipelineStep` (abstract class): Registered subclasses of `PipelineStep` can directly be instantiated and added as a single pipeline step.\n - `bitflow4j.script.registry.ProcessingStepBuilder` (interface): Registered instances of this interface can be used to modify the created pipeline in more complex ways than adding a single pipeline step. For example, multiple connected instances of `PipelineStep` can be instantiated and added in a predefined sequence. This should only be used, when pipeline steps depend on each other, so that a constructor with only primitive parameter types is not sufficient.\n - `bitflow4j.steps.fork.ScriptableDistributor` (interface): Registered implementations of `ScriptableDistributor` can be instantiated as a single fork step inside the pipeline. They will receive all defined sub pipelines and must distribute samples according to their custom logic.\n - `bitflow4j.script.registry.ForkBuilder` (interface): If the creation of a `ScriptableDistributor` cannot be implemented in a single constructor with primitive parameter types, a `ForkBuilder` can be used to move the creation of the `ScriptableDistributor` to a dedicated builder function. However, contrary to a `PipelineBuilder`, the `Pipeline` can not be further modified by a `ForkBuilder`.\n\n## Usage in Java code\n\nThe basic data entity is a `bitflow4j.Sample`, which consists of a timestamp, a vector of double values (double array), and a String-map of tags.\nSupported marshalling formats are CSV and a dense binary format.\nSupported transport channels are files, standard I/O, and TCP.\nReceived or generated Samples can be modified or analysed through a Pipeline object, which sends incoming Samples through a chain of\ntransformation steps implementing the bitflow4j.PipelineStep interface.\n\nBitflow4j can be used programmatically through the `Pipeline` class and different instances and implementations of `Source` and `PipelineStep`.\n\n```\nnew Pipeline()\n\t.inputCsv(\"/some/path/to/data.csv\")\n\t.HistogramAlgorithm(\"/path/to/visualization/output\")\n\t.outputCsv(\"/path/to/output/results.csv\")\n\t.runAndWait();\n```\n\nAlso parallel pipelines can be defined via forks. Forks are also steps, which provide the possibility to define several different subpipelines. There exists different distribution techniques like `ForkTag`, `MultiplexDistributor` and `RoundRobinDistributor`.\n\n```\nForkTag forkTag = new ForkTag(\"tagName\");\nforkTag.setSubPipelines(\n\tArrays.asList(\n\t\tnew Pair<>(\"key1\", new Pipeline().step(new BatchFeatureScaler.MinMax())), \n\t\tnew Pair<>(\"key2\", new Pipeline().step(new BatchFeatureScaler.Standardize()))));\nnew Pipeline()\n\t.inputCsv(\"/some/path/to/data.csv\")\n\t.step(new Fork(forkTag))\n\t.outputCsv(\"/path/to/output/results.csv\")\n\t.runAndWait();\n```\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",7603448509,"orgData",{"_86":87,"_88":89,"_90":91,"_92":29,"_93":94,"_95":96,"_97":98,"_99":44,"_100":101,"_102":44,"_103":44,"_104":44,"_105":17},"id","f19f6bce0525406aaa1318e81982a317","uuid","f19f6bce-0525-406a-aa13-18e81982a317","type","organization","orgname","full_name","CIT Bitflow Team","location","Berlin","company","CIT","profile_url","date_joined","2018-08-13T12:34:28.323867Z","gravatar_url","gravatar_email","badge","is_active","recentTags",[108,145],{"_109":40,"_110":111,"_112":113,"_86":114,"_115":116,"_46":133,"_134":135,"_136":29,"_137":52,"_53":138,"_139":140,"_141":124,"_142":133,"_143":62,"_144":17},"content_type","creator",1858291,"full_size",676686913,50377029,"images",[117],{"_118":119,"_120":121,"_122":44,"_123":124,"_125":126,"_127":128,"_129":44,"_130":-5,"_131":113,"_59":62,"_132":-5},"architecture","amd64","digest","sha256:ad8995fce1f4177e25ce141b1284585ec6f5631241bb529aad38de81fe1f8db4","features","last_pulled","2026-09-13T18:12:05.4161499Z","last_pushed","2019-05-10T16:28:05Z","os","linux","os_features","os_version","size","variant","2019-05-10T16:28:04.896885Z","last_updater",3770314,"last_updater_username","media_type","latest","repository",6863293,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_109":40,"_110":135,"_112":146,"_86":147,"_115":148,"_46":153,"_134":135,"_136":29,"_137":52,"_53":154,"_139":140,"_141":151,"_142":153,"_143":62,"_144":17},484622001,52482401,[149],{"_118":119,"_120":150,"_122":44,"_123":151,"_125":152,"_127":128,"_129":44,"_130":-5,"_131":146,"_59":62,"_132":-5},"sha256:17034ffe13cc000b55814d5121568b988507b1226b05f7f95998c8064fe98e32","2026-09-17T21:27:24.769645194Z","2019-04-11T08:47:53Z","2019-04-11T08:47:52.765767Z","v0.0.1","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":164,"_171":172,"_160":185,"_186":11},{"_36":165,"_38":166,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":167,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":168,"_75":11,"_76":170,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":169},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_173":174,"_175":-5,"_176":-5,"_177":178},"count",2,"next","previous","results",[179,182],{"_109":40,"_110":111,"_112":113,"_86":114,"_115":180,"_46":133,"_134":135,"_136":29,"_137":52,"_53":138,"_139":140,"_141":124,"_142":133,"_143":62,"_144":17},[181],{"_118":119,"_120":121,"_122":44,"_123":124,"_125":126,"_127":128,"_129":44,"_130":-5,"_131":113,"_59":62,"_132":-5},{"_109":40,"_110":135,"_112":146,"_86":147,"_115":183,"_46":153,"_134":135,"_136":29,"_137":52,"_53":154,"_139":140,"_141":151,"_142":153,"_143":62,"_144":17},[184],{"_118":119,"_120":150,"_122":44,"_123":151,"_125":152,"_127":128,"_129":44,"_130":-5,"_131":146,"_59":62,"_132":-5},[],"canDeleteTags","actionData","errors"]

teambitflow/bitflow4j-build

Tags for teambitflow/bitflow4j-build